File-Based Recognition Workflow

When you send LiveRamp a file to process via our File-Based Recognition (FBR) workflow, we replace the input identifiers (such as PII, cookies, mobile device IDs, CIDs, etc.) with their associated RampIDs and return the file to the location you specify. Unlike files that go through our Onboarding workflow, LiveRamp does not ingest any identifiers or segment data and does not create segments in an FBR workflow. For this reason, you can think of the FBR workflow as “file in, file out”.

You can view the recognition rate (the percentage of rows from your file we matched to) in the Connect UI (see the “View FBR Stats in Connect” section below). The recognition rate for a file is calculated by dividing the number of matched rows by the total number of rows.

Once your file contains RampIDs, you can then tie the original dataset to any other source you have linked to RampID. General use cases for this workflow include measurement, targeting, exposure, conversion, and more.


Customers considering using an FBR workflow for measurement might be interested in the Measurement courses in the LiveRamp University section of LiveRamp Community.

To start utilizing an FBR workflow, contact your LiveRamp representative.


When you first utilize an FBR workflow, the LiveRamp Implementation team will work with you to set everything up. If you need to add an additional data feed for a new set of files after your initial implementation, follow the instructions in "Set Up a New File-Based Recognition Data Feed."

FBR Workflow Example

Let’s say you send us a file that contains email addresses and segment data for an FBR workflow.

FBR Workflow example input-3h0.jpg

We perform automated privacy checks, match each line to a corresponding RampID, remove the email address field and randomize the row order.

FBR Workflow example step two new-V7I.jpg

Send your FBR Data to LiveRamp

Create Files

Make sure to properly format your files so that we can process them quickly. It’s especially important to keep the following key guidelines in mind:

  • Ensure your file contains identifiers that LiveRamp can recognize. A list of these identifiers can be found in our content on known identifiers and anonymous identifiers.

  • Once you decide on a format for your initial files, the column headers for the identifier columns that we use for matching must stay exactly consistent in subsequent files.

  • If you’ll be sending files with different identifier types (for example, if you’ll be sending both files with PII and files with mobile device IDs), let your LiveRamp Implementation Manager know. Otherwise, we will assume that all files contain the same type of identifiers.

  • LiveRamp's file limits.

  • For files containing PII, do not include unique values (a value that appears in only one row) in a segment data column. If a unique segment value is found in a row in a PII file, LiveRamp will not be able to provide the unique value next to RampIDs to maintain the anonymity of the RampIDs. In certain cases where unique values must be included in the output file, work with your LiveRamp representative to obtain a privacy approval from our team.


New Customers: Let your Implementation Manager know how many distinct file formats you’ll be sending (formats with different column headers and different identifier data fields).

Send Files to LiveRamp

Once you’ve decided on your distinct file format, you can send your data to us in a number of ways. In general, we recommend that you either upload your data via SFTP or have us retrieve it from an AWS S3 bucket.


New Customers: Let your Implementation Manager know which file delivery method you’d like to use.

After you've uploaded your file or files, you'll need to wait 1-3 days for us to process the data before the output file will be available for pickup.

RampID Options for FBR Output Files

There are two output options available for FBR files:

  • One RampID per record

  • All available RampIDs per record

In many situations, receiving all available RampIDs is preferable. However, there are some situations (like attribution use cases, where accuracy and precision are the biggest concerns) where you might prefer to receive one RampID per record.

For customers who choose to receive one RampID per record, when there are multiple maintained RampIDs associated with the record, one is selected at random and used consistently.

If your use case emphasizes reach and frequency, you might prefer to receive all available RampIDs for each record. With this option, LiveRamp generates a grouping indicator for each input row and adds that to each row in the output file that contains an associated RampID (see “Receiving All RampIDs Per Record” for more information).

In most workflows, it's best to receive all RampIDs per record, to make sure your data can overlap with other data sets at the highest rate possible.

For more information on output file options and the types of RampIDs you might receive, see “File Output Options for File-Based Recognition Workflows”.

FBR File Delivery Options

After 1-3 business days, the output file will be available for pickup. Typically, LiveRamp drops the output files into an SFTP we set up for you. We do have other options available for delivery, including AWS S3, your operated SFTP, GCS, and Microsoft Azure Blobs. See “Set Up LiveRamp File Deliveries” for more information. Work with your LiveRamp representative to set up your preferred delivery location.

Now that your file contains RampIDs, you can now tie the original dataset to any other source you have linked to RampID. General use cases for this workflow include measurement, targeting, exposure, conversion, and more.

View FBR File Info

For each FBR file we process, you can view the following info on the Files page in Connect:

  • The date the file was received

  • The status of the file

  • The number of rows in the input file

  • The recognition rate (the percentage of valid rows in the file that were matched to a maintained RampID)

To navigate to the Files page, click Files in the Connect navigation menu and then select your FBR audience from the Audience dropdown.

You can also open a details panel that displays additional information. See "Check the Status of an Uploaded File" for more information.


Since LiveRamp does not store any segment data for this workflow, there is no data manipulation within the Connect UI.

Set Up a New File-Based Recognition Data Feed

A "data feed" is a set of files you send through a File-Based Recognition (FBR) workflow. If you want to set up an additional data feed through an FBR workflow after your initial implementation, follow the steps below to create a case in the LiveRamp Community portal with the required information.

Using the info you provide, the Technical Operations Manager working on your ticket will determine if the new data feed requires a new audience.

  1. From the Connect Welcome page, click the Go To LiveRamp Community tile.

  2. From the LiveRamp Community portal, select the Support tab.

  3. From the Measurement Product Quick Cases, click the File Based Recognition tile to take advantage of a case template with most needed info prefilled.

  4. In the Description field, use the following descriptions to populate the template:

    • Identifiers: Specify the type of identifiers your data uses:

      • Offline Identifiers: Email, Name and Postal, Phone

      • Online Identifiers: Cookies, Mobile IDs, Custom Platform IDs from <insert platform>"

      • RampIDs

    • Output option: Specify the type of output you would like for your File-Based Recognition file: Multiple RampID or Single RampID (see "RampID Options for FBR Output Files" for more information).

    • Provider: Specify the entity that will be providing the files to LiveRamp for this workflow (Your company, your partner, etc.).

    • Upload method: Specify which method the provider will use to send us files for the new feed (see "Getting Your Data Into LiveRamp" for a full list of LiveRamp's upload options).

    • Upload path: Specify the full path on the server that the files are going to be uploaded to (i.e., "s3://liveramp/imports/File Based Recognition files" or "/uploads/new_file_based_recognition_data_feed/").

    • File name: Specify the expected file name(s) for the first file.

    • Recipient: Specify the entity that LiveRamp should send the File-Based Recognition output files to.

    • Delivery method: Specify which delivery method LiveRamp should use for sending the output files to the recipient (see "Set Up LiveRamp File Deliveries" for a list of LiveRamp's delivery options).

    • Delivery path: Specify the full path on the server that the files will be delivered to (i.e., "s3://liveramp/imports/FBRfiles" or "/uploads/FBRfiles/").

    • Notification email addresses: Specify the email address(es) you would like us to use for the email notifications that File-Based Recognition files have been delivered.

    • CC list: Specify the email addresses for any additional people you would like to have CC’d on this support ticket.

    • Additional info: Include any additional info that will help us understand the context of your request.

    See the description below for an example of what a populated description might look like:

    1. Identifiers: Offline - Email Addresses
    2. Output option: Multiple RampID
    3. Provider: Company A
    4. Upload method: LiveRamp SFTP
    5. Upload path: /uploads/FBRfiles/
    6. File name: /uploads/FBRfiles/firstFBRfile.csv
    7. Recipient: Company B
    8. Delivery method: S3 Bucket
    9. Delivery path: s3://liveramp/imports/FBRFiles
    10. Notification email addresses:,,
    11. CC list: No thanks!
    12. Additional info: We are trying to have this setup by Monday (5 days away) Please let me know if you need any additional info to get this new audience started. Thank you for your help!
  5. Click SUBMIT.


Once we've aligned with you on the required information, your new data feed will be set up in 3-5 days. After set up, new files for this feed will be processed in 1-3 days.