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 IdentityLinks (IDLs) 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 IDLs, you can then tie the original dataset to any other source you have linked to IDL. General use cases for this workflow include measurement, targeting, exposure, conversion, and more.

Tip

Customers considering using an FBR workflow for measurement might be interested in the recorded session on Measurement Enablement on the LiveRamp University Education Hub.

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 IDL, remove the email address field and randomize the row order.

FBR Workflow example step two new-V7I.jpg

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 here.

  • 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 (i.e. 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 IDLs to maintain the anonymity of the IDLs. In certain cases where unique values must be included in the output file, please work with your LiveRamp representative on a privacy

Note

New Customers: Let your Implementation Manager know how many distinct file formats you’ll be sending (i.e., 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.

Note

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.

There are two output options available for FBR files:

  • One IDL per record

  • All available IDLs per record

In many situations, receiving all available IDLs 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 IDL per record.

For customers who choose to receive one IDL per record, LiveRamp will only send you the IDL with the highest confidence level for each input row that LiveRamp was able to match.

If your use case emphasizes reach and frequency, you might prefer to receive all available IDLs 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 IDL (see “Receiving All IDLs Per Record” for more information).

In most workflows, it's best to receive all IDLs 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 IDLs you might receive, see “File Output Options for File-Based Recognition Workflows”.

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 IDLs, you can now tie the original dataset to any other source you have linked to IDL. General use cases for this workflow include measurement, targeting, exposure, conversion, and more.

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

  • The date the file was received

  • The status of the file

  • The number of rows in the input file

  • The recognition rate

To access file info, hover over MANAGE in the left navigation bar and then select “My Files”. From the Files page, select your FBR audience from the Audience dropdown.

C_FBR-FBR_Workflow-Files_page-vxs.jpg

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