Skip to main content

LiveRamp Embedded Identity in BigQuery

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

There are two available operations that you can perform using LiveRamp's Embedded Identity in Google BigQuery:

  • Identity Resolution: You can resolve an identifier (a device ID or PII, such as name, address, email, hashed email, or phone) to LiveRamp’s person-based, pseudonymous identifier, RampID. You can also resolve a person-based RampID to a household-based RampID. For more information, see "Perform Identity Resolution in BigQuery".

  • RampID Translation: You can translate RampIDs in one domain to RampIDs in another domain. Translation converts or translates the pseudonymous person-based identifier (the RampID) for use by another party. For more information, see "Perform RampID Translation in BigQuery".

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.

Note

LiveRamp BigQuery Capabilities

LiveRamp’s identity capabilities are available within BigQuery through the BigQuery Entity Resolution Framework. LiveRamp writes the results to a table in your account, enabling you to query the data set from within your own BigQuery environment.

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

I-Big_Query_architecture.png

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

  1. You prepare an input table and a metadata table for the appropriate identity resolution operation in your BigQuery account.

  2. You share read-only access to those tables with LiveRamp’s BigQuery account and you share write-only access to a target dataset in your account where the output tables will be written.

  3. LiveRamp shares a stored procedure with your BigQuery account.

  4. You call the shared stored procedure to initiate the identity resolution operation, referencing your tables.

  5. LiveRamp uses your input and metadata tables to perform the operation and writes the output to a table in your account.

Prerequisites

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 translation operations, if appropriate (permissions can also be revoked at any time by emailing transcodingpermission@liveramp.com).

  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.

    Note

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

Authentication

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.

Note

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 LiveRampIdentitySupport@liveramp.com.

In this section:

LiveRamp's universal, pseudonymous identifier that is tied to devices in the LiveRamp Identity Graph.