Identity Translation
RampIDs are unique per each LiveRamp client, and you need privacy-safe ways to build strategic data partnerships through data collaborations leveraging LiveRamp's RampIDs.
LiveRamp's identity translation solutions allow you to translate identifiers from one identity space to another.
RampID Translation allows you to translate RampIDs that are encoded in one identity domain into RampIDs encoded in another domain. Translation can be accomplished in several ways:
Via the Transcoding endpoint of the RampID API.
Via the Translation native app in your Snowflake cloud environment (for more information, see "Perform RampID Translation in Snowflake").
Via the translation functionality in your AWS cloud environment (for more information, see "Perform Translation Through AWS Sagemaker").
Via the translation functionality in your Google BigQuery environment (for more information, see "Perform RampID Translation in BigQuery").
Via input files using our File-Based Recognition workflow (for more information, see "Translate RampIDs Using a File-Based Recognition Workflow").
LiveRamp’s Cookie Sync Tag allows you to match your cookies to other partner cookies, mobile devices, proprietary platform IDs, and RampIDs.
RampID Translation Concepts
You can translate RampIDs from your partner encoding (your “native” encoding) to a partner’s encoding, or from a partner’s encoding to your native encoding.
The first 4 characters (after the prefix) in a RampID are known as the "partner encoding", or "encoding", which uniquely identifies the partner.
The "native" partner encoding is the default encoding that you will receive RampIDs in. You will need to know your native partner encoding if you’re going to translate RampIDs from a partner’s encoding to your native encoding.
If you are receiving any RampIDs from LiveRamp (through the Client-Side Tag, the RampID API, Mapping Files, etc.), you can check what your "native" partner encoding is by looking at the first 4 characters (after the prefix) of the RampID.
Note
The RampID prefix can be used to distinguish between a maintained or derived RampID, and between an individual RampID and a household RampID:
A maintained RampID is 49 characters long and starts with "XY." For example, "XY1005wXyWPB1SgpMUKIpzA0I3UaLEz-2lg0wFAr1PWK7FMhs."
A derived RampID is 70 characters long, and starts with "Xi." For example, "Xi1005p_iYcKP7ZlvFwwK9EwR8GKl_VJqIWUhEaAFmHLAjNOQ9b6OQzSkA43XiVFcTYQ9X."
A Household RampID is 49 characters long and starts with "hY."
For more on RampID types and versions, see “RampID”.
Partner’s Encoding to Your Native Encoding
If you’re receiving RampIDs in encodings that are different than your native encoding, you can translate those RampIDs into your native encoding. Each partner encoding you would like to translate from requires an explicit one-time authorization to be performed by our client support team.
When performing translation from a partner’s encoding to your native encoding, include your 4-digit native encoding value in the appropriate location, depending on the translation method you're using,
Your Native Encoding to Partner Encoding
You can translate your RampIDs from your native partner encoding into a partner's encoding.
When performing translation from your native encoding to a partner’s encoding, include your partner’s 4-digit partner encoding value in the appropriate location, depending on the translation method you're using,