Is one repeat on refresh really a problem?

Yes, if it's a conversion event. Every refresh, back-button return and email revisit adds one. Over a month that becomes a measurable inflation of conversions and a distortion in automated bidding.

Which platforms does it check?

GA4, Google Ads, Meta Pixel, TikTok Pixel, Reddit Pixel, LinkedIn Insight Tag and Microsoft UET conversion requests that are visible in the browser.

What if no conversion fires at all?

Then either the page needs an order context to render the tag, or the conversion lives somewhere else in the flow. Try the page you reach after a real test purchase or lead.

Will deduplication fix a repeat that the checker found?

Usually. If the repeated request carries the same transaction or event ID, the platform can discard it. If it carries no ID, or a new random one each time, it will be counted.

Does it submit anything or place an order?

No. It only loads and refreshes the URL you give it.

Free tool by Clarvivo · no login

Find false conversions hiding on your thank-you page

We safely reload a public confirmation page once and report recognised conversion events that replay without a new lead or order.

Thank-you or confirmation page

Paste a public confirmation page. We load and safely refresh it once to reveal conversions that replay without a new form submission or order.

This tool answers: Can a refresh or revisit create a false conversion?

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

Why this happens

Thank-you pages are the easiest place to put a conversion tag and one of the easiest places to double count. The page loads, the tag fires, and the conversion is recorded. Then the customer refreshes, bookmarks the page, comes back from an email link, or hits the back button, and the tag fires again.

Each of those revisits is a conversion that never happened. Ad platforms count them, bidding learns from them, and your reported cost per lead looks better than reality. Because the inflation is small and steady, it rarely gets noticed until someone reconciles conversions against the CRM or the order system.

This checker answers one practical question: if someone loads your confirmation page twice, how many conversions do you record? It loads the page, refreshes it once, and compares what fired across GA4, Google Ads, Meta, TikTok, Reddit, LinkedIn and Microsoft Ads.

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.

We load the confirmation page
The public URL is opened in an isolated browser, and every recognised conversion request is captured: GA4 events, Google Ads conversions, Meta Pixel, TikTok, Reddit, LinkedIn Insight and Microsoft UET.
We refresh it once
After the page settles, the scanner reloads it, exactly as a customer would by pressing refresh. Any conversion that fires again on the reload is a conversion that will repeat for every revisit.
We compare the two loads
For each platform and event name we report whether it fired on the first load only, on both, or not at all, so you can see exactly which tag needs a one-time guard or a deduplication ID.

Common causes and fixes

The tag triggers on a page view of the thank-you URL: Page-view triggers can't tell a first visit from a revisit. Fire the conversion from the success event in your form or checkout flow instead, or set a one-time flag in session storage keyed to the order or submission ID.
No transaction or event ID for deduplication: Google Ads deduplicates on transaction_id, Meta on event_id, GA4 purchases on transaction_id. Without them, every repeat is counted. Send the order or submission ID with every conversion.
The thank-you page is public and linkable: If the URL works without an order context, anyone can load it, including bots and staff. Require a one-time token in the URL, or render the conversion only when the server confirms a fresh submission.
Confirmation emails link back to the thank-you page: Order emails that link to the confirmation page create a steady stream of repeat loads. Link to an order status page that doesn't carry conversion tags.

Frequently asked questions

Is one repeat on refresh really a problem?: Yes, if it's a conversion event. Every refresh, back-button return and email revisit adds one. Over a month that becomes a measurable inflation of conversions and a distortion in automated bidding.
Which platforms does it check?: GA4, Google Ads, Meta Pixel, TikTok Pixel, Reddit Pixel, LinkedIn Insight Tag and Microsoft UET conversion requests that are visible in the browser.
What if no conversion fires at all?: Then either the page needs an order context to render the tag, or the conversion lives somewhere else in the flow. Try the page you reach after a real test purchase or lead.
Will deduplication fix a repeat that the checker found?: Usually. If the repeated request carries the same transaction or event ID, the platform can discard it. If it carries no ID, or a new random one each time, it will be counted.
Does it submit anything or place an order?: No. It only loads and refreshes the URL you give it.

Trust the conversion before you optimize against it.

Clarvivo reconciles reported activity with payment and lead truth continuously.

Make conversion reporting trustworthy

What this tool reads, and what it keeps

We load the public URL in an isolated browser and inspect public document and tracking signals.
We do not log in, submit forms, complete checkout, or retain a page recording.
Redacted diagnostic evidence is retained for 7 days, then deleted.