Distribution FAQs
See the FAQs below for common distribution questions (in addition to the info in "Troubleshoot Distributions to Destination Accounts").
Keep in mind that distribution typically takes 1-3 days to complete.
For more information on processing times, see "Typical Processing Times for Activation Workflow Operations" and "Typical Processing Times for Data Selling Operations".
Why is my distribution to Google stuck in the "Failed" status?
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 a Google Customer Match destination account: Before activating a Google Customer Match destination account (either a Google Customer Match or a Google Customer Match - DV360 destination account), you must complete the self-service LiveRamp account linking process for Customer Match within the Google Ads UI to map the LiveRamp CMU account 637-789-1275 to your Google Ads advertiser account. Follow these instructions to provide access via Google’s UI.
For a Google Ad Manager destination account: Contact your Google account representative and have them map the LiveRamp DMP account 750-013-0530 to your Google Ad Manager account. For complete instructions, see "Providing Access to LiveRamp".
For a Google Display & Video 360 (DV360) destination account: Contact your Google account representative and have them map the LiveRamp DMP account 750-013-0530 to your Google DV360 account. For complete instructions, see "Providing Access to LiveRamp".
For more information, see “Distribute Data to Google” and "View Delivery Status".
Note
Before creating a support ticket, confirm that you’ve granted LiveRamp access and that your Google account ID listed in the destination account is correct. Once those have been connected, you can resend the active segments or wait until the next delivery.
Why is my distribution to Google Customer Match stuck in the "Queued" 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".
Why is my Data Marketplace distribution to The Trade Desk stuck in the "Queued" status?
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.
What are other reasons my distribution might be stuck in the "Queued" status?
If none of the situations above apply to you, check for these additional issues:
Check that any account IDs are correct.
Check that all distributed segments have counts (segments with no records, including derived segments, cannot be distributed).
Check that you haven't exceeded the recommended destination account limits (typically no more than 1,000 segments distributing and no more than 500 segments added for distribution to the destination account per hour).
Check that you're not trying to distribute a raw field to a destination platform that cannot accept raw fields (for more information, see "Platforms that Do Not Accept Raw Fields").
You can also check the troubleshooting steps in "Troubleshoot Distributions to Destination Accounts".
Where do I find the field to enter the ad account ID for a destination I am distributing to in Connect?
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).
Why am I able to configure a destination account for a particular platform without being required to enter my platform account ID?
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.
Can I see the number of records that we matched after the distribution of the segment 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.
When can I expect delivery stats to be populated at platform?
It typically takes 1-3 days after delivery has been completed for delivery stats to populate at the platform.
Note
Some platforms typically take longer. For example, Google often takes up to 7 days and Salesforce often takes up to 5 days.
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".