Connected accounts › Google · service account
Add Google Ads credentials
Crackle authenticates to the Google Ads API using a service account. Paste the service-account email and upload its JSON key — that's all we need from you. Crackle's developer token and MCC routing are managed centrally.
Before saving — give Crackle access in your Google Ads account
Crackle's MCC needs Standard access on the customer you're connecting. From your Google Ads MCC:
- Open Admin → Access & security → Users.
- Click + Add user and paste this email:
crackle-acme@natural-plasma-471312-k3.iam.gserviceaccount.com - Set permission level to Standard and click Send invitation.
Without this, the
customers.get probe on Save will fail with USER_PERMISSION_DENIED.Service account
From your GCP project: IAM & Admin → Service Accounts → Email column. Auto-filled from the JSON key on upload — editable in case you want to override.
natural-plasma-471312-k3-771fc26d53d9.json
2.4 KB · sha256 a1b2c3…f8e9 · uploaded 4 s ago
From your GCP project: IAM & Admin → Service Accounts → Keys → Add Key → Create new key → JSON. We extract the
client_email for the field above and store the rest envelope-encrypted in KVM. Plaintext never persists.Managed by Crackle — not in this form
Developer token — Crackle's shared token covers all tenants. No customer-side configuration required.
OAuth scope — fixed to
https://www.googleapis.com/auth/adwords.Login customer ID (MCC) — auto-routed by Crackle based on the customer-ID picker below.
Pick the customer to sync
Probe succeeded — customers.listAccessibleCustomers returned 3 accounts. Pick which one Crackle should attach to Acme Ads Co.
Authenticated as crackle-acme@natural-plasma-…iam.gserviceaccount.com. We'll re-probe with
customers.get on save.