Getting Started with Conversions API Feed Distribution for Brands

Download the file template by clicking here.

If desired, you can remove any non-required columns that aren't utilized by one of your conversion programs, but you can also leave those columns in the file and not populate them with values.

Transfer your data into the template.

After transferring your data into the file template, delete the second row with the formatting instructions.

Save the file as one of our allowed file types (.csv, .tsv, .psv, or .txt).

From the navigation pane, select Data Management → Tables and Views.

Click Create and select Create Table.

On the Select Intended Use step, select CAPI Event Feed. Then, select the workflow type based on which identifier type in the file you want LiveRamp to process:

Enter an import configuration name and an optional description.

Click Next.

From the Select Data Source step, fill out the following fields:

1. GCS Bucket or Data Source: The Google Cloud Storage (GCS) bucket where the data source is located.

2. File or Folder Path: The file path within the above-specified GCS bucket (for example, “/input/liveramp-test-file.csv”).

3. Files are encrypted: If your files are encrypted, select this option and enter the path to the non-encrypted files in the Schema File field.

4. Format: CSV or Parquet.

5. Delimiter Configuration: If you are using a CSV file, select Auto Detect or Manual to manually specify delimiters.

6. Number of Rows to Exclude: Enter the number of rows (such as header rows) to exclude. Enter "0" if your file doesn't contain a header.

7. Files to Process: Select which files to scan and process:

   • All Files: All files in the directory will be processed regardless of whether they were already processed.

   • Only Process New Files: Only new files added to the directory from this point onward will be processed.

     Note

     If the table is configured to process only new files, ingestion will begin only after a new file is added to the source location. The table won’t be available for distribution until a new file is detected and ingestion is complete.

   • Backlog and New Files: New files and existing files in the directory which have not been processed will be processed.

Click Next.

Enter a name for the table and an optional description. Click Next.

For passthrough (No Identity Matching) workflows, select the input field that contains the PII to pass, and the hashing method to apply.

Click Next. You may skip step 10.

The Configure Identity Resolution step lets you define which input fields to match or transcode on. The Import Optimizer generates a list identifiers to match on based on the identifiers in your input file and the selected workflow type.

To review the suggestions: 

1. Confirm each identifier maps to the correct field. Click the arrow on an identifier's row to view its field and make necessary changes.

   

2. For online matching and transcoding workflow, you must provide the relevant Ad Network Account (ANA) ID for the configured identifier.

3. All detected identifiers are included for matching by default. To exclude an identifier, click the More Options menu (the three dots) and select “Delete Identifier”.

   

4. Select the identifier to use to for creating Enterprise IDs.

5. For suggestions that require attention, you must select the identifier field manually, or exclude it from matching.

6. Once the above steps are completed, click Import Optimizer Actions  → Accept Suggestions.

   

In the Data Hygiene and Privacy Transformations step, perform the following actions:

Click Next.

Review your table configuration, and click Create Table.

Remove the end date to leave the end date open-ended.

Under Destination-Specific Settings, enter the required account IDs.

If your destination requires an OAuth authentication, select an existing one from the OAuth Connection dropdown list and click Validate OAuth Connection.

To create a new OAuth connection and validate that connection:

1. From the OAuth Connection dropdown list, select Create New OAuth Connection.

2. From the new window that opens with the platform's sign-in or login screen, enter your credentials and then click Sign in.

Click Validate OAuth Connection.

In the Destination Account Name field, pick a unique and memorable name for this account. We'll suggest one for you but you can use any name you wish as long as it is less than 50 characters in length.

On the Tables and Views page, click the More Options menu () of an event feed asset and select "Distribute Event Feeds".

(Optional) Click Previous and select any additional views you want to distribute.

Click Next.

From the Select Destinations step, check one or more boxes for the CAPI destination accounts you want to distribute the views to.

Click Validate. LiveRamp checks whether your file is missing any fields required by the selected destination platform.

If a row's validation status displays “Incompatible”, hover over the status to see the missing requirement.

When all selected platforms show a validation status of “Compatible”, click Distribute Event-Feeds.

On the Tables and Views page, click the More Options menu () of a shared event feed view, and select "Create Event Feed".

Select a product mapping table or event feed view you want to aggregate against.

If you selected an event feed table in the previous step, only product mapping tables will display, and vice versa.

Click Next.

From the Define Rules step, apply filtering based on the attributes (columns) of the selected CAPI product mapping table.

From the “Include all of the following rules” area:

Click Next.

From the Review Event Feed Views step, you can perform the following actions:

Click Create Event Feed.