Distribution FAQs

Distributions of first-party segments to Google often fail because LiveRamp has not been granted access to deliver data to the appropriate Google account before the destination account was activated in Connect. These segments will remain in a “Failed” status in the Delivery Job Status UI.

This access is provided differently, depending on which type of destination account integration you’re going to activate:

For more information, see “Distribute Data to Google” and "View Delivery Status".

Distributions of first-party segments to Google Customer Match (GCM) often get stuck in the "queued" status because you have attempted to distribute segments that are not based on PII. Because GCM is a Passthrough Activation destination (where LiveRamp passes through hashed PII without performing matching (or any leveraging of our Identity Graph), all data being distributed to GCM must be based on PII. For GCM, this could either be plaintext PII or RampIDs that have been generated from PII (not generated from online identifiers).

For example, if you send cookie-based segments or RampID-based segments where the RampIDs have been generated from online identifiers, the distribution will get stuck in the "queued" status. For more information, see "Distribute Data to Google Customer Match".

All Data Marketplace segments with a programmatic standard CPM of less than $5 being distributed to TTD are priced at a “programmatic hybrid” pricing model that consists of a percentage of media (PoM) rate ("programmatic percentage of media") and a CPM cap. You must provide the designated percentage(s) of gross media spend and CPM caps either via a segment metadata file or individually in the Connect UI (PoM will vary by segment). See "Data Marketplace Pricing Options" for more information.

If a Data Marketplace segment with a CPM of less than $5 is added to a distribution to TTD without having both a programmatic percentage of media and a CPM cap, the delivery job will remain in "Queued" status. If a delivery job is in the "Queued" status for more than 24 hours and you suspect this is due to pricing issues, create a support case following these instructions to have the pricing fields corrected.

See "Distribute Data Marketplace Data to The Trade Desk" for more information.

If none of the situations above apply to you, check for these additional issues:

You can also check the troubleshooting steps in "Troubleshoot Distributions to Destination Accounts".

The field to input the ad account ID can be found when you configure the destination account (see “Activate a New Destination Account” for instructions).

Some of our destination platform integrations do not require any ad account information to be entered. For these destination platforms, we have internal fields that pull destination account information into the destination configurations behind the scenes that determine where the data lands in the platform. These internal configuration fields are not visible in Connect.

Apart from the destinations listed here, you can see the record matches in Connect on the Audience Segments page (from the Connect navigation menu, hover over Audiences and then select the desired audience to navigate to the Audience Segments page for that audience). On the left, select the destination you want to check from the list of available destinations in the Destinations panel. All the segments which belong to that audience and which have been distributed to that audience will be displayed, along with the record matches and destination (device) matches.

These stats typically take 4-7 days to populate after the field or segment has been added to distribution. See “View Matched Reach Stats” for more information.

It typically takes 1-3 days after delivery has been completed for delivery stats to populate at the platform.

Since it usually takes 1-3 days for delivery to complete, you can expect it to take 4-7 days total after distribution has been initiated for stats to populate at the platform.

For more information on processing times, see "Typical Processing Times for Activation Workflow Operations" and "Typical Processing Times for Data Selling Operations".