For access to LiveRamp’s native applications, first please reach out to your LiveRamp account team or snowflake@liveramp.com
LiveRamp’s documentation gives a detailed overview of the processes required. At a high level, this includes:
Accepting Snowflakes Terms of Service
Installing the desired application(s) to your designated warehouse in Snowflake
Authenticating the application using the credentials provided by LiveRamp
Configuring Metrics and Logging tables to be used by both your organization and LiveRamp for performance monitoring and troubleshooting/debugging
The application comes with an Application Setup Workbook with sample SQL to easily configure the above.
With the application installed the next step is to prepare your data tables from Segment’s Profile Sync process to be called against the applications.
First, you’ll want to determine which identifiers within your tables are eligible for resolution. LiveRamp’s application categorizes identifiers into four buckets, each with a defined input format:
Full PII*:
Name
Postal Address
Email
Phone Number
*Not all of the above are required for every record
Once you have determined the above, you’ll format the input table to the corresponding format detailed here.
Privacy Filters: When preparing PII-based tables, it is important to consider LiveRamp’s privacy filter process. At a high level, these are checks that occur within a job to ensure that the attribute columns (ie non-identifiers) within your input tables do not contain values that are too unique. This is critical to ensure consumer privacy is maintained and to avoid the possibility of reidentification.
The next step will be to specify the variables for the job within the Execution Steps worksheet provided in the app, which includes details such as the target database where the job will run, the associated tables (input data, metrics, logging), as well as defining what the output table should be named.
With the variables set, you’ll then create the metadata table, which gives details on the specific job type to be executed based on the category of identifiers involved.
With the above set, your last two steps are to run the operation and check for the output:
Operation