RecipeGoogle Ads
Map a Google Ads account hierarchy
The account hierarchy under a manager, with account details and currencies per node.
IntentThe MCC tree with names, so nobody works on IDs.
- 2
- Steps
- 2
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Agency onboarding.
- Before cross-account reporting.
Do not use it when
- No specific contraindication beyond the preconditions below.
What it needs first
Required
Preconditions
- The account is ticked in the dashboard, confirmed via list_accounts.
Inputs
window- Analysis window.Default: last 30 days.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Walk the hierarchy from the manager.
Pull details, currency and timezone per account that matters.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Accounts under the MCC differ in currency or timezone
Conclude
Every future merged table must convert or label: record it now, in the map.
Evidence every conclusion must carry
- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.
Where the agent stops
- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- Manager access does not equal ticked access: the gateway answers only for ticked accounts, and the map must say which.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.