Clarvivo

Free tool by Clarvivo · no login

Find conversion events that fire more than once

Inspect a public confirmation page for duplicate browser conversion beacons, their timing and the IDs that may—or may not—deduplicate them.

Conversion page

Inspect a public conversion page for repeated GA4, Google Ads, Meta, TikTok, Reddit, LinkedIn, or Microsoft conversion beacons.

This tool answers: Which browser-side conversion events fire more than once?

Enable JavaScript to run the check — the diagnosis itself is free and needs no account.

Why this happens

Duplicate conversions are the most common way ad platforms over-report. A purchase is sent by the hard-coded site tag and again by Google Tag Manager. A Meta Purchase fires from the theme and from an app. A GA4 generate_lead event is wired to both a form-submit trigger and a thank-you page view. The customer did one thing; the platforms recorded two.

The effect compounds. Reported conversion rates look healthy, return on ad spend looks better than it is, and automated bidding pushes budget toward the campaigns that appear to convert most, which may simply be the ones with the most duplicated tags.

This detector loads a public conversion page and counts every recognised conversion request by platform and event name. If the same conversion appears more than once in a single page journey, you see it immediately, with the platform and event that repeated.

Next checks

These answer the questions this one tends to raise.

How this check works

So you can trust the result — and your developer can verify it.

  1. We capture every conversion request on the page

    The page is loaded in an isolated browser and we record recognised conversion beacons for GA4, Google Ads, Meta, TikTok, Reddit, LinkedIn and Microsoft Ads, including those fired through Google Tag Manager.

  2. We group them by platform and event

    Requests are grouped by platform, event name and, where present, conversion action or pixel ID. Two Purchase events to the same Meta pixel in one journey are flagged; a Purchase to Meta and a purchase to GA4 are not, because they are different platforms.

  3. We separate harmless repeats from real duplicates

    Some platforms send a configuration hit and an event hit. We count conversion events specifically, so a page_view or PageView alongside a Purchase does not trigger a false alarm.

Common causes and fixes

Hard-coded tag plus Google Tag Manager
A developer adds gtag.js conversions directly in the template, then marketing adds the same conversion in GTM. Pick one source of truth and remove the other.
Two apps or plugins sending the same pixel event
On Shopify and WordPress, a native integration and a third-party app often both send Purchase. Disable one, or make sure both send the same event ID so the platform can deduplicate.
Multiple triggers on one tag
A GTM tag triggered by both a form-submit event and a thank-you page view fires twice for one lead. Use a single success trigger.
Single-page apps firing on every route change
If the conversion tag listens to history changes, navigating within an SPA can re-fire it. Fire the conversion from the business event, not the route.

Frequently asked questions

Does the same conversion sent to two platforms count as a duplicate?
No. Sending a purchase to GA4 and to Meta is normal. A duplicate is the same conversion sent twice to the same platform.
Meta deduplicates with event_id. Is a duplicate still a problem?
Only if both requests share the same event_id and event name, which lets Meta discard one. If the IDs differ or are missing, both are counted.
Can it see server-side duplicates?
No. Conversions API and server-side tagging requests don't pass through the browser. Use the Meta Pixel + CAPI Dedup Checker for browser-side event IDs.
What should I paste?
The page where conversions fire: a thank-you, order-confirmation or sign-up success page.
How do I confirm the fix?
Re-run the check after removing the duplicate tag, and compare a week of platform-reported conversions against your CRM or order system.

Remove noise before attributing revenue.

Clarvivo shows the payment outcome behind every channel claim.

Connect conversion claims to payments

What this tool reads, and what it keeps