RecipeGoogle Analytics 4
Review GA4 property configuration
Property configuration read at onboarding and after governance changes.
IntentTimezone, currency, retention, the settings every number inherits.
- 2
- Steps
- 1
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Onboarding.
- Before cross-property comparisons.
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.
Read the property configuration.
Record timezone, currency and retention for every later analysis.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Data retention is set short
Conclude
Explorations lose history at that horizon: warn every analysis that plans beyond it.
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.
- Timezone differences between GA4 and ad platforms shift daily boundaries: 'yesterday' is not one thing.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.