Fix diagnostic alerts for conversions with multiple data sources (beta)

Note: This feature is currently in beta. If you’re unable to access this feature, it may not be available to you yet.

Conversions using multiple data sources use additional event data to boost Google tag conversions across Google Ads. When you’ve adopted conversions using multiple data sources, you’ll receive diagnostic alerts to help you identify and address potential setup issues, including data source errors.

Diagnostic alerts

These alerts help identify setup issues that prevent accurate reporting with additional data sources.

Google tag has stopped sending data

This diagnostic appears when your conversions aren’t being counted because your tag stopped sending data. View instructions on how to use Tag Assistant to ensure the tag is correctly installed on your website.

Note: The "Tag has stopped sending data" alert appears with the "Urgent" status when the Google tag that was once sending data has not been sending data in the last 48 hours. The alert is different from the "No recent data" status that appears when no data was ever received from the Google tag. The “Tag has stopped sending data” alert also applies to multiple-source conversions and appears when no data has been received from the tags in conversions using multiple data sources in the last 7 days.

Offline data for <data-source> not found

Check whether the data source exists. View instructions on how to ensure credentials are valid and data sharing permissions are up to date .

Google tag is missing transaction ID

Your Google tag is sending data, but the transaction ID is missing or invalid. Transaction IDs are unique identifiers for each transaction. They help prevent counting the same conversions twice. View instructions on how to update your conversion event snippet to include the missing parameter.

Transaction ID overlap rate was less than 10% for the past 2 days

Less than 10% of transaction_id received from additional data sources were found to overlap with the transaction_id received from Google tag. If the overlap rate between your additional data sources and Google tag is low, identical events could be counted multiple times.

Ensure the transaction ID is unique for every purchase, sent with every tag event, and exactly matches between your tag and additional data sources.

Troubleshooting steps

Check for transaction_id formatting discrepancies: Review the transaction_id setup in your Google tag and additional data sources and look for common formatting errors:
- Prefixes or suffixes: order-12345 vs. 12345
- Case sensitivity: abc-123 vs. ABC-123
- Data type: 12345 vs. 12345.0
- Leading zeros or different lengths: 00123 vs. 123
- Dummy or placeholder IDs: Check for placeholder values like undefined or order_id being passed.
Investigate partial transaction_id coverage from the Google tag: A low overlap rate can occur if the tag only intermittently collects transaction_ids. Ensure that transaction_id is sent on every tag ping. Common root cause is due to incorrect tagging logic on a subset of conversion pages. Learn how to set up transaction IDs for website conversions .

Severity levels of diagnostic alerts

The severity levels of diagnostic alerts are the same across all platforms, regardless of where they appear.

Excellent

“Excellent” indicates that conversions using multiple data sources are active and there’s no indication of any issues affecting campaign performance.

Good

“Good” indicates that your multiple-source conversion setup is active, but at least one recommendation is given to help enhance performance. For example, you may only be passing one conversion identifier. Passing more would give you a better measurement of your conversions.

Needs attention

“Needs attention” indicates that conversions using multiple data sources are active and receiving some data, but there are issues affecting campaign performance that need attention. For example, you’re sending a conversion value with your tag, but your offline data isn’t sending a conversion value, which can negatively impact your bidding performance.

Urgent

“Urgent” indicates that there are conversions using multiple data sources that have urgent issues affecting campaign performance. For example, your conversions using multiple data sources may have received offline data at one point, but are now missing offline data sources, or you might not have transaction ID matches between your online tag and offline data.

Non-biddable trial period

When setting up a biddable multiple-source conversion action in Google Ads, your additional source conversions will enter a 14-day trial period. During this period, data from your additional source will be used for reporting purposes, including providing estimated overlap rates and uplift data in diagnostics, but it will not be used for bidding. Your existing tag-source conversions will continue to be biddable as usual.

Throughout the 14-day trial period, you’ll also receive multiple data source conversion diagnostic alerts to help identify and resolve any set up or data quality issues without additional data uploads impacting bidding. These alerts are designed to provide clear guidance to help you quickly understand and fix any problems.

At the end of the 14-day trial, the multiple data source conversions will automatically become biddable, regardless of any diagnostic alerts. The actual conversion uplift will then be visible.

When filtering your diagnostics for a single conversion action, if that conversion action is currently in a trial period, you'll notice the following message until the trial period is over:

“The additional data source you recently connected to this web conversion action becomes biddable on {month, day}. During this time, diagnostics for this conversion will only be used to surface errors to identify any potential impacts to bidding.”

Once the trial period is over for that conversion action, the message will disappear.

Important

The trial period begins when the first offline data upload is received for each conversion action.
Diagnostic alerts will be provided throughout and after the trial period ends.
Once the trial period concludes, or if not in a trial period, all valid and net-new user-uploaded data will flow to both reporting and bidding.

Was this helpful?

How can we improve it?