Skip to main content

LiveRamp Embedded Identity in BigQuery

LiveRamp's Embedded Identity in Google BigQuery is available through Native BigQuery functionality.

You can perform RampID transcoding in BigQuery, which transcodes a RampID in one domain to a RampID in another domain. Transcoding converts or translates the pseudonymous person-based identifier (the RampID) for use by another party. For more information, see "Perform RampID Transcoding".


In the future, you will also be able to perform Identity Resolution in Big Query, which will allow you to resolve an identifier (a device ID or PII, such as name, address, email, or phone) to LiveRamp’s person-based, pseudonymous identifier, RampID. You will also be able to resolve a person-based RampID to a household-based RampID.

To perform an operation, you provide an input table that contains the relevant identifiers and a metadata table that contains information on the operation to be performed.


LiveRamp's Embedded Identity in BigQuery is currently in beta. To find out more about participating in this program, email

LiveRamp BigQuery Capabilities

Transcoding capabilities are available within BigQuery through a LiveRamp process, which creates a share to your account, opening up a view to query the reference data set from within your own BigQuery environment.

The LiveRamp application’s architecture is shown in the figure below.


Transcoding capabilities are available through a dataset sharing flow, which involves the following steps:

  1. You prepare an input table and a metadata table in your BigQuery account.

  2. You share that dataset and those tables with LiveRamp’s BigQuery account and then notify LiveRamp.

  3. LiveRamp uses that dataset to perform transcoding and then shares the output table back to your account.


To access LiveRamp in Big Query, you need permission to create BigQuery Tables and Shares.

Enabling LiveRamp Embedded Identity in BigQuery

To enable LiveRamp Embedded Identity in BigQuery, the following tasks must be performed:

  1. You execute an agreement with LiveRamp to access the service, including the permission required between the parties for transcoding operations, if appropriate (permissions can also be revoked at any time by emailing

  2. LiveRamp reviews the use case, including any additional Data Ethics reviews if required.

  3. If you don’t already have credentials for LiveRamp's Identity API, LiveRamp sends you a client ID and a secret for authentication.

  4. LiveRamp sends you LiveRamp’s GCP Service Account project ID.


    You will share the data for transcoding to this LiveRamp account and then the output will be shared back from this account.


The LiveRamp Identity Service in BigQuery relies on the same authentication service as LiveRamp's AbiliTec and RampID APIs (Identity APIs). If you have credentials for those APIs, you can use your previously assigned credentials.


Coordinate with your LiveRamp team to enable those API credentials for use with Embedded Identity in BigQuery.

Authenticating with LiveRamp's BigQuery service requires a call on behalf of the customer to LiveRamp's core services.

Client credentials are used to obtain an access token by passing the client ID and client secret values.

Product Support

For support issues, email