Universal Pixel Feed
The Log-Level Universal Pixel Feed provides you with data on the firing of all of your Universal Pixels. The feed contains one row per pixel fire. Each row includes both the data received on the fire as well as any segment and conversion IDs that were associated with the event based on the Audience and Conversion rules that matched the traffic. It is possible for a pixel fire to satisfy no Audience or Conversion rules.
The Xandr internal name for this feed is
The columns below are listed in the same order in which they appear in the log-level feed file (top to bottom here, left to right in the file).
- tinyint = 1 byte (8 bit)
- smallint = 2 byte (16 bit)
- int = 4 byte (32 bit)
- bigint = 8 byte (64 bit)
|Column Index||Column Name||Type||Description|
|01||UNIX Epoch time|
The time and date of the universal pixel fire.
The EPOCH time is in milliseconds format, and not the standard EPOCH time.
|02||string||The UUID of the universal pixel.|
|03||bigint||The Xandr 64-bit user ID (stored in the Xandr cookie store). The value of this field is 0 when Xandr does not have a match for this user or the user's browser doesn't accept cookies. The value of this field is -1 for opt-out users.|
|04||string||The entire URL of the page the pixel is on.|
The entire URL of the referrer to the page the pixel is on.
|06||string|| The event associated with the pixel fire. The standard universal pixel events are:|
|07||array of strings|
Strings passed in on the
|08||array of strings|| Strings passed in on the |
|09||array of strings|
Strings passed in on the
|10||array of int||The list of IDs for the segments the user was added to as a result of the universal pixel firing.|
|11||array of int||The list of IDs for the conversion events triggered by the user as a result of the universal pixel firing.|
|12||long||The hourly partition any record row falls into, represented as a UNIX Epoch timestamp value (in milliseconds). Useful for defining hourly partitions when loading into a database or data warehouse. For the Avro format, this field is given the timestamp-millis logical type for native timestamp detection. For example, |
|13||event_value||numeric||The nominal value of the event (passed in as a float from the |
|14||string||The source of the traffic being tracked by the pixel. Possible values are |
|15||string||The ID of the application (in the app store) that the pixel has been placed on. This value can be numeric or alphanumeric (e..g, |
The unique identifier representing the mobile device. The numeric prefix indicates the type of unique device identifier:
The value of this field will be
|17||message||Contains all custom parameters that were sent with the pixel fire. This is represented as a repeated protobuf field with a key (string) and values (repeated string).|