Connect Google Ads to Tatheon and paid search spend lands beside paid social and revenue on the same board. This guide is for whoever has access to the Google Ads manager account, often called the MCC. It covers why this connection works differently from the others, how to set it up once, and what it does on its own afterwards.
Why this one is different
Google Ads uses a separate flow from Google Analytics 4 and Search Console, and it is worth knowing why before you start.
Most tools that read Google Ads use the Google Ads API, which requires a developer token, an OAuth client and a Cloud project, and the token takes weeks to be approved. Tatheon uses a scheduled Ads Script instead. Scripts run inside the Google Ads account itself, so none of that applies. There is no token to apply for, no Cloud project to create and no OAuth consent screen.
The practical result is that this connection takes minutes rather than weeks, and it works the same whether you manage one account or thirty.
Before you start
You need access to the manager account that sits above your ad accounts, not just to an individual account. The script runs at manager level and walks every linked child account underneath it, which is what makes one setup cover the whole portfolio.
If you only have access to a single ad account, the script still works, but you will need to install it per account rather than once.
Install the script
Open the source wizard and choose Google Ads. The wizard provides the script with your endpoint and token already filled in, so copy it from there.
In Google Ads, open Tools, then Bulk actions, then Scripts, and create a new script at the manager account level. Paste the script in, authorise it when prompted, and preview it once to confirm it runs without error.
Then schedule it to run daily. One schedule, left on permanently. That is the step people skip, and a script that is installed but never scheduled looks connected while sending nothing.
What it does on its own
Each run pushes recent performance and then walks history backwards until every linked account is fully backfilled. You do not have to trigger the backfill separately or tell it how far back to go. A large account takes several nightly runs to finish its history, and the board fills in as it goes.
The daily run also re-pulls a recent window rather than only sending yesterday. Google continues to attribute conversions for days after the click, so a figure from last week can still change this week. Re-pulling the window means the board reflects Google’s corrected numbers rather than freezing the first version it saw.
Confirm it is working
Check the script’s own run history in Google Ads first. A successful run reports rows sent. A run that errors reports why, and the most common cause is the authorisation being declined during setup.
Then compare a recent closed week against the same week in the Google Ads interface. Spend should match closely. Conversions and conversion value may differ, because Google reports conversions against the date of the click rather than the date of the purchase, and Tatheon reports revenue against the order. That difference is expected and is the reason both figures are shown.
Common problems
Spend appearing for some accounts and not others usually means the script was installed on a single account rather than the manager account. Reinstall at manager level.
Data that stops arriving suddenly, while the script still shows as scheduled, is nearly always an authorisation that lapsed after a password change on the account that created the script. Reauthorise the script and it resumes.
Next
With both major advertising platforms connected, the marketing mix section can compare blended efficiency across channels rather than trusting each platform’s own account of itself.