# Review GA4 property configuration

> Tier: recipe. Operating recipe: real tool sequence, core rules, known traps.

Property configuration read at onboarding and after governance changes.

**Intent.** Timezone, currency, retention, the settings every number inherits.

## When to use

- Onboarding.
- Before cross-property comparisons.

## When not to use

- No specific contraindication beyond the preconditions below.

## Sources

Required: Google Analytics 4

## Preconditions

- The account is ticked in the dashboard, confirmed via list_accounts.

## Inputs

- `window`: Analysis window. Default: last 30 days.

## Procedure

1. Read the property configuration. — tools: `ga4_get_property_configuration`
2. Record timezone, currency and retention for every later analysis.

## Decision rules

- **When** Data retention is set short → **conclude** Explorations lose history at that horizon: warn every analysis that plans beyond it.

## Evidence requirements

- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.

## Human approval boundary

- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.

## Failure modes

- Timezone differences between GA4 and ad platforms shift daily boundaries: 'yesterday' is not one thing.

## Output

- **Readout**: The figures, with windows and accounts named.
- **Flags**: What deserves a deeper skill or a human decision.

## Related

- Skill: [new-client-onboarding](https://www.getmcpads.com/skills/new-client-onboarding.md)