From 55fc7a94d9ad351cc3fe56d6e17fe9f6968bb22b Mon Sep 17 00:00:00 2001
From: jonmolle <86323092+jonmolle@users.noreply.github.com>
Date: Tue, 18 Apr 2023 20:34:53 +0000
Subject: [PATCH] Create message to hold non-labeling, non-measurement event
 info (#58)

- Add a space for event collections in the labeler input. These can be data provider campaign ids, some meta identifier, etc.
- Intended to identify a specific set of events that the model provider knows for model building.
---
 .../proto/wfa/virtual_people/common/event.proto     | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/src/main/proto/wfa/virtual_people/common/event.proto b/src/main/proto/wfa/virtual_people/common/event.proto
index b4f7ec6..adc5d3c 100644
--- a/src/main/proto/wfa/virtual_people/common/event.proto
+++ b/src/main/proto/wfa/virtual_people/common/event.proto
@@ -67,6 +67,15 @@ message UserInfo {
   optional uint64 user_id_fingerprint = 6;
 }
 
+// Represents information about the parent event that is not used in labeling or
+// measurement. These are not intended to be unique across all EDPs.
+message TrafficInfo {
+  // Identifies a collection of events. A model provider can use this to group
+  // events during VID model training. This could be something like a campaign
+  // id.
+  optional string event_collection_id = 1;
+}
+
 // Represents info for all user ids associated with a specific event.
 message ProfileInfo {
   // Information for email id.
@@ -126,6 +135,10 @@ message LabelerInput {
   // Device type string. Computed from user agent string using a library
   // function.
   optional string device_type = 6;
+
+  // Event information not intended to be used during labeling or in the
+  // measurement system.
+  optional TrafficInfo traffic_info = 7;
 }
 
 // LogEvent contains all attributes in LabelerInput, as well as other