# Map how fresh each platform's data actually is

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

Per-platform freshness and attribution lags, measured and dated: the map every windowing decision leans on.

**Intent.** The lag table: what 'today' means on every platform, written down once.

## When to use

- Onboarding.
- Whenever windows get debated.

## When not to use

- No specific contraindication beyond the preconditions below.

## Sources

Required: any connected source

## Preconditions

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

## Inputs

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

## Procedure

1. Read Search Console's own freshness marker. — tools: `gsc_get_data_freshness`
2. Probe recent windows per platform and note where numbers still move. — tools: `google_ads_get_insights`, `meta_get_insights`, `pinterest_run_report`

## Decision rules

- **When** A report's window ends inside a platform's moving zone → **conclude** Trim or flag: publishing numbers that will change is how trust dies.

## 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

- Lags change with platform reporting updates: date the map, refresh quarterly.

## Output

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

## Related

- Skill: [weekly-performance-review](https://www.getmcpads.com/skills/weekly-performance-review.md)