Read before:
../conectores.md(state map) andfichas.md(index of connector sheets).
What it is#
Reads clicks, impressions, CTR and position by query, page and country from the Search Console API and loads into the Bronze layer.
Supported ingestion modes:
- Nós buscamos — Nós buscamos os dados na sua fonte.
What it’s for#
Bring Google Search Console data into your datalake and make it available to the Bronze/Silver/Gold layers, BI models and 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.
Remember that the first run with a real credential is followed by our team before the connector is fully released.
Plan and permissions#
- Plan: core product (connectors are part of all plans; the limit is the number of sources of the plan).
- Access: requires an active workspace — with the subscription delinquent, suspended or cancelled, the run is blocked.
- Shutdown: ingestion runs can be temporarily turned off (maintenance or incident). When that happens, the screen reports that the feature is currently unavailable.
Prerequisites#
- A Google Search Console account with access to the data you want to ingest.
- In Search Console, go to Settings → Users and permissions and add the service account email with Full or Restricted (read) permission. Provide the property exactly as it appears there: sc-domain:exemplo.com.br (domain) or https://www.exemplo.com.br/ (URL prefix, with trailing slash).
Credentials#
Authentication method: Share with a service account: you share the resource (the spreadsheet) with the service account email, with Reader permission. We do not ask for your Google password nor access to your entire Drive.
Sensitive fields. They are encrypted (AES-256-GCM) and are never stored 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 this connection's credential to the external credential vault is an explicit choice, made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.
- Service account JSON key (
serviceAccountJson)
Secrets are never re-displayed and are redacted in any error/log (raw token, URL-encoded and in JSON).
Form fields#
| Campo | Rótulo | Tipo | Obrigatório | Observação |
|---|---|---|---|---|
siteUrl | Property | text | yes | Domain property (sc-domain:…) or URL prefix property (https://…/), identical to the Search Console selector. |
dataInicio | Start date | text | yes | Format yyyy-MM-dd. Used when the run does not provide a window. |
dataFim | End date | text | yes | Format yyyy-MM-dd. Search Console data arrives with 2–3 days of delay. |
lookbackDays | Window (days) | number | no | default: 28; How many days back each run rereads. |
saMode | Service account | selection | no | default: plataforma; options: plataforma / propria; With ours, you only add the service account email as a reader on the Search Console property. |
serviceAccountJson 🔒 | Service account JSON key | password/secret | no | secret (encrypted; external vault optional); appears when saMode = propria |
Step by step#
- In the menu Dados → Conexões, use Nova conexão.
- Choose Google Search Console from the catalog.
- Fill the form fields (see the table above).
- 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.
- Use Salvar conexão. Saving DOES NOT start any ingestion.
- 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.
- In review, Publicar (agenda desligada) creates version 1 without running anything. Afterwards, Ativar agenda and Executar agora are separate actions.
Example — connection test#
Example configuration (all values are fictitious; secrets appear masked):
# Exemplo sintético (valores fictícios — não são credenciais reais)
siteUrl = <siteUrl>
dataInicio = <dataInicio>
dataFim = <dataFim>
lookbackDays = 28
saMode = plataformaExpected result#
Testar conexão returns the list of discovered tables/resources. After the first load, rows appear in your workspace's Bronze layer, 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
batchSize5,000,maxRows200,000 per resource. - Estimated volume: ~0.2 GB/month (catalog estimate, not measurement).
- Cost: the extraction itself is not charged by the platform; the Bronze load consumes datalake processing (chargeable).
Security#
- Workspace scoping: each customer reads and writes only to their own datalake (
<prefix>_bronze/_silver/_gold); there is never leakage between workspaces. - Encrypted secrets: sensitive material is encrypted with AES-256-GCM before being written. The external credential vault is optional and enabled 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: every error/log is passed through secret redaction (raw, URL-encoded and in JSON).
- Production does not mock: a path that would fall into a 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 required permission. Reconnect the source (the source and history are preserved; do not recreate the source).
- Rate limit (429) — the provider asked to wait. The extraction respects
Retry-Afterand 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 consecutive runs, open a ticket with support stating the connector and resource.
- Empty record path — the response arrived without records in the expected place. Check the selected resource and filters (period, account, status) before assuming there is no data.
Troubleshooting#
- Use Testar conexão to isolate credential/network issues 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 changed = attention).
Related#
../conectores.md— connector catalog by state../ingestao-incremental-backfill.md— full, incremental by watermark, backfill and checkpoint../pipeline-medalhao.md— Bronze/Silver/Gold layers and quality../agendamento-retry-dlq.md— scheduling, retry/backoff and DLQ../custo-limites-seguranca.md— cost, caps and workspace security
Last review: 2026-10-04. Sheet generated automatically from the product connector catalog.