Connect your Google Ads account
Let your AI employee read campaign performance and manage your Google Ads (formerly AdWords) campaigns on your behalf.
Google AdsWhy we ask for this
Google Ads has no concept of a "password" for software. Instead, access is granted through a developer token (which authorises the application to talk to the Ads API at all) plus an OAuth refresh token (which proves you personally consented to let that application act on your account). The Customer ID simply tells the API which of your accounts to operate on.
This split is deliberately safer than a password. The OAuth grant is scoped to Google Ads only — it can never read your email or touch other Google services — and you can revoke it from your Google account at any time without changing any password. The developer token can likewise be reset from the API Center.
We hold these values as encrypted secrets (AES-256-GCM) scoped to your tenant and inject them into your isolated workroom only when a session starts. They are never baked into the container image, and revoking the OAuth grant on Google's side instantly cuts off access.
Where to get your credentials
- 1Sign in to your Google Ads account at ads.google.com with an account that has admin access.
- 2Open Tools → Setup → API Center to request a developer token. Approve the terms; the token is shown there.
- 3In the Google Cloud Console, create (or pick) a project and configure an OAuth consent screen, then create an OAuth 2.0 client ID of type "Web application" or "Desktop app". Note the client ID and client secret.
- 4Run Google's OAuth flow once with that client (the OAuth Playground works) and grant the Google Ads scope to generate a refresh token. Copy it.
- 5Find your Customer ID in the top-right of the Google Ads UI — the 10-digit number. Enter it without dashes (e.g. 1234567890, not 123-456-7890).
- 6Paste the developer token, client ID, client secret, refresh token, and Customer ID into the connection form.
Production access may need Google approval
A freshly issued developer token starts with "test" access, which can only reach test accounts. To manage your real, live campaigns, the token needs basic (production) access, which Google grants after a short application review of how the token will be used.
This is normal and not something to worry about — but it does mean campaign automation may not work the very first day, and may require some extra setup or approval. Our platform team can help you prepare the application and wire everything up. Until production access is granted, read-only reporting on test data is the most you will see.