Leia antes:
../conectores.md(mapa de estados) efichas.md(índice das fichas).
What it is#
Reads daily traffic by channel, pages and events from the Google Analytics Data API (GA4) 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 Analytics 4 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 by 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 allowed by the plan).
- Access: requires an active workspace — with the subscription past due, suspended or cancelled, the run is blocked.
- Shutdown: the ingestion run can be temporarily turned off (maintenance or incident). When that happens, the screen indicates that the feature is currently unavailable.
Prerequisites#
- A Google Analytics 4 account with access to the data you want to ingest.
- In Google Analytics, go to Administrador → Gerenciamento de acesso à propriedade and add the service account email with the Viewer role. Provide the numeric property ID (Administrador → Detalhes da propriedade). We do not ask for your Google password.
Credentials#
Authentication method: Sharing with a conta de serviço: you share the resource with the service account email, with Viewer permission. We do not ask for your Google password or access to your entire Drive.
Sensitive fields. They are encrypted (AES-256-GCM) and never stored in the config of the connection, 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.
- Chave JSON da conta de serviço (
serviceAccountJson)
Secrets are never re-displayed and go through redaction on every error/log (raw token, URL-encoded and in JSON).
Form fields#
| Campo | Rótulo | Tipo | Obrigatório | Observação |
|---|---|---|---|---|
propertyId | ID da propriedade GA4 | texto | sim | Número que aparece em Administrador → Detalhes da propriedade (não é o ID de medida G-XXXX). |
lookbackDays | Janela (dias) | número | não | padrão: 30; Quantos dias para trás cada run relê. |
saMode | Conta de serviço | seleção | não | padrão: plataforma; opções: plataforma / propria; Com a nossa, você só adiciona o e-mail da conta de serviço como leitor na propriedade do GA4. |
serviceAccountJson 🔒 | Chave JSON da conta de serviço | senha/segredo | não | segredo (cifrado; cofre externo opcional); aparece quando saMode = propria |
Step-by-step#
- No menu Dados → Conexões, use Nova conexão.
- Escolha Google Analytics 4 no catálogo.
- Preencha os campos do formulário (veja a tabela acima).
- 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. Salvar NÃO inicia ingestão nenhuma.
- No cartão da conexão, use Montar extração (ou vá em Orquestração → Pipelines e use Conectar fonte). O pipeline aponta para a conexão salva — a credencial não é copiada.
- Na revisão, Publicar (agenda desligada) cria a versão 1 sem executar nada. Depois, Ativar agenda e Executar agora são ações separadas.
Example — connection test#
Example configuration (all values are fictitious; secrets appear masked):
# Exemplo sintético (valores fictícios — não são credenciais reais)
propertyId = <propertyId>
lookbackDays = 30
saMode = plataformaExpected result#
Testar conexão returns the list of discovered tables/resources. After the first load, 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); includes an anti-loop safeguard.
- SaaS load: default
batchSize5,000,maxRows200,000 per resource. - Estimated volume: ~0.3 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 customer reads and writes only in 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 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 passes 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 necessary 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 terminates when the API cursor does not advance (anti-loop safeguard). If it happens in consecutive runs, open a support ticket with the connector and resource information.
- 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 observabilidade por conector (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, limits and security by workspace
Last review: 2026-10-04. Card automatically generated from the product connectors catalog.