Reseller Onboarding

Data onboarding with LiveRamp activates offline first-, second-, and third-party data, as well as contextual data, in and across any marketing channel. Simply put, LiveRamp enables marketers to activate their offline CRM and transaction data in the online ecosystem. This allows for people-based marketing across all digital applications.

LiveRamp resellers offer their reseller clients premier LiveRamp services, enabling their reseller clients to make offline data actionable online. One implementation of this service is provided through our Connect UI; these instructions will help you get started with this option.


Want to implement through your UI? Resellers can also offer LiveRamp’s capabilities within their own UI through the use of the LiveRamp Quick Onboard API. Contact your LiveRamp representative to learn more.

  1. Before your clients’ data can be onboarded, you must set up the necessary reseller client customer accounts in Connect.

  2. Once the account has been created, create an audience for your client. Make sure you are in the correct account, and then follow the instructions in "Create a New Audience".


    To switch between your reseller accounts, click anywhere in the account switcher area and then use the account drop-down list to change from one account to another. If you have a large number of accounts, you can also use the search bar to locate the desired account.

  3. Once you have set up the necessary customer account, you have the option of having your reseller client manage the rest of the onboarding process or you can do that for them.


Note sure which option to use? Consult your LiveRamp Account Manager to help understand which onboarding option is best for you.

In Connect, resellers and reseller clients both have “customer accounts.” Via customer accounts, users can upload their offline data and distribute to the end destination.


Only users with “Admin” level permissions can add reseller client customer accounts: Contact your LiveRamp representative if you need your permission level changed.

Understanding LiveRamp’s Customer Account Hierarchy

Customer accounts are structured in a hierarchy:

  • The reseller’s customer account (the “parent account’): users of this account have access to the reseller’s customer account, as well as all reseller client customer accounts

  • Reseller client customer accounts (“child accounts”): users of these accounts only have access to their specific customer account

This hierarchical structure enables resellers to manage all their clients’ customer accounts in Connect, while making sure clients only have access to their own customer account and data.

Setting Up a Customer Account

To set up a customer account for a reseller client:

  1. Log in to your parent reseller customer account in Connect.


    If you haven’t received login credentials: Contact your LiveRamp Account Manager.

  2. Follow the steps in “Add a New Reseller Client”.


    To give a user the ability to upload files via SFTP, enter their email address in the “Send SFTP credentials to” field, which will send an email to that user (this can only be done for one user for each reseller client account).

  3. Switch to the new account you just created by clicking anywhere in the account switcher area and then using the account drop-down list to change from one account to another.

  4. Create an audience for the reseller client by following the instructions in "Create a New Audience".

Users you add will receive an email with directions for how to access Connect. These credentials will expire in 24 hours.

After the necessary reseller client customer account and audience have been created, either you or your reseller client can handle the onboarding process, which involves uploading data into LiveRamp and distributing data to the end destination. See “Onboarding Guide for Reseller Clients” for complete instructions.

LiveRamp’s match rates for offline to online onboarding are typically 30-60%, depending on the type and quality of uploaded information. The onboarding process takes 2-7 days depending on data volumes and workflows.

Files for reseller clients must follow a specific format to ensure successful file uploads.

All files must be single-segment files, meaning they only contain the identifiers for all the consumers you want in a particular segment (and no segment data fields). These types of files are sometimes also referred to as "file-wide fields" because they create a field that contains all of the members in the file.

For example, if you want to have a segment of all the dog lovers in your CRM, you would create a file containing only the PII identifiers of those consumers and name the file with the desired name of the segment to be created. Do not include a "dog lovers" column.

Once the file is ingested and processed, a “dog lovers” segment is created in Connect with all the consumers in your uploaded file.

Guidelines Overview

In addition to our standard file formatting guidelines, reseller client files must meet the following guidelines:

  • Column-based files only

  • PII-based data only (no online data files)

  • No segment data fields (only identifier data fields)

  • Allowed file formats are CSV, TSV, or TXT (do not upload Excel files)

  • Name the file with the name of the segment you want to create (in addition to our file naming guidelines)

  • Files can be compressed and/or encrypted (see “Finalizing Files for Uploading” for more information)

  • Must contain the following PII identifier fields only (no segment data fields), with these exact headers in this exact order:



    • ADDRESS1

    • ADDRESS2

    • CITY

    • STATE

    • ZIP

    • EMAIL1

    • EMAIL2

    • EMAIL3

    • EMAIL4

    • PHONE1

    • PHONE2

  • If you don't have data for a particular column, include the column and leave the cells empty

To download a .csv file template with these columns and column headers, click here.


Hashing identifiers: To send hashed emails (SHA-256, MD5, and/or SHA-1 hashes) or hashed phone numbers (SHA-1 hashes only), use the existing email or phone columns and headers (no other identifiers can be hashed - see "Hashing Identifiers" for more information). Do not add additional columns or change the column headers.

The first time you send hashed identifiers, make sure the Implementation team is aware so they can import the data correctly.