Onboarding Guide for Reseller Clients

If you are the client of a reseller of LiveRamp's services, use the information below to onboard your data.

At LiveRamp, “Onboarding” refers to the process of sending your customer data to digital marketing applications and media platforms. See the appropriate sections below for information on how to onboard your data.


See "Onboarding Your Data" for the key LiveRamp terms you’ll encounter.

The key steps in this process are:

  1. Accessing Connect

  2. Creating files

  3. Uploading files

  4. Distributing data to an end destination

The company that has partnered with LiveRamp to offer onboarding will create an account for you in LiveRamp Connect, our self-service UI. Once the reseller has given you access, you will receive an email with instructions for accessing Connect.


Didn't get the email? If you have not received the activation email, contact your reseller representative.

Reseller clients must follow a specific file 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).

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

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.


At LiveRamp, an "audience" is a way to group your data. Your reseller should have already created an audience for you to upload your data to when they created their account. However, if they haven't created an audience for you, contact your reseller and request an audience be created for your account before attempting to upload your files.

There are two options for uploading files to LiveRamp:

  • Via Connect: For files 500MB and smaller, you can upload them in Connect by following the instructions in "Upload a File via Connect".

  • Via SFTP: Files larger than 500MB need to be uploaded via the LiveRamp SFTP by following the instructions in "Upload a File via LiveRamp's SFTP".


    Make sure to upload files into the appropriate audience subdirectory within the “/uploads” directory. Contact your reseller for SFTP access.

After your file has been ingested and processed (generally within 24 hours), the files will appear in Connect. Each file upload results in a segment being created in Connect with the same name as the file name. You can then distribute those segments to the desired end destinations.

To see if your file has completed processing, hover over MANAGE in the left navigation bar and select "My Files" (see "Check the Status of an Uploaded File" for more information).

To distribute segments to an end destination: