Skip to main content

Google (Common)

This page documents the shared Google OAuth setup used by multiple connectors in this docs set. You typically won’t configure Google (Common) directly; instead, you’ll authenticate Google when setting up a specific Google source or destination that depends on this shared integration.

Setup​

  1. In the connector you’re configuring (for example, a Google Ads / Google destination that prompts for Google auth), choose Connect Google account.
  2. Sign in to Google and approve the requested permissions (scopes).
  3. After authorization completes, return to the connector configuration and finish setup.

Authentication​

Google (Common) uses OAuth 2.0. Under the hood, the platform stores a refresh token and periodically refreshes access tokens as needed.

Required permissions (scopes)​

The required scopes depend on the specific connector using Google (Common). For example, Google Data Manager ingestion requires:

  • https://www.googleapis.com/auth/datamanager

If the connected Google account does not include the required scope, the connector will prompt you to reconnect and re-authorize with the correct permissions.

Reconnecting / fixing authorization errors​

If you see errors indicating authorization is invalid or missing permissions:

  1. Open the connector configuration.
  2. Click Reconnect (or equivalent) to re-run the Google OAuth flow.
  3. Ensure you approve the permissions requested during the consent step.

Configuration fields​

Because this is a shared OAuth component, the exact fields shown in the UI may vary by connector. Common fields include:

  • Client ID: OAuth client ID used to initiate the Google OAuth flow.
  • Client secret: OAuth client secret paired with the client ID.
  • Authorization / Token: The stored OAuth authorization (refresh token) created during the sign-in flow.

Streams​

Google (Common) does not define streams by itself. Streams are defined by the specific Google source/destination connector that uses this shared authentication.