Skip to main content

Implementing LiveRamp’s Real-Time Identity Service Tag

Abstract

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.

For more information, see this article in the LiveRamp Identity documentation site.

More Information About RampIDs

RampIDs are LiveRamp’s people-based, cross-device identifiers that you’ll use to communicate with LiveRamp. A RampID is a privacy-safe, online representation of an individual, built by deterministically merging offline PII (personally identifiable information, such as email address, name, postal address, and phone number) and matching to cookies, mobile device IDs, and proprietary platform IDs.

See the articles below for more information about RampIDs: