Does the checker place an order?

No. It never enters checkout or pays. It only loads the public confirmation URL you supply and refreshes it once.

My confirmation page needs an order token. Will the scan work?

It will see whatever the page renders without a valid token, which is often an empty state. Use the URL from a real test order if it stays valid, or a public test confirmation page.

Which purchase events does it recognise?

GA4 purchase, Google Ads conversions, Meta Purchase, TikTok purchase events, and conversion events on Reddit, LinkedIn and Microsoft Ads that are visible in the browser.

How does this relate to the Shopify vs GA4 Revenue tool?

This checker tests one confirmation page in the browser. The Shopify vs GA4 Revenue tool compares totals across all orders, which shows whether purchases go missing on paths you can't test by hand.

Is a purchase with value but no transaction ID a problem?

Yes for deduplication. Without transaction_id, GA4 and Google Ads can't recognise a repeat of the same order.

Free tool by Clarvivo · no login

Check whether checkout produces one usable purchase event

Safely load and refresh a public confirmation page to find browser-side purchase events without starting checkout or paying.

Public order-confirmation page

Use a public confirmation page after checkout. We load and safely refresh it to identify browser-side purchase events and repeat firing; we never enter checkout or pay.

This tool answers: Does a purchase event fire once after checkout success with the data it needs?

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

Why this happens

The purchase event is the most valuable signal your analytics and ad platforms receive, and the one most likely to break during a theme change, a checkout migration or a new payment method. When it fails, revenue reporting drifts away from the order system without any visible error.

Three failures matter most. The purchase doesn't fire at all on some checkout paths. It fires without a value or currency, so revenue reports show zero or the wrong amount. Or it fires again when the confirmation page is refreshed or revisited, inflating revenue and conversions.

This checker loads your public order-confirmation page, identifies browser-side purchase events across GA4 and the major ad pixels, checks that value and currency are present, and refreshes once to see whether the purchase repeats.

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 order-confirmation page
The scan opens the public URL in an isolated browser and captures recognised purchase events: GA4 purchase, Google Ads purchase conversions, Meta Purchase, TikTok CompletePayment or Purchase, and equivalent events on Reddit, LinkedIn and Microsoft Ads.
We check value and currency on each purchase
Each purchase event is inspected for a numeric value and a currency code. A purchase without them is reported per platform, because revenue and value-based bidding depend on both.
We refresh to catch repeats
The page is reloaded once. A purchase that fires again on reload will be counted every time a customer revisits the confirmation page, unless the platform can deduplicate it by transaction or event ID.

Common causes and fixes

Purchase fires from a page view: Triggering the purchase on the confirmation URL means refreshes and revisits count again. Trigger it from the order-complete event, and send the order ID so repeats are deduplicated.
Value or currency not mapped: Theme or checkout updates rename the variables your tags read. Map value and currency from the order object, and send currency as an ISO 4217 code such as USD or EUR.
Express checkouts skip the confirmation page: Apple Pay, Shop Pay, PayPal and other express flows sometimes complete on a different page or a provider domain. Test each payment method; a purchase that only fires on standard checkout under-reports revenue.
Consent blocks the tags on the confirmation page: If the consent banner hasn't been answered on the confirmation page, ad tags may wait or be denied. Check that consent state carries over from earlier in the session.

Frequently asked questions

Does the checker place an order?: No. It never enters checkout or pays. It only loads the public confirmation URL you supply and refreshes it once.
My confirmation page needs an order token. Will the scan work?: It will see whatever the page renders without a valid token, which is often an empty state. Use the URL from a real test order if it stays valid, or a public test confirmation page.
Which purchase events does it recognise?: GA4 purchase, Google Ads conversions, Meta Purchase, TikTok purchase events, and conversion events on Reddit, LinkedIn and Microsoft Ads that are visible in the browser.
How does this relate to the Shopify vs GA4 Revenue tool?: This checker tests one confirmation page in the browser. The Shopify vs GA4 Revenue tool compares totals across all orders, which shows whether purchases go missing on paths you can't test by hand.
Is a purchase with value but no transaction ID a problem?: Yes for deduplication. Without transaction_id, GA4 and Google Ads can't recognise a repeat of the same order.

Count orders once, then reconcile them to payment.

Clarvivo keeps checkout measurement accountable to revenue.

Connect checkout to revenue

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.