Repeated technical events should not become repeated business outcomes
Check whether the same successful action fires repeatedly or arrives through multiple collection paths. Duplicate events can increase a reported rate without creating additional people or inquiries.
Double counting can arise from duplicate tags, multiple listeners, refreshes or tracking both a confirmation page and an acceptance callback. Find the event path before adjusting report totals.
A worked example
A hypothetical form creates one inquiry but fires two success events because a tag manager and a plugin both track completion. Dividing the dashboard count by two is a fragile workaround: it does not repair the path or handle other forms correctly.
How to apply it
- Trace a controlled successful submission and identify every event source.
- Test retries, refreshes, validation failures and alternative completion paths.
- Keep one justified success signal per defined outcome and verify downstream reporting.
What the result can establish
Deduplication keys should match the business event, with appropriate privacy handling. Keep aggregate historical corrections documented if required. A lower corrected conversion count is improved measurement integrity, not evidence of worse marketing.
Reference: Google Analytics: recommended events.
Supporting documentation
Google Analytics: recommended eventsW3C WAI: validating formsGoogle Analytics: attribution overview