Perform RampID Identity Resolution in Databricks

Perform the following steps to perform RampID identity resolution in Databricks:

See the sections below for information on performing these tasks.

An input table needs to be prepared for each identity resolution operation.

When creating tables, keep the following guidelines in mind:

See the section below for suggested input table columns and descriptions.

An output table is created when you run the operation. For an example, see the "View the Output Table" section below.

A metadata table can be reused for multiple operations.

To create the metadata table for PII resolution, update the following variables in the sample SQL shown below and then run the SQL:

The metadata table configures how LiveRamp processes your input. Create exactly one row in the metadata table for the job (it does not accept multiple job configurations).

CREATE TABLE <catalog>.<schema>.pii_meta_table (
    client_id       STRING,
    client_secret   STRING,
    execution_mode  STRING,
    execution_type  STRING,
    target_columns  STRING,
    limit           INT
);

INSERT INTO <catalog>.<schema>.pii_meta_table VALUES (
    '<your_client_id>' as client_id,
    '<your_client_secret>' as client_secret,
    'resolution' as execution_mode,
    'PII' as execution_type,
    '{"name":["FIRSTNAME","LASTNAME"],"streetAddress":["ADDRESSLINE","ADDRESSLINE2"],
      "city":"CITY","state":"STATE","zipCode":"ZIPCODE","phone":"PHONE","email":"EMAIL"}' as target_columns,
    1 as limit
);

'{
  "name": ["<first_name_col>", "<last_name_col>"],   // up to 4 columns
  "streetAddress": ["<address_line1_col>", "<address_line2_col>"],  // up to 10 columns
  "city": "<city_col>",
  "state": "<state_col>",
  "zipCode": "<zip_col>",
  "phone": "<phone_col>",
  "email": "<email_col>"
}'

'{
  "name": ["FIRST", "LAST"],
  "streetAddress": ["ADDR", "ADDR2"],
  "city": "CITY",
  "state": "ST",
  "zipCode": "ZIP",
  "phone": "PHONE_NUM",
  "email": "EMAIL_ADDR"
}'

Add your input table and metadata table to a Delta Share and grant access to LiveRamp's Databricks account.

DECLARE OR REPLACE VARIABLE share_name STRING DEFAULT 'testing_share';
DECLARE OR REPLACE VARIABLE catalog_name STRING DEFAULT 'testing_catalog';
DECLARE OR REPLACE VARIABLE schema_name STRING DEFAULT 'input_schema';
DECLARE OR REPLACE VARIABLE pii_input_table STRING;
DECLARE OR REPLACE VARIABLE pii_meta_table STRING;


SET VAR pii_input_table = catalog_name || '.' || schema_name || '.pii_input_table_synthetic';
SET VAR pii_meta_table = catalog_name || '.' || schema_name || '.pii_meta_table_synthetic';


EXECUTE IMMEDIATE 'CREATE SHARE ' || share_name;


EXECUTE IMMEDIATE 'ALTER SHARE ' || share_name || ' ADD TABLE ' || pii_input_table;
EXECUTE IMMEDIATE 'ALTER SHARE ' || share_name || ' ADD TABLE ' || pii_meta_table;

GRANT SELECT ON SHARE <share_name> TO RECIPIENT <recipient_name>;

The identity resolution results will be shared back to the specified recipient as an output table.

Each output table is retained for a maximum of 14 days or until you run another operation (which overwrites any existing output table).

To use the output table in your Databricks account, you’ll need to copy it before you run another operation or within 14 days (whichever comes first).

The PII resolution process passes the input table through a privacy filter which removes the PII and reswizzles the table (in addition to other operations). Because of this, any attributes you need to keep associated with the identifier need to be included in the input table. For more information, see the "Privacy Filter" section below.

Identity resolution of PII provides supplemental match metadata for additional insight into customer data that can provide powerful signals for making decisions based on RampIDs.

For PII resolution, the output table includes the fields shown in the table below.

To minimize the risk of re-identification (the ability to tie PII directly to a RampID), the service includes the following processes when resolving PII identifiers (PII resolution or email-only resolution):