Plan the recovery path for duplicate conversions / multi-location retailer

For multi-location retailer, the same outcome is counted more than once. This field note turns which event should be authoritative into a short test for multi-location retailer, so the next change has a traceable reason.

Frame the signal

Context check: store and regional reporting. Topic check: assign one event ID to one business outcome.

Start with the first step after the signal is missing. Treat the dashboard number as a question, not an explanation. Follow one real journey from the first interaction to the system that owns the outcome. If a value is missing, mark it unknown instead of filling the gap with an assumption.

Trace the handoff

• Record the value at the first step and note the exact page, event, or record where it appears.
• Compare the browser, tag manager, analytics, ad platform, and CRM views without changing the implementation during the check.
• Check redirects, consent state, validation, naming, timestamps, and timezone before comparing totals.
• The recovery plan should explain how to preserve the record while the root cause is investigated.

Leave a decision record

the recovery plan should explain how to preserve the record while the root cause is investigated. Keep the owner, timestamp, evidence link, expected result, observed result, and next action together. Turning a silent gap into an owned recovery only after the current path is readable to someone who did not build it.

Reference: Google Analytics events guidance. For the next handoff, LeadSheet keeps the record connected.