Skip to main content

Data Automatically Captured for Client-Side Tags

Abstract

No matter what implementation method you use, the data listed below are automatically captured by default and stored as segments (with the field names listed below) in LiveRamp for both the CST and the eCST:

No matter what implementation method you use, the data listed below are automatically captured by default and stored as segments (with the field names listed below) in LiveRamp for both the CST and the eCST:

Note

If you receive log files as part of a Measurement workflow, this data will appear as columns in the file.

  • Tag-ID: The tag ID (pid) that this exposure came from.

  • Ref-URL: The URL of the page where the tag was placed.

  • Impression-Key: A unique identifier for this impression that can be used across audience delivery files (for measurement use cases in our Measurement Enablement workflow). Example: When capturing cookies and Identity Envelopes, one impression may capture both a cookie and an envelope. There will be two files delivered: A cookie file with cookies and an envelope file with RampIDs. The Impression Key will allow clients to choose the RampIDs they wish to use for impressions when more than one is returned.

  • Log-Date: The date of the exposure in YYYY-MM-DD format (PST).

  • Log-Time: The date and time of the exposure in YYYY-MM-DD-HH:MM:SS format (PST).

  • Log-Time-UTC-Sec: The time of the exposure in Unix time.

Keep the following in mind:

  • For privacy reasons, the URL will be truncated before the first "?" or "=" character in the string.

  • Some reference URLs captured might be missing or confusing. For more information on how this might happen, see "FAQs".

  • If you want to capture additional data beyond what is automatically captured, you can configure the tag to capture custom data (pdata). For more information, see “Capturing Custom Data (pdata)”.

  • These data are always included: If you choose not to capture any custom segment data through the use of pdata, the above segments will still be included.

  • Don't include the data types listed above in custom data (pdata): These data are captured by default, so there is no need to add this type of information as custom data (pdata) in your tag. This includes domain information (URLs).