Does coverage prove deduplication?

No. Use shared event or transaction IDs to verify pairing.

Free tool by Clarvivo · no login

Find conversion events that rely only on the browser

Upload event coverage counts to identify where blockers, consent or page failures leave no server-side counterpart.

Upload a CSV with Event, Browser count and Server count columns. We flag event types that rely only on browser delivery.

This tool answers: Which conversion events have browser delivery but no server-side coverage?

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

Browser tracking is useful but incomplete by design: consent, blockers and page failures can suppress it.

Server events are not automatically better; the point is to identify paths with no complementary coverage and then reconcile stable IDs.

These answer the questions this one tends to raise.

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

Compare event-type counts
We read Event, Browser count and Server count columns from one coverage export.
Highlight missing counterparts
A browser-only event is surfaced with a specific next mapping step.

No server endpoint: The event was never wired beyond a client tag.
Names do not align: Browser and server systems report the same action under different names.

Does coverage prove deduplication?: No. Use shared event or transaction IDs to verify pairing.
What file format works?: A CSV with Event, Browser count and Server count.

Clarvivo reconciles browser and downstream business evidence.