Troubleshooting: data mismatch in Google Ads UI and Coupler.io

If you see that some data returned by Coupler.io is not equal to what you see in Google Ads UI, it may be due to importer misconfiguration or specifics of Google Ads API. Please review possible reasons and steps you may take to ensure you are getting proper data.

1. Data freshness

Performance data, particularly conversion data, may not be available instantly.

Steps to resolve:

  1. Refer to the Google Ads Data Freshness Guide for information on how fresh the data is and how it may affect your reports.

2. Empty report

Report may be empty if all metrics for the selected entity (e.g. Campaign) in defined period are zero.

Steps to resolve:

  1. Ensure that you have selected a period where performance data is expected.
  2. If no data is available for new conversion actions, try adjusting the date range or checking for any reporting filters.

3. Missing custom columns

Custom columns created in Google Ads are not supported by the Google Ads API and cannot be retrieved in reports.

Reference: Google Ads API Documentation

4. Missing some Campaigns, Ads or Keywords in the report 

If a selected campaign, ad, or keyword has no reported performance metrics for the chosen period, it will not appear in the results. This is expected behavior as the API does not return null or empty values.

Reference: Google Ads API Reporting: Zero Metrics

Steps to resolve:

  1. Check your reporting criteria and ensure that there are metrics available for the selected period for the missing campaign, ad, or keyword.

5. Rows seem to be duplicated

If you notice what seems to be duplicated rows, this might be due to hidden columns or different breakdowns in your report.

Steps to resolve:

“Duplicated” rows can appear due to different dimensions like "Ad network type" or other hidden columns. Reviewing the columns and data breakdowns can help identify the source of apparent duplicates.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.