If you are experiencing issues with your Google Ads connection in Datadrew, this article covers the most common problems and how to resolve them.
Authorization fails or hangs
Problem: The Google sign-in window does not open, shows an error, or the authorization does not complete.
Possible causes:
Pop-up blocker preventing the Google OAuth window.
You are signed into multiple Google accounts and the wrong one is being used.
Google is blocking the authorization because of account security settings.
Solutions:
Allow pop-ups for
app.datadrew.ioandaccounts.google.com.Before connecting, sign into only the Google account with Google Ads access. Alternatively, use an incognito window and sign in with the correct account.
Check if you have any security alerts in your Google account at myaccount.google.com/security.
No accounts appear after authorization
Problem: You authorize successfully but no Google Ads accounts are listed.
Possible causes:
The Google account does not have access to any Google Ads accounts.
You only have access to a manager (MCC) account with no sub-accounts.
The Google Ads account was recently created and may not be fully provisioned.
Solutions:
Verify your access by signing into ads.google.com directly with the same Google account.
If you use an MCC account, ensure it has at least one active sub-account.
Ask your Google Ads administrator to grant your Google account at least read access.
Token expired -- sync stopped
Problem: Google Ads data stops syncing and the integration shows a disconnected status.
Possible causes:
Google revoked the refresh token (this can happen if you remove Datadrew from your authorized apps or change your Google password).
Your Google Ads account was suspended.
Solutions:
Go to Settings > Integrations in Datadrew.
Click Reconnect next to the Google Ads integration.
Complete the Google authorization flow. Datadrew always requests
offlineaccess and prompts for consent to obtain a fresh refresh token.Your data pipeline will resume syncing from where it left off.
Metrics do not match Google Ads dashboard
Problem: Numbers in Datadrew differ from what you see in the Google Ads dashboard.
Possible causes:
Conversion lag -- Google Ads may adjust conversion data for several days after the click date. Very recent data may not yet reflect final numbers.
Date range or timezone -- Ensure you are comparing the same date range and timezone in both platforms.
Attribution model -- Your Google Ads account may use a different attribution model than last-click. Datadrew syncs the raw data as reported by Google.
Filtered views -- Your Google Ads dashboard may have filters applied (e.g., by campaign type or network) that affect the totals.
Solutions:
Compare the same date range and remove any filters in Google Ads.
For recent data, wait 48 hours for conversions to finalize.
If the discrepancy persists, contact us with screenshots from both platforms and we will investigate.
Only seeing some campaigns
Problem: Some campaigns appear in Datadrew but others are missing.
Possible causes:
The campaigns may belong to a different Google Ads customer account.
If you have multiple Google Ads accounts, you may have connected the wrong one.
Solutions:
Check which Google Ads customer ID is connected in Settings > Integrations.
If you need a different account, disconnect the current one and reconnect with the correct account.
Need help? Contact us at support@datadrew.io.
Related articles
Need help?
If you have questions or run into issues, reach out to us at support@datadrew.io or use the in-app chat. We're happy to help.