# Key Event Counting Method Effective Cutoff

Keep a counting-method change from being applied retroactively to old report rows.

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

## Inputs
Method-change log, effective time, event times/timezone and before/after report periods.

## Workflow
1. Preserve the old and new counting methods with their effective time.
2. Split periods at the change instead of rewriting historical counts.
3. Label mixed-method reports as not directly comparable without source evidence.
4. Return a change note; no historical data repair or setting update.

## Output contract
period | effective_method | cutoff | mixed_method | comparable | explanation

## Fictional acceptance test
Fictional method switches to once-per-eventOct 10. September data is not recalculated by that setting. Comparing September 10 withOctober 20 needs method scope, not an automatic 100%growth claim.

## 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/13366706?hl=en

Checked October 11, 2026. Oct11 live AIS Search Console: marketing Copilot37 impressions, Planable/Claude35, Planable/ChatGPT24, campaignbrief12, investoragent19, MuseIndia98. Social calendar/reporting topics follow parent-query leads; other professions follow documented workflow needs, not measured exact intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.