Leia antes:
../conectores.md(mapa de estados) efichas.md(índice das fichas).
What it is#
Reads campaigns, ad groups and ads from the ad account in the Pinterest API v5 and loads into the Bronze layer.
Supported ingestion modes:
- We pull — We pull the data from your source.
What it's for#
Bring Pinterest Ads 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 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 UI indicates the resource is currently unavailable.
Prerequisites#
- A Pinterest Ads account with access to the data you want to ingest.
- In Pinterest Developers, create an app, authorize it on your ad account with the ads:read scope and generate the refresh token. Provide the ad account ID (Ads Manager → account), the Client ID, the Client Secret and the refresh token; secrets are encrypted (AES-256-GCM) and never shown again. If the authorization expires, simply reconnect.
Credentials#
Authentication method: OAuth 2.0 (client id/secret + refresh token). All secrets are encrypted (AES-256-GCM) and never shown again. If the authorization expires, simply reconnect — the source and history are preserved.
Sensitive fields. They are encrypted (AES-256-GCM) and never stored in the connection config, pipeline definition, export or 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.
- Client Secret (
clientSecret) - Refresh token (
refreshToken) — Issued when authorizing the app on your Pinterest account. If it expires or is revoked, reconnect — you do not need to recreate the source.
Secrets are never re-displayed and are redacted in every error/log (raw token, URL-encoded and in JSON).
Form fields#
| Campo | Rótulo | Tipo | Obrigatório | Observação |
|---|---|---|---|---|
adAccountId | ID da conta de anúncios | texto | sim | Número da conta no Ads Manager do Pinterest. |
clientId | Client ID | texto | sim | Identificador do aplicativo criado no portal de desenvolvedores do Pinterest. |
clientSecret 🔒 | Client Secret | senha/segredo | sim | segredo (cifrado; cofre externo opcional) |
refreshToken 🔒 | Refresh token | senha/segredo | sim | segredo (cifrado; cofre externo opcional); Emitido ao autorizar o aplicativo na sua conta Pinterest. Se expirar ou for revogado, reconecte — não é preciso recriar a fonte. |
Step-by-step#
- No menu Dados → Conexões, use Nova conexão.
- Escolha Pinterest Ads 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 connection 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)
adAccountId = act_1234567890
clientId = exemplo-client-id-ficticio
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
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 (billable).
Security#
- Scope per workspace: 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 remains in the database. Changing the value here DOES NOT revoke the credential at the source.
- Redaction: every error/log goes 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 rejected (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 repeated, wait and reduce the schedule frequency. - Resource not found — check the resource identifier (account, object, report) and 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 indicating the connector and the 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 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 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 security per workspace
Last review: 2026-10-04. Card automatically generated from the product connector catalog.