Troubleshooting¶
This page covers common issues encountered when using the Google Ads Integration module and how to resolve them. Issues are organized by category for quick reference.
Connection issues¶
“Connection test failed” error¶
Symptom: Clicking Test Connection in the configuration shows a failure message.
Causes and solutions:
Invalid customer ID. Verify the Customer ID is exactly 10 digits with no dashes. Navigate to and correct it.
Developer token not approved. New developer tokens start in test mode and can only access test accounts. Apply for Standard access in the Google Ads API Center.
OAuth token expired. Click Connect to Google Ads to re-authorize and obtain a fresh refresh token.
Wrong Google account. The Google account used for authorization must have access to the specified Google Ads account. Re-authorize with the correct account.
MCC account required. If accessing through a Manager account, ensure the Login Customer ID field is set to the MCC account ID.
Conversion tracking issues¶
Conversions stuck in “pending” status¶
Symptom: Queue entries remain in pending status and are not uploaded.
Causes and solutions:
Missing click identifier. The lead does not have a GCLID, GBRAID, or WBRAID. Check the lead’s Google Click ID field. Leads without click identifiers cannot have click conversions uploaded.
New conversion action propagation. If the stage’s conversion action was recently created (within 6 hours), entries are held until the propagation delay expires. Check the Action Created At timestamp on the CRM stage.
Cron not running. Verify the scheduled action is active at . Look for “Daily Conversion Catch-up.”
Connection issue. Test the Google Ads connection at .
Conversions marked as “failed”¶
Symptom: Queue entries show failed status with an error message.
Causes and solutions:
“INVALID_CONVERSION_ACTION” – The conversion action ID no longer exists or was deleted in Google Ads. Re-link the stage to a valid conversion action.
“DUPLICATE_ORDER_ID” – A conversion with the same order ID was already uploaded. This typically indicates the conversion was already processed. No action needed.
“EXPIRED_CONVERSION” – The click happened more than 90 days ago, exceeding Google’s maximum attribution window. No action possible.
“INVALID_CUSTOMER_ID” – The customer ID in the configuration does not match the Google Ads account. Verify the Customer ID setting.
Review the Error Message field on the queue entry for specific details.
Conversions marked as “skipped”¶
Symptom: Queue entries show skipped status with a skip reason.
Common skip reasons:
“No click identifier” – The lead has no GCLID/GBRAID/WBRAID. This is expected for leads that did not come from Google Ads clicks.
“Action propagation delay” – The conversion action was created within the last 6 hours. Entries are automatically retried after the delay.
Audience issues¶
Audience list shows “Below Minimum”¶
Symptom: The audience list has a below_minimum badge.
Cause: The list has fewer than 1,000 members. Google Ads requires at least 1,000 members for an audience to be used in ad targeting.
Solution: Add more CRM stages to the list or wait for more leads to reach the linked stages.
Audience sync fails with error¶
Symptom: Audience list status shows error with an error message.
Causes and solutions:
“INVALID_OPERATION” – The audience list was deleted in Google Ads. Click Create in Google Ads to recreate it.
“AD_USER_DATA_CONSENT_DENIED” – The consent settings prevent uploading. Set Default Ad Personalization Consent to
grantedin .“INVALID_DATA” – Members do not have valid email addresses. Ensure leads at the linked stages have email addresses filled in.
Reporting issues¶
No report data showing¶
Symptom: The reporting views are empty.
Causes and solutions:
Reporting not enabled. Navigate to and check Enable Ad Performance Reporting.
Cron has not run yet. The reporting cron runs daily at 5:00 AM. Trigger it manually from .
No campaign data in Google Ads. If your Google Ads account has no active campaigns, there is no data to pull.
Report data seems outdated¶
Symptom: Report metrics do not reflect recent changes in Google Ads.
Cause: Reports are refreshed on a rolling 7-day window. The daily cron may not have run yet for today.
Solution: Wait for the next scheduled run, or trigger the “Pull Ad Reports” cron manually. Google Ads attribution can take up to 72 hours to fully settle, so recent conversion counts may increase over the next few days.
Health alerts¶
Understanding alert types¶
Alert type |
Meaning and action |
|---|---|
|
OAuth credentials are no longer valid. Re-authorize at . |
|
A conversion action referenced by a CRM stage was deleted in Google Ads. Re-link the stage to a valid action. |
|
A conversion action was renamed in Google Ads. Update the stage name if needed. |
|
A conversion action was disabled in Google Ads. Re-enable it in Google Ads or unlink the stage. |
|
More than 50% of recent uploads failed. Check the conversion queue for error patterns. |
|
More than 1,000 entries are pending upload. Check connection and cron health. |
To acknowledge an alert, open it and click Acknowledge. Acknowledged alerts are hidden from the default view.
Lead form import issues¶
No leads being imported¶
Symptom: The lead form imports list is empty despite having form submissions in Google Ads.
Causes and solutions:
Feature not enabled. Check Enable Lead Form Import in the configuration.
No lead form extensions. Verify your Google Ads campaigns have lead form extensions configured.
Cron not running. The import cron runs hourly. Check scheduled actions.
Imported leads missing data¶
Symptom: CRM leads created from form submissions have empty fields.
Cause: Google Ads lead forms only capture the fields configured in the form extension. If a form only asks for name and email, phone and company fields will be empty.
Solution: Review your lead form configuration in Google Ads and add the fields you need.
Getting help¶
If none of the above solutions resolve your issue:
Check the health alerts at for system-level issues.
Review the conversion queue at for specific entry errors.
Check the Progrid server logs for detailed error traces.
See also
Connection Setup – Re-verify your connection setup
Security – Ensure you have the right permissions