Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-05

Google Ads — connector

Reads performance reports from Google Ads (by campaign, ad group, or keyword) and loads them into the Bronze layer.

On this page (16)

Read before: ../conectores.md (state map) and fichas.md (index of the datasheets).


What it is#

Reads performance reports from Google Ads (by campaign, ad group, or keyword) and loads them into the Bronze layer.

Supported ingestion modes:

  • We pull — We pull the data from your source.

What it's for#

Bring the data from Google Ads into your datalake and make it available to the Bronze/Silver/Gold layers, to BI models and to the natural-language question wizard.

When to use / when not to use#

Use when you need to consolidate this source into the datalake on a scheduled basis, with isolation per workspace.

Use it with your company's credentials: the connector calls the Google Ads API with the developer token of your manager account (MCC), an OAuth client from your project and a refresh token from a user with access to the account. Everything is yours; nothing depends on an app of ours.

Plan and permissions#

  • Plan: core product (connectors are part of all plans; the limit is the number of sources in the plan).
  • Access: requires an active workspace — with the subscription overdue, suspended or canceled, the run is blocked.
  • Shutdown: the ingestion run can be temporarily turned off (maintenance or incident). When that happens, the screen informs that the feature is unavailable at the moment.

Prerequisites#

  • A Google Ads manager account (MCC) — the developer token is obtained there.
  • A Google user with access (read is enough) to the ad account you want to read.
  • A project in Google's cloud console with the Google Ads API enabled, to create the OAuth client.

How to obtain each credential#

  1. Developer token (developerToken) — in the manager account (MCC), open Tools → Setup → API Center, accept the terms and copy the token. A token at Test access level only reads test accounts: request Basic access on the same screen to read real accounts.
  2. OAuth client (clientId and clientSecret) — in Google's cloud console, in your project: enable the Google Ads API, configure the OAuth consent screen and create an OAuth client ID credential of type Desktop app. Copy the client ID and the client secret.
  3. Refresh token (refreshToken) — authorize that OAuth client with the user who accesses the ad account, requesting the https://www.googleapis.com/auth/adwords scope, and keep the returned refresh token (e.g. with Google's OAuth Playground, ticking Use your own OAuth credentials with your ID and secret). If the consent screen is in Testing mode, the refresh token expires in 7 days — publish the app so it lasts.
  4. Account ID (customerId) — the 123-456-7890 number in the top-right corner of Google Ads, on the ad account (not the MCC).
  5. Manager account (loginCustomerId) — only if your user accesses the ad account through the MCC: enter the MCC ID. If access is direct, leave it empty.
  6. In ingestia.io, under Dados → Conexões → Nova conexão → Google Ads, fill ID da conta (customer ID), Conta administradora (MCC) (if applicable), OAuth client ID, Developer token, OAuth client secret and Refresh token, then use Testar conexão.

If the authorization expires or is revoked, generate a new refresh token and use Reconectar on the connection — the source and its history are preserved.

Credentials#

Authentication method: OAuth 2.0 (client id/secret + refresh token). All secrets are encrypted (AES-256-GCM) and are never displayed again. If the authorization expires, just reconnect — the source and the history are preserved.

Sensitive fields. They are encrypted (AES-256-GCM) and never remain in the connection config, in the pipeline definition, in the export or in the DAG. By default the encrypted value is stored in the database; moving the credential for this connection to the external credential vault is an explicit choice, made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.

  • Developer token (developerToken) — Found in the API Center of your manager account (MCC). It must be approved with basic or standard access.
  • OAuth client secret (clientSecret)
  • Refresh token (refreshToken) — Generated once with the https://www.googleapis.com/auth/adwords scope, by the same OAuth client, by someone who has access to the account.

Secrets are never re-displayed and are redacted in every error/log (raw token, URL-encoded and in JSON).

Form fields#

CampoRótuloTipoObrigatórioObservação
customerIdAccount ID (customer ID)textyesAppears in the top-right corner of Google Ads.
loginCustomerIdManager account (MCC)textno—
reportPresetReportselectnodefault: campaigns; options: campaigns / groups / keywords
lookbackDaysWindow (days)numbernodefault: 30
clientIdOAuth client IDtextyesFrom the OAuth client (desktop app or web type) created in your project, with the Google Ads API enabled.
developerToken 🔒Developer tokenpassword/secretyessecret (encrypted; external vault optional); Found in the API Center of your manager account (MCC). It must be approved with basic or standard access.
clientSecret 🔒OAuth client secretpassword/secretyessecret (encrypted; external vault optional)
refreshToken 🔒Refresh tokenpassword/secretyessecret (encrypted; external vault optional); Generated once with the https://www.googleapis.com/auth/adwords scope, by the same OAuth client, by someone who has access to the account.

Step-by-step#

  1. In the menu Dados → Conexões, use Nova conexão.
  2. Choose Google Ads in the catalog.
  3. Fill out the form fields (see the table above).
  4. Use Testar conexão. The result is shown broken down into Conectividade, Autenticação and Listagem/leitura — each with OK, Failed, Not applicable or Not tested. A capability with no test of its own for this connector shows as Not applicable, and Not applicable never counts as success.
  5. Use Salvar conexão. Saving does NOT start any ingestion.
  6. On the connection card, use Montar extração (or go to Orquestração → Pipelines and use Conectar fonte). The pipeline points to the saved connection — the credential is not copied.
  7. In the review, Publicar (agenda desligada) creates version 1 without running anything. Then, Ativar agenda and Executar agora are separate actions.

Example — connection test#

Sample configuration (all values are fictitious; secrets appear masked):

text
# Exemplo sintético (valores fictícios — não são credenciais reais)
customerId = 123-456-7890
loginCustomerId = <loginCustomerId>
reportPreset = campanhas
lookbackDays = 30
clientId = exemplo-client-id-ficticio
developerToken = •••••• (cifrado — nunca exibido)
clientSecret = •••••• (cifrado — nunca exibido)
refreshToken = •••••• (cifrado — nunca exibido)

Expected result#

The Testar conexão returns the list of discovered tables/resources. After the first load, the rows appear in the Bronze layer of your workspace, ready for the pipeline.

Limits and costs#

  • Pagination: hard cap per run (default 10,000 pages / 5,000,000 rows); anti-loop guard.
  • SaaS load: default batchSize 5,000, maxRows 200,000 per resource.
  • Estimated volume: ~0.5 GB/month (catalog estimate, not measurement).
  • Cost: the extraction itself is not charged by the platform; the Bronze load consumes datalake processing (billable).

Security#

  • Scope by workspace: each client reads and writes only to their own datalake (<prefixo>_bronze / _silver / _gold); there is never leakage between workspaces.
  • Encrypted secrets: sensitive material is encrypted with AES-256-GCM before being stored. The external credential vault is optional and linked per connection; without it, the encrypted value is stored in the database. Changing the value here DOES NOT revoke the credential at the source.
  • Redaction: all errors/logs pass through secret redaction (raw, URL-encoded and in JSON).
  • Production does not mock: a path that would fall into mock triggers the production guard (explicit failure instead of simulating success).

Common errors#

  • Credential refused (401/403) — the provider did not accept the credential: expired, revoked or lacking the necessary permission. Reconnect the source (the source and the history are preserved; do not recreate the source).
  • Rate limit (429) — the provider asked to wait. The extraction respects Retry-After and retries; if it repeats, wait and reduce the schedule frequency.
  • Resource not found — check the resource identifier (account, object, report) and the granted permissions.
  • Pagination cursor stuck — the extraction stops when the API cursor does not advance (anti-loop guard). If it happens in successive runs, open a support ticket informing the connector and the resource.
  • Empty record path — the response arrived without records in the expected place. Check the selected resource and the filters (period, account, status) before assuming there is no data.

Troubleshooting#

  • Use Testar conexão to isolate credential/network problems before scheduling.
  • Monitor runs in the connector observability (error rate, p50/p95, freshness).
  • A schema change at the source is signaled by schema drift (new column = info; removed column/type change = attention).

Related#


Last review: 2026-10-05. Datasheet automatically generated from the product's connector catalog.

Related links