Transcode RampIDs Using a File-Based Recognition Workflow
Every RampID has a partner-specific encoding to ensure the security and privacy of our partner's data. You can use the File-Based Recognition workflow (FBR) to convert RampIDs from one partner encoding to RampIDs in another partner encoding. Unlike files that go through our Onboarding workflow, LiveRamp does not ingest any identifiers (other than for the purpose of transcoding) 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".
For more information on transcoding concepts, see “Identity Translation”.
Transcoding RampIDs using an FBR workflow requires a separate contract. Contact your LiveRamp representative for more information.
Set Up a New FBR Transcoding Workflow
When setting up a new FBR workflow for transcoding, you’ll need to give the following information to your LiveRamp representative:
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 "Setting 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.
Transcoding partner: The name and encoding domain of the partner whose domain you want to transcode RampIDs to.
Format the Input File
See the sections below for information on formatting the input file for transcoding.
Input File Formatting Guidelines
Transcoding input files should be formatted as CSV files. When creating input data files, follow these additional guidelines:
Include a header row in the first line of every file. Files cannot be processed without headers.
You can name your columns however you want, but every column name must be unique in a table.
Once you decide on a format for your initial files, the column headers must stay exactly consistent in subsequent files.
You can include additional columns containing attribute data for each consumer as long as the file stays within our file limits and the data meets our data restrictions.
File Format Example
See the table below for an example of how to format an input file.
Column | Example | Description |
|---|---|---|
RampID | XYT001k0MS00MDc1LUI4NjEtMjlCOUI0MUY3MENBCgNjVGQjE0MTMtRkFBMC00QzlELUJF | RampID (maintained or derived) for translation. |
[Attribute Data Field Name] | Favorite Pet | You can include additional columns with attribute data on the consumer associated with the RampID. |
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.
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 in your delivery location.
Note
If you don't see the file after 3 days, use the Troubleshoot File Delivery / Output for Existing File-Based Recognition Workflow quick case to create a support case.