Skip to main content

Troubleshoot Distributions to Destination Accounts

Since each destination platform takes some time to ingest the data that we deliver to them, you should give the destination at least 3 days to have your data ready for use on their platform after delivery.

Note

It typically takes another 1-3 days after the data appears in the destination platform for stats to calculate and populate within Connect. You can view the delivery status in Connect.

For distributions through the Facebook Direct integration, make sure the steps to add LiveRamp as a partner in Facebook have been performed for that Ad Account ID. See "Troubleshooting Distributions to Facebook Direct Destination Accounts" below for more information.

For distributions to Viant or Jivox, there is an additional step that LiveRamp needs to be performed before segments can be distributed. If that hasn't been done already, create a support case (see "Using the LiveRamp Community Portal" for instructions).

If you've had LiveRamp enable the ability for you to resend all active segments from the Connect UI, you can try resending the active segments and waiting 3 days to see if that solves the problem. See "Resend Active Segments" for more information.

You might also check that the destination account is still active by following the instructions in "Edit or View Destination Account Settings". If the destination account in inactive, set it to "active" and revise the end date (if necessary).

If you still don't see your data after that time, you can share the delivery information by following the instructions in “View Delivery Job Status for a Destination Account”. We recommend sharing the following with the platform:

  • For batch file deliveries, provide the platform with the file name(s) associated with the job.

  • For streaming (API) deliveries, provide the platform with the timestamp of when the job was delivered.

If the platform doesn’t see the delivery, create a support case (see "Using the LiveRamp Community Portal" for instructions).

Caution

In most cases, the company that distributed the data will need to troubleshoot the delivery with LiveRamp.

When creating a support case, it helps to provide the job number for the delivery (see “View Delivery Status” for more information on finding the delivery job number).

In cases where the platform needs to see the segment IDs, you can download the taxonomy to get those segment IDs.

Troubleshooting Distributions to Facebook Direct Destination Accounts

For distributions of first-party data through a Facebook Direct destination account, you must give LiveRamp "Manage campaigns" access to the Ad Account being delivered to by adding LiveRamp as a partner in Facebook. Once that's been done, create a support case so that LiveRamp can complete the configuration. See "Add LiveRamp as a Partner in Facebook" for complete instructions.

If these steps haven't been done, any distributions to Facebook Direct destination accounts that use that Ad Account ID will fail.

Troubleshooting Distributions to Destinations that Require OAuth

You might need to perform additional steps to troubleshoot distributions to destinations that require OAuth authorization.

If your login credentials at the platform change (such as your email address changes), you will need to reauthenticate your connection with your new credentials. See "Reauthenticate an OAuth Connection" for more information.

Occasionally a previous OAuth authorization might become unauthorized (either due to actions on the destination platform end or due to someone inadvertently unauthorizing LiveRamp), which will cause the delivery job to fail. Perform the authorization again and then create a support case to resend the data. For information onthe steps to take to perform authorization, see "Activate a Destination Account for OAuth Destinations."