# Analytics Intraday Restatement Register

Track changes between early and daily analytics snapshots without calling every difference a tracking failure.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Two dated report snapshots with same property, metrics, date range/timezone and filters; processing state and attribution settings.

## Workflow
1. Verify scope and cutoff match before subtracting values.
2. Keep intraday and daily processing state visible; typical processing windows are not guarantees.
3. Calculate snapshot changes and separate missing dimensions from numeric revisions.
4. Return restatement evidence and questions; no tracking-code or attribution-setting change.

## Output contract
metric | early_value | later_value | signed_change | processing_state | scope_match | cause_unverified

## Fictional acceptance test
Fictional same-scope key events revise from 18 to 20, change+2. Record the change, not a proven tracking bug. Missing early traffic source remains missing; do not distribute the 2 events across channels without evidence.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://support.google.com/analytics/answer/11198161

Checked October 9, 2026. Oct 9 live AIS Search Console through Oct 6: marketing Copilot 37 impressions, Planable/Claude 33, Planable/ChatGPT 23, campaign brief 12, investor agent 19. Social-review/reporting topics follow these parent-query leads. Other professions follow documented workflow needs, not measured exact search intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.