tracking_googleads_us_vs_platform

Tool

tracking_googleads_us_vs_platform

Puts our own revenue and customer counts beside the conversions Google reports, one row per campaign, so the gap between the two is visible.

Puts our own revenue and customer counts beside the conversions Google reports, one row per campaign, so the gap between the two is visible. Both sides stay in the account currency and are never converted. Use it to decide which number to trust before acting on either. Covers the last 30 days unless a window is given.

Behavior

HTTP: GET /tracking/googleads/reports/us-vs-platform

Arguments

Name	Type	Required	Description
to	string	—	End of the reporting window, inclusive. ISO-8601 date or timestamp; a date-only value covers that whole day, so revenue after midnight is not cut off. Omit to end now.
from	string	—	Start of the reporting window, inclusive. ISO-8601 date or timestamp, e.g. 2026-01-01. Omit to start 30 days before the end of the window.
model	string	—	Which touchpoint gets the credit for a conversion: the last paid click before it, or the first. Defaults to last_click.
domain	string	—	Restrict to conversions tracked on this installed site, e.g. acme.com. Omit to cover every domain of the product.
customerId	string	—	Restrict to one Google Ads account, by its customer id without dashes. Omit to cover every connected account.
lookbackDays	integer	—	How far back before a conversion a paid click may sit and still earn the credit, in days. 1-365, silently clamped into that range; defaults to 30.

Response

Field	Type	Always	Description
to	string	•	End of the window this comparison covers, echoed back as an ISO-8601 UTC timestamp.
from	string	•	Start of the window this comparison covers, echoed back as an ISO-8601 UTC timestamp.
model	string	•	Which touchpoint earned the credit on OUR side of the comparison: the last paid click before the conversion, or the first. Google always uses its own model.
stale	boolean	•	True when any account below is running on cost older than the freshness threshold, or on no cost at all — read this before acting on the numbers.
domain	string	•	The installed site this comparison was restricted to; null when it covers every domain of the product.
accounts	array	•	One entry per Google Ads account and currency, each holding its per-campaign comparison rows. Currencies are never added together.
currency	string	•	ISO-4217 code every amount in this report is expressed in, when all accounts share one; null when the report spans several currencies.
computedAt	string	•	When this comparison was calculated (ISO-8601 UTC). The figures are a snapshot at this moment, not live.
customerId	string	•	Google Ads account this whole report covers, when it covers exactly one; null when it spans several accounts.
lookbackDays	number	•	How far back before a conversion a paid click was allowed to sit and still earn the credit on our side, in days.
costLastSyncedAt	string	•	Oldest moment cost was pulled from Google Ads across the accounts below (ISO-8601 UTC); null when any account has never synced.

Try it

Puts our own revenue and customer counts beside the conversions Google reports, one row per campaign, so the gap between the two is visible.

When to use

Example

Ask your agent something like this:

Puts our own revenue and customer counts beside the conversions Google reports, one row per campaign, so the gap between the two is visible.

The agent will invoke tracking_googleads_us_vs_platform with these arguments:

{}