Skip to main content

Troubleshooting Google Ads Reader

Use this section to quickly diagnose common setup and runtime issues with the Google Ads Reader.

  • No rows in Incremental/Automated mode

    • Cause: No data for the Date window or misconfigured Start position.

    • Fix: Confirm the incremental marker is Date; adjust Start position and Polling interval.

  • 400-series errors during OAuth

    • Cause: Incorrect scopes or redirect URI.

    • Fix: Use scope https://www.googleapis.com/auth/adwords, include access_type=offline, and ensure the redirect URI matches the OAuth client configuration.

  • “Invalid table names”

    • Cause: Unsupported names or conflict between Tables and Excluded tables.

    • Fix: Test with a known table (for example, CampaignStatsReport), then broaden using %; clear conflicting exclusions.

  • Duplicates after recovery

    • Cause: Checkpoint is a Date field; updates aren’t tracked.

    • Fix: Enable MERGE/UPSERT at the target and define keys (or target key-column configuration).

  • Access denied to a client account

    • Cause: Access inherited via MCC, but Manager ID not specified.

    • Fix: Provide Manager ID or grant direct user access to the client account.

  • Token expired or unauthorized

    • Cause: Access token not refreshed or refresh token invalid.

    • Fix: Keep Auto token renewal enabled, or regenerate the refresh token and update credentials.

  • Rate limiting or throttling

    • Cause: Excessive concurrency or too-frequent polling.

    • Fix: Lower Thread pool count, increase Polling interval, or narrow the Tables selection.