LiveRamp Tags
See the sections below for information on LiveRamp's tags.
See the articles in this section for information on LiveRamp's tags.
LiveRamp's Client-Side Tags
LiveRamp Client-Side Tags are tags that can be used to log user activities (such as page views or ad views, adding items to a cart, or completing a transaction) and then match the identifiers associated with those activities to RampIDs.
LiveRamp Client-Side Tags are tags that can be used to log user activities (such as page views or ad views, adding items to a cart, or completing a transaction) and then match the identifiers associated with those activities to RampIDs.
The tags can be placed in the following environments, depending on the tag type and the implementation method:
The standard Client-Side Tag (CST) can be placed in advertisements, and web or mobile web environments.
The standard implementation of the Enhanced Client-Side Tag (eCST) can also be placed in in-app mobile, CTV, and OTT environments.
The eCST module for ATS.js implementation of the Enhanced Client-Side Tag can be placed on web and mobile web owned and operated properties.
LiveRamp creates a log file from these activities daily. The log file is either used to create fields and segments in your Connect account (for Activation use cases) or is delivered to you or your measurement partner (for Measurement use cases).
For more information, see this article in the LiveRamp Identity documentation site.
Building a cookie sync with LiveRamp will enable us to match your cookies to other partner cookies, mobile devices, proprietary platform IDs, and RampIDs.
Cookie syncs with LiveRamp leverage standard pixel-based syncing, off of your and/or LiveRamp’s traffic, to build a large pool of shared cookies.
For more information, see this article in the LiveRamp Identity documentation site.
Implementing LiveRamp’s Real-Time Identity Service Tag
Integrations with LiveRamp are built around communicating via RampIDs, our people-based, cross-device identifiers. One way this process can be enabled is via the Real-Time Identity Service (RTIS), a tag that can track website visits and ad traffic. When the tag fires, LiveRamp will return a RampID to your server endpoint, providing you a people-based identifier that can be used for personalization and measurement use cases.
Integrations with LiveRamp are built around communicating via RampIDs, our people-based, cross-device identifiers. One way this process can be enabled is via the Real-Time Identity Service (RTIS), a tag that can track website visits and ad traffic. When the tag fires, LiveRamp will return a RampID to your server endpoint, providing you a people-based identifier that can be used for personalization and measurement use cases.
Note
If you'd like the RampIDs of your web visits to be returned directly back to the browser in a JSON object, talk to your Implementation manager about the RTIS API (rather than the RTIS pixel).
The LiveRamp tag is certified to run on a number of platforms, including Google AdX. There are some platforms where LiveRamp is not certified, such as Facebook or GDN. Contact your technical support representative to learn more.
If you are planning on sending data to LiveRamp for matching to other platforms, a cookie sync or proprietary platform ID sync is required.
For more information, see this article in the LiveRamp Identity documentation site.
Implementing LiveRamp's Real-Time CID Delivery Tag
The Real-Time CID Delivery Tag enables you to receive a CID (your platform’s custom ID) in real time when you pass us a user’s cookie via a tag you implement on your website. This allows you to recognize a website user from anonymous site activity, and can be used for retargeting, site personalization, or measurement.
The Real-Time CID Delivery Tag enables you to receive a CID (your platform’s custom ID) in real time when you pass us a user’s cookie via a tag you implement on your website. This allows you to recognize a website user from anonymous site activity, and can be used for retargeting, site personalization, or measurement.
When the tag fires with the user’s cookie, LiveRamp uses the pseudonymized PII (personally identifiable information) we have associated with that cookie and a mapping you provide that maps your CIDs to your users’ personal information to find the CID associated with that cookie and then pass that CID back to you. All PII is pseudonymized during the matching process.
Real-Time CID Delivery Tags can be implemented via iframe or gif.
For more information, see this article in the LiveRamp Identity documentation site.