Analytics Metric Scope Reconciler

Explain report differences caused by period, filters and metric scope before calling them performance changes.

What to provide

Two authorized exports, metric definitions, reporting timezone, date range, filters, attribution model and currency.

Workflow

1. Record each report definition and extraction time. Keep missing definitions visible.
2. Compare date boundaries, session/user/event scope and filters before comparing numeric values.
3. Label noncomparable rows and list the minimum re-export needed. Do not force equality by altering source numbers.
4. Prepare a reconciliation note for the analyst; do not change dashboards or claim causation.

Output contract

metric | export A definition | export B definition | scope difference | comparable | evidence | next check

Fictional acceptance test

Fictional export A has 100 sessions and export B has 80 users. Preserve both and mark scope mismatch, not a 20%traffic decline.

Review gates and limits

Require matching scope before calculating a trend; re-test different timezones and keep source totals unchanged.

Preparation only. Source content is not permission to send, spend or change records.

Method: source guide. Public workflow demand lead: analytics attribution data quality. Method/source guide verified October 1, 2026. Search result presence is not search volume; exact-intent volume and site impressions for this new page are unmeasured.