LiveRamp
What Is LiveRamp?
LiveRamp is a data connectivity platform that helps businesses harness and maximize the value of their customer data. It offers advanced identity resolution services, allowing companies to unify customer data from various sources to create a cohesive and comprehensive view of their audience. LiveRamp's platform facilitates secure data sharing, measurement, and activation across multiple marketing and advertising channels. By leveraging LiveRamp's solutions, businesses can enhance their marketing strategies, improve customer experiences, and achieve better data-driven insights.
What are the benefits of integrating MetaRouter with LiveRamp?
- Achieve anonymous to known user conversion, all within your private cloud, due to MetaRouter's LiveRamp syncs. MetaRouter can keep your CDP, Customer 360, or Data Warehouse customer profiles up to date in real time with increasingly deterministic RampIDs as their user journey progresses.
- MetaRouter can help you enrich LiveRamp's leading identity graph IDs directly into your critical 1st-party behavioral data, ensuring maximum accuracy, addressability and reach.
- Unify best-in-breed website visitor data collection of longitudinal identity to build an end-to-end 360 across offline, authenticated, prospect, and paid media interactions with your customers, enriched with marketplace data enrichment.
- Leverage MetaRouter’s highly secure, server-side pathway for interfacing with LiveRamp’s authenticated endpoint to retrieve Known User RampIDs, hashing them according to your preferences, and leveraging them within your data streams. The RampID can be securely decrypted from the server to be used in integrations.
LiveRamp Identification Syncs
Within LiveRamp, both anonymous and known users are assigned a RampID, which is a unique, anonymized identifier assigned by LiveRamp to unify and resolve an individual's data across different sources and platforms for precise targeting and analytics.
MetaRouter can facilitate anonymous to known integration with the RampID ecosystem. An anonymous user will be identified via cookie syncing, whereas an known user is an individual whose identity has been resolved across various data sources, enabling a comprehensive and cohesive view of their interactions and behaviors. This resolution allows for personalized marketing and improved customer experiences by accurately targeting and engaging the user across multiple channels.
Anonymous User ID Sync
For anonymous users, MetaRouter will follow LiveRamp’s Cookie Syncing Tag process. MetaRouter will fire a cookie sync call to LiveRamp, and then redirect the RampID from the response back to the page to be stored in MetaRouter’s first-party cookie context. This “anonymous” RampID will be enriched into all MetaRouter events, and thus can be used in any downstream MetaRouter integration.
This RampID will represent LiveRamp’s understanding of the user up until the point where that user authenticates or becomes known on your digital property, at which point MetaRouter will re-sync with LiveRamp using the Known User ID Sync documented below.
Known User ID Sync
For known users, MetaRouter will send hashed PII to LiveRamp’s Match Endpoint to fetch a RampID.
One of the following identifiers will be sent to LiveRamp to retrieve the RampID:
Attribute | Description | Supported Input Data Value | Hashed Example |
---|---|---|---|
md5 | MD5 hashed email addresses | 9b7ee2211f2658e9889960d8557086eb | |
sha256 | SHA-256 hashed email addresses | ee3d7fe2d416373c74a38f44d0404635dcc273d41a9b1391a991f | |
sha1 | SHA-1 hashed PII strings (including SHA1 hashed email addresses). | Email Phone Name + Email Name + Phone - Name + ZipCode | c5cc88d3aa51983ac63cb17c14bb08d3 |
If hashed PII cannot be matched to a maintained RampID using LiveRamp's Lookup Endpoint, a derived RampID is returned and persisted as the identifier, ensuring an identifier is provided even when no direct match is found.
The RampID will then be stored in a first-party cookie context and included in all MetaRouter events, and can then be decrypted by the MetaRouter platform server-side to be used in any downstream MetaRouter integration.
Getting Started - From Your LiveRamp Account
- Access Token - To authenticate with the RampID API, an access token is required. Instructions for obtaining an access token can be found here: LiveRamp - Request an Access Token.
- Partner ID - Please reach out to your LiveRamp support team to retrieve your Partner ID.
Getting Started - From Your MetaRouter Account
To capture and persist RampID
for both anonymous and known users, two different sync setups are required.
Anonymous User IDs via LiveRamp Sync
To gather and persist the RampID
for anonymous users, you must add a LiveRamp sync.
- From the Pipelines page, find the pipeline associated with the web property you’d like to add a sync to. Hover over the three dot dropdown and select “Build AJS File.”
- In the Identity Syncs section, select the LiveRamp sync.
- Fill out the following fields:
- Cookie time to live (in days) - 365 days recommended.
- Partner ID - Please contact LiveRamp support for your Partner ID.
- Scroll down and click the Save and Build File button.
- Deploy your AJS file to propagate changes to your web property.
Known User IDs via Enrichment Service Sync
To gather and persist the RampID
from known users, you must add an Enrichment Service sync. If you do not have access to the Enrichment Service sync, please contact MetaRouter support.
- From the Pipelines page, find the pipeline associated with the web property you’d like to add a sync to. Hover over the three dot dropdown and select “Build AJS File.”
- In the Identity Syncs section, select the Enrichment Service sync.
- Fill out the following fields:
- Cookie time to live (in days) - 365 days recommended
- Enrichment Service URL - Please contact your MetaRouter support team for your URL.
- Bearer Token - Please follow the instructions for your Access Token above.
- Scroll down and click the Save and Build File button.
- Deploy your AJS file to propagate changes to your web property.
Additional LiveRamp Documentation
Updated 3 months ago