How to Check Google Ads Data Manager Diagnostics

To check whether Google Ads Data Manager is receiving and matching conversion records, use connection diagnostics in Google Ads if they are available in your account, or use request- and record-level diagnostics for Data Manager API uploads. These are separate checks. Follow the path that matches your setup, then compare one purchase ID in your order system, upload, and Google tag. Google’s connection diagnostics are in gradual rollout, so a missing panel does not mean a connection is healthy.

What Google’s recent announcements establish

Google’s September 10, 2026 announcement described built-in Data Manager diagnostics for identifying data issues and announced the Data Manager API as a unified setup for connecting and activating audiences and measurement. The announcement is useful context, but it does not establish that diagnostics—or a particular integration—are available or working in every account. Google’s Data Manager connection diagnostics guidance says the feature is gradually rolling out.

If you rely on offline conversion imports or enhanced conversions for leads uploads, check Google’s enhanced conversions settings update. Google says migration to the Data Manager API was to begin June 15, 2026, with the specified uploads blocked in the Google Ads API. That timeline does not confirm that your own connector or integration migrated successfully.

Check connection diagnostics in Google Ads

If the connection diagnostics feature is available in your account, inspect the affected Data Manager connection and look for its status, issue details, and recommended actions. Google documents statuses such as Needs attention and Urgent. Use the displayed issue and action as a starting point for investigation; diagnostics present information for you to review, not an automatic repair.

Identify the connection that supplies the conversion data you are checking.
Review its diagnostic status and open any issue details or recommended actions.
Check when the source or connector last imported data. If the interface does not show enough history, review the connector’s run history or available integration logs.
Record the issue, affected source, last import time, and relevant error details before changing the setup.

If you cannot find a diagnostics panel, do not treat that as a clean bill of health. The feature may not have reached your account. Check import recency and the connection or connector’s available logs instead. If your integration sends event uploads through the Data Manager API, use the separate API diagnostic path below.

Google also documents an overcount warning when fewer than 10% of transaction IDs matched between the Google tag and an additional data source over the past two days. If that warning appears, compare the IDs for uniqueness and exact formatting before changing campaign settings.

Check Data Manager API uploads separately

For event uploads through the Data Manager API, a successful upload request is not the end of the check. Google’s Data Manager API diagnostics guide calls for checking destination processing and record-level results:

Save the request ID returned for the upload. Keep it with the request time and the source or batch it represents.
Wait at least 30 minutes before the first status check. Google says processing can take up to 24 hours.
Check each destination and continue polling until it reaches a final status.
Inspect counts, warnings, and errors as well as the destination status. Warnings mean portions of the data were ignored. A SUCCESS status can still include warnings; PARTIAL_SUCCESS means some records failed.

Use the request ID to follow the specific upload, then investigate any warning or error at the record or destination level. A successful request or SUCCESS destination status alone does not show that every record or field was accepted and used.

Compare transaction IDs across the purchase, upload, and tag

For purchase deduplication, Google says the transaction ID should be unique for each purchase and consistent between the Google tag and the additional Data Manager data source. A prefix, suffix, or other formatting difference can prevent a match. Google’s transaction ID guidance also explains how to use Tag Assistant to verify the ID sent with a tag conversion.

Hypothetical example: A store’s order record is 1058. Its Google tag sends WEB-1058, while its Data Manager upload sends 1058. Those values refer to the same order in the store’s system, but they are not exact matches. That mismatch can obstruct deduplication. Inspect the uploaded value in the source record or upload payload, and inspect the tag’s conversion event in Tag Assistant. Then check where the connector adds or removes the WEB- prefix.

For a controlled test or known purchase, the expected check is the same unique transaction ID—with the same formatting—in the source order, the additional data source, and the Google tag event. A matching ID alone does not prove that every other field or processing step is correct.

Trace one conversion before drawing conclusions

Choose one known purchase record and trace it through the systems that handle it. Compare its source order details with the upload value, then check the API request and destination results if the integration uses the API. Review any connection-level issue in Google Ads and use Tag Assistant to verify the tag’s transaction ID on a test conversion.

Use this checklist to keep the investigation concrete:

Source order: Is the purchase ID present and unique for that order?
Upload: Does the record contain the same ID, with exactly the same formatting?
API evidence, if applicable: Did you save the request ID, wait before checking, and review final destination status, counts, warnings, and errors?
Connection evidence: Are there Data Manager diagnostic statuses, issue details, recommended actions, or a recent import time to investigate?
Tag evidence: Does Tag Assistant show the expected transaction ID on the tag conversion?

Do not require an upload’s record count to equal the conversions shown in Google Ads. Conversion-action counting, attribution, and processing can affect what appears in reporting, so investigate a discrepancy with the relevant record and diagnostic evidence rather than treating the totals as a one-to-one test.

Choose the next step from the evidence

The source and tag or upload IDs differ: Correct the source mapping or identifier formatting, then verify the same record again.
The connection shows an issue or imports are stale: Follow the displayed recommendation where available, and investigate the connector’s run history or logs for the affected import.
An API destination is delayed, partial, or has warnings or errors: Follow the request ID and inspect the affected destination and records before concluding that the upload was fully processed.
You have a diagnostic but no evidence of a data mismatch or campaign effect: Gather the missing account and conversion-record evidence. Do not change bidding strategy solely because a diagnostic appeared.

Have you found a transaction-ID mismatch between a Google tag and an additional conversion data source? Which evidence helped you locate it? Don’t post customer or account data.

Sources

Editorial note: AI assists with research, drafting and automated checks. Sources are linked so you can verify the guidance. Platform requirements can change; confirm the details that apply to your setup.