Clarvivo

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

A purchase tag may fire before payment success, omit the order ID, or replay on a refresh. Each failure can distort revenue and bidding.

A safe confirmation-page check is useful because it observes browser evidence without placing a real order.

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. Inspect purchase-like events

    Recognised browser events are grouped by name and ID.

  2. Refresh once safely

    A single refresh reveals replay risk without adding an item or using a checkout.

Common causes and fixes

Page-view purchase trigger
A confirmation route is treated as a new order on every visit.
No final order payload
Value and currency are unavailable when the event fires.

Frequently asked questions

Will this access checkout?
No. Use a public confirmation page only.
Does it see server purchase events?
No; it reports browser evidence.

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