Duplicate conversion counting
Duplicate conversion counting happens when a single real conversion is recorded more than once — for example by both a browser pixel and a server event, by a tag firing twice, or by two platforms each claiming it. It silently inflates reported conversions and value, distorts ROAS, and misleads bidding unless deduplication via shared event IDs and clear ownership is in place.
What this means
A conversion should map to one recorded event. Duplication breaks that when the same purchase is logged twice: a pixel fires and a Conversions API also sends it; a tag double-fires on a refresh or SPA navigation; a thank-you page is reloaded; or two ad platforms each attribute the same sale within their own walled gardens.
The result is inflated conversion counts and value. Because the inflation looks like success, it often goes unquestioned until ROAS or close-rate numbers stop reconciling with actual revenue.
How to prevent it
Within a single platform, deduplication relies on a shared event ID sent by both the pixel and the server so the platform counts the conversion once. Tag-level duplication is prevented by firing conversion tags only on a true completion, guarding against refreshes and back-navigation, and avoiding multiple tags for one event.
Cross-platform duplication is different: two walled gardens legitimately each claim a conversion they influenced, so you must not sum platform-reported conversions as if they were exclusive. Meta and Google document event-ID deduplication. The discipline is one event per real conversion, deduped by ID, with explicit ownership rules across overlapping platforms.
- Pixel + server: dedupe with a shared event ID
- Tags: fire once on true completion, guard refreshes
- Across platforms: never sum overlapping claimed conversions
How it appears in analytics and logs
Reported conversions exceeding known real conversions, or a sudden jump after adding a tag/integration, points to duplication rather than genuine growth.
Diagnostic use case
Audit for duplicate counting whenever a pixel and server both report, tags can double-fire, or multiple platforms claim conversions, and deduplicate with event IDs.
What WebmasterID can help detect
WebmasterID records conversions first-party with a clear event source, giving a clean reference to detect when other systems double-count.
Common mistakes
- Running pixel and server events without an event ID to dedupe.
- Firing conversion tags on page refresh or back-navigation.
- Summing the same conversion claimed by two ad platforms.
Privacy and accuracy notes
Deduplication uses an event identifier to match records, not additional personal data. This page is educational, not legal advice.
Related pages
- Conversions API (CAPI)
A Conversions API (CAPI) is a server-side interface that sends conversion and event data directly from a business's servers to an ad platform, rather than relying solely on a browser pixel. It exists because in-browser tags increasingly miss events due to tracking prevention, ad blockers, and lost cookies; a server connection can pass events the browser never reported, subject to consent and matching.
- Walled-garden attribution and its self-reporting
Walled gardens are closed ad platforms that measure and report the conversions they claim credit for, inside their own systems. Each marks its own homework with its own window and rules, so summed across platforms the attributed conversions routinely exceed the real total — double-counting is structural, not accidental.
- Server-side attribution and tagging
Server-side attribution moves the collection and forwarding of measurement events from the browser to a server you control — via server-side tag management or platform conversion APIs like Meta's CAPI. It can improve resilience to browser restrictions and give you governance over what data leaves your environment, but it is a data-flow change, not a way to bypass consent.
- CTA tracking
Fire conversion events once on true completion.
Sources and verification notes
- Meta for Developers — Conversions API: deduplicationDocuments shared event-ID deduplication of pixel and server events.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.