Matchbacks

A Matchback lets you see exactly which records in a given file would be successfully delivered to a particular destination at the time of the request.

Note

To purchase a Matchback, contact your LiveRamp representative and provide the information listed in "Setting Up Matchbacks".

Caution

Most premium platforms, and a few other specific destinations, do not support Matchbacks. Contact LiveRamp for more information on which destinations support Matchbacks.

Note

A Matchback provides record-specific match information. To get an estimate of the overall match percentage for a file, you can generate a Match Report (see “Match Reports” for more information).

LiveRamp performs the following operations to the data in your original file to create the Matchback file it delivers back to you:

  • A "Row #" column is added to correspond to your original row numbers, if desired.

  • A destination column is added to indicate which rows would be delivered to that destination ("true" for any row that would be delivered and "false" for any row that would not be delivered).

  • All PII (personally identifiable information) is removed.

  • Any customer-specified customizations are performed (such as file splitting, hashing, or encryption). Note: See “Matchback File Options” for more information.

Note

See "Setting Up Matchbacks" for the information LiveRamp requires to correctly configure your Matchback files.

Here's an example of a hypothetical input file:

Source_File_Example.jpg

Here's what the file returned for a Matchback performed on this input file for the destination MediaMath might look like:

Matchback_File_Example.jpg

After you've provided the information needed to set up Matchbacks, the Matchback process includes the following basic steps:

  1. You upload a file (see “Getting Your Data Into LiveRamp” for more information).

    Note

    Matchbacks can be set to run either on all files uploaded to a designated Matchback directory, or to all files for a particular audience.

  2. LiveRamp simulates the delivery of the file to the specified destination or destinations.

  3. LiveRamp delivers a file to you that includes all original non-PII data and an additional “True/False” column that indicates which records would be successfully delivered to a particular destination.

    Note

    For multiple destinations, LiveRamp delivers a separate file for each destination.

See "Matchback Example" for an example of what the file LiveRamp returns to you might look like.

A number of options are available for the Matchback file LiveRamp delivers back to you during the Matchback process.

Note

These options are chosen during the initial Matchback configuration with your LiveRamp representative, and apply to all Matchback files for a particular audience or directory. See "Setting Up Matchbacks" for more information.

LiveRamp can perform the following operations on the Matchback file before delivery:

  • Files that are larger than a customer-specified threshold can be split into separate files.

  • File headers can be customized.

  • Column entries can be hashed.

  • Files, or individual columns within files, can be encrypted.

  • Files can be compressed.

  • File names can be customized.

A Matchback lets you see exactly which records in a given file would be successfully delivered to a particular destination at the time of the request. See "Matchbacks" for more information.

To purchase a Matchback, contact your LiveRamp representative and provide them with the information listed below:

  • The LiveRamp audience name for the audience you wish to run Matchbacks on

  • The destinations you want a Matchback run for (provide the exact destination account name), and the types of devices IDs you want included (i.e., iOs devices, Android devices, cookies, or all of the above).

  • Whether a Matchback should be run for all files imported into the audience, or only for specific files.

  • Whether you want the file to contain a "Row #" column with row numbers that correspond to your original rows.

  • Whether you want any custom operations to be performed on your Matchback files. See "Matchback File Options" for more information.

Note

Turnaround time? It takes about 5-7 days for LiveRamp to set up and deliver the initial Matchback file. For subsequent files (those not requiring any setup adjustments), it takes up to 3 days after the new file has been uploaded for LiveRamp to process and deliver the Matchback file.

See "Matchback Example" for an example of what the file LiveRamp returns to you might look like.

  • All files used to generate Matchbacks must contain PII (personally identifiable information).

  • It takes about 5-7 days for LiveRamp to set up and deliver the initial Matchback file. For subsequent files (those not requiring any setup adjustments), it takes up to 3 days after the new file has been uploaded for LiveRamp to process and deliver the Matchback file.

  • The order of records in a Matchback file will not match the record order of the original file, but a "Row #" column can be added to the file with row numbers that correspond to your original rows.

  • For privacy reasons, no PII is returned in a Matchback file.

  • All anonymous identifiers included in the original file (such as customer IDs or IdentityLinks) will be returned in the Matchback file.

  • For all subsequent files used to generate Matchbacks, the headers and column layout must exactly match the first file uploaded (whether to a particular audience or a designated Matchback directory).

See "Matchback File Options" for information on file customization options (including file splitting, headers, hashing/encryption, and compression).