Map how fresh each platform's data actually is
Per-platform freshness and attribution lags, measured and dated: the map every windowing decision leans on.
IntentThe lag table: what 'today' means on every platform, written down once.
- 2
- Steps
- 4
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Onboarding.
- Whenever windows get debated.
Do not use it when
- No specific contraindication beyond the preconditions below.
What it needs first
No single source is required: this one reads across whatever you have connected.
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 Search Console's own freshness marker.
Probe recent windows per platform and note where numbers still move.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
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 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.
- Lags change with platform reporting updates: date the map, refresh quarterly.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.