Troubleshoot the Google Ads connector
Beta
This feature is in Beta.
Learn how to troubleshoot common errors with the managed Google Ads connector in Lakeflow Connect.
I've authenticated, but I can't see my Google Ads data
Cause: You might be authenticating to the wrong Google account. Alternatively, the account might not have access to Google Ads.
Solution:
- Confirm that you are authenticating to the correct Google account. You can edit the connection and reauthenticate with the correct account, or recreate the connection to reassess the OAuth flow.
- Confirm that the account has Google Ads access. Log into the Google account and verify that it has permissions to access your Google Ads data.
Error: GOOGLE_ADS_ACTION_NOT_PERMITTED
Error message:
Output
The authenticated Google Ads user or the Google Cloud project that owns the OAuth client is not permitted to perform this action on the requested resource or to call this method (authorization_error: ACTION_NOT_PERMITTED or CLOUD_PROJECT_NOT_APPROVED_FOR_PRODUCTION).
Cause: Either the authenticated user doesn't have access to the account, or the Google Cloud project that owns your OAuth client has only Test access to the Google Ads API. A project with Test access can't read production Google Ads accounts.
Solution:
- Confirm that the authenticated user has access to the Google Ads account.
- Check the access level of the Google Cloud project that owns your OAuth client. See Confirm the Google Ads API access level. If it shows Test, apply for Basic or Standard access.
Redirect URI error during OAuth setup
Error message:
Output
Error: redirect_uri_mismatch
Cause: The redirect URI configured in your Google Cloud Console OAuth client doesn't match the Databricks workspace URL.
Solution:
- Visit the Google Cloud Console at https://console.cloud.google.com.
- Navigate to APIs & Services /> Credentials.
- Click your OAuth client credential.
- Under Authorized redirect URIs, confirm that it contains the following pattern:
https://<workspace-url>/login/oauth/google.html. Replace<workspace-url>with your Databricks workspace URL (for example,https://dbc-a1b2c3d4-e5f6.cloud.databricks.com). - Save the changes and try authenticating again.