# Key Event Session and Event Reconcile

Explain a key-event total using its counting method before calling repeated triggers lost data.

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

## Inputs
Event IDs, session IDs, key-event definition and counting method at the event time.

## Workflow
1. Group supplied triggers by event and session IDs.
2. Compute once-per-event versus once-per-session totals separately.
3. Compare the documented method with the displayed total.
4. Hold missing session evidence and avoid changing tracking settings.

## Output contract
event | trigger_count | unique_sessions | counting_method | expected_count | gap

## Fictional acceptance test
Fictional five triggers in two sessions give 5 once-per-event or 2 once-per-session. Neither proves five buyers. Missing session IDs prevents the second calculation.

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