Connect Google Ads to SiteOps

Google Ads is where you pay Google to show your ads — on the search results page, on YouTube, and across the display network of partner sites. You set a budget, Google shows the ads, and you pay per click or per view.

On its own, Google Ads reporting lives in its own dashboard, away from your traffic and revenue numbers. Connecting it to SiteOps puts spend next to the visits and sales it produces, so you can see what a customer actually costs you.

The connection also works the other way. Once linked, SiteOps can launch campaigns for you — using your approved videos and the keywords it suggests, or as a plain search campaign with no video at all — without you building anything inside the Google Ads interface.

One honest timing note: campaign management runs through SiteOps's own Google Ads developer token, which Google upgrades from Basic to Standard access once at the platform level. That approval is a SiteOps step, not something you do — but on a fresh app it can lag, so launching may switch on a little after reporting does.

A loop, not a launch

Set it up, step by step

0 of 9 done

    1. Tools
    2. Billing
    1. Settings
    2. Google Ads
    3. Connect
  1. Both scopes matter — reporting fills charts, managing launches campaigns

    If you untick the managing permission, the connection still works for reporting, but launching campaigns from SiteOps will fail. You can reconnect later to grant it.

    1. Ads
    2. Launch

If something does not work

I connected but the Ads view is empty
Two common reasons. Either the account has never run a campaign — then there is simply nothing to show yet — or you picked the wrong customer id during the connection. Check the ten-digit number at the top right of ads.google.com against the one in SiteOps settings, and reconnect if they differ.
My campaign will not start spending
Billing, almost always. Open Google Ads, go to the Billing section and check for a verified payment method and any red warnings. Also check the campaign status: "Under review" is normal for the first day; "Disapproved" means Google rejected the ad and shows a reason next to it.
Launching from SiteOps fails with a permission error
Your Google login has read-only access to the ad account, or you declined the campaign-management permission on the consent screen. Ask the account owner for standard or admin access, then press Connect in SiteOps settings again and approve everything Google asks.
I see several accounts and do not know which to pick
Open ads.google.com, make sure you are looking at the account that holds your campaigns, and copy the ten-digit customer id from the top right. Pick that exact number in SiteOps. Skip anything labelled as a manager account — those hold other accounts, not campaigns.
The numbers in SiteOps differ slightly from Google Ads
Google keeps adjusting recent figures for up to a couple of days as it filters invalid clicks and settles conversions. SiteOps refreshes daily, so the last day or two can lag. Numbers older than that should match; if they do not, reconnect the account.

Set up once, see everything every morning

Get started