If you have read anything about the “Google Ads API,” you may have seen scary words like developer token, manager account, OAuth and Google Cloud Console. Take a breath — almost none of that is your job. This guide walks you through the actual steps, in plain English, with nothing technical required.
First, the good news: you don't “set up an API”
Here is the single most important thing to understand, because it removes most of the fear: the developer token and Manager (MCC) account that the Google Ads API requires belong to AdPilot, the software — not to you. They are already set up on our side.
Your everyday Google Ads account does not even have an “API Center,” and it does not need one. You connect by simply granting permissionwith a normal Google sign-in, and AdPilot's credentials do all the technical work behind the scenes.
What you need before you start
Just two things: a Google Ads account (free to create at ads.google.com), and your 10-digit Account ID. No Google Cloud project, no billing setup beyond whatever your Google Ads account already has, and no MCC.
Step 1 — Find your Google Ads Account ID
Sign in to your Google Ads account at ads.google.com. Look near the top-right corner — you will see a 10-digit number formatted like 123-456-7890. That is your Account ID (Google also calls it the Customer ID). Jot it down; you will confirm it in AdPilot in Step 4.
Step 2 — Click “Connect Google Ads” in AdPilot
In AdPilot, go to Settings. In the Google Ads section, click the Connect Google Adsbutton. This sends you to Google's secure sign-in screen — you are now on Google's side, not ours.
Step 3 — Sign in with Google and click “Allow”
Choose the Google account that has access to your Google Ads account (the same login you use at ads.google.com). Google will show you what AdPilot is asking for — permission to manage your Google Ads campaigns — and you click Allow (or Continue). Google sends you straight back to AdPilot, now connected.
Step 4 — Link your website to your Google Ads account
Back in AdPilot Settings, you will see your website(s). For each one, pick your Google Ads account — the 10-digit Account ID from Step 1 — and click Link. This simply tells AdPilot which account to build and push campaigns into. That is the last step.
That's it — what happens next
You are connected. Now you can generate a campaign from your website URL, review and edit every field, and push it to Google Ads with one click. Everything arrives paused — nothing serves or spends until you review it and switch it on yourself.
“But don't I need a developer token or an MCC?”
This is the most common worry, so let's answer it clearly. Yes — the Google Ads API does require a developer token, and developer tokens only come from a Manager (MCC) account. But that requirement falls on the app provider, and per Google's own documentation the developer token grants API access in general, while access to your specific account is handled separately through your sign-in permission (OAuth).
In other words: AdPilot holds the developer token under its own manager account; you grant access to your individual account by signing in. A standalone Google Ads account can be managed this way without ever creating its own manager account. That is why your account has no “API Center” — and why it doesn't need one.
If you're an agency with a Manager (MCC) account
Managing client accounts under a Manager (MCC) account works too. In Step 3, sign in with the Google account that has manager access. Then in Step 4, link each website to the specific client Account ID you want it to use — entering the exact ID keeps each website pointed at precisely the right account.
Is this safe? What am I giving AdPilot access to?
Connecting grants AdPilot permission to build and manage Google Ads campaigns on your behalf — that is what lets it create and push the campaigns you generate. It never spends money on its own: every campaign is created paused, and you approve every dollar. You stay fully in control, and you can revoke access at any time — either by clicking Disconnect inside AdPilot, or from your Google Account under Security → Third-party access.
