Skip to main content
Last updated on

Troubleshoot the Google Ads connector

Beta

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.

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:

  1. 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.
  2. 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: "Test tokens cannot access production accounts"​

Error message:

Test tokens cannot access production accounts.

Cause: The developer token has only test access, which cannot read production Google Ads data.

Solution: Ensure that the developer token has at least standard access. To check or upgrade your token:

  1. Sign in to your Google Ads Manager Account at https://ads.google.com/aw/apicenter.
  2. Go to Admin > API Center.
  3. Check the access level of your developer token. If it shows Basic or Test, apply for standard access for production workloads.

Redirect URI error during OAuth setup​

Error message:

Error: redirect_uri_mismatch

Cause: The redirect URI configured in your Google Cloud Console OAuth client doesn't match the Databricks workspace URL.

Solution:

  1. Visit the Google Cloud Console at https://console.cloud.google.com.
  2. Navigate to APIs & Services /> Credentials.
  3. Click your OAuth client credential.
  4. 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).
  5. Save the changes and try authenticating again.