# Key Event Explicit Value and Default Precedence

Preserve explicit event values when reconciling a configured default.

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

## Inputs
Event IDs, currency/value payloads, default setting snapshot, effective time and report export.

## Workflow
1. Keep explicit value and currency evidence beside each event.
2. Apply documented default behavior only to rows without an existing value.
3. Hold missing payload parameters and currency scope.
4. Return a precedence map; no tracking or value settings change.

## Output contract
event | explicit_value | currency | default | chosen_basis | unknown

## Fictional acceptance test
Fictional event A has value 7 and default 20; retain 7. Event B lacks value with a supported default 20; label its 20 as default-derived. These are key-event values, not proved cash sales.

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

Checked October 12, 2026. Oct12 live AIS Search Console: marketing Copilot37 impressions, Planable/Claude38, Planable/ChatGPT24, campaignbrief12, investoragent19, MuseIndia100. 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.