Clarvivo

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.

Browser and server event coverage export

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.

Why this happens

Browser tracking is losing ground. Ad blockers, browser privacy features and consent refusals stop a share of pixel and tag requests from ever leaving the visitor's device. For conversion events, that loss lands directly on your ad platforms' optimisation and your attribution reports.

Server-side tracking (Conversions APIs, server containers and backend events) closes much of that gap, but most setups adopt it unevenly. Purchases might be covered server-side while leads, sign-ups or subscription renewals still depend entirely on the browser.

This checker takes a simple export of event counts from both sides and lists the conversion events that have browser delivery but no server coverage, so you know where the gaps are.

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. Upload a coverage export

    A CSV with Event, Browser count and Server count columns, from Events Manager, your server logs or a reporting export.

  2. We find browser-only events

    Any event type with browser activity and zero server events is listed as a coverage gap.

  3. We summarise totals

    Browser and server totals are shown so you can see the overall balance.

Common causes and fixes

Server-side set up for purchases only
Extend server events to leads, sign-ups and other conversions your campaigns optimise for.
Server events named differently
If the server sends a different event name, it won't match. Use the same event names on both sides.
Server integration paused or failing
Zero server events for a type that used to have them often means an expired token or a broken integration.
Deduplication not configured
When you add server events, send a shared event ID so the platform doesn't count the action twice.

Frequently asked questions

Where can I get browser and server event counts?
Meta Events Manager shows both per event. Other platforms and server containers expose similar counts.
Is browser-only tracking always a problem?
For conversion events used in optimisation, it means you'll lose the share blocked by browsers and consent.
Should every event go server-side?
Prioritise the conversions your campaigns optimise for and the revenue events you report on.
Is my data stored?
No. The export is parsed for the result only.
What should I check after adding server events?
Deduplication: use the Meta Pixel + CAPI Dedup Checker for Meta and the Reddit Pixel + CAPI Dedup Checker for Reddit.

Give important conversions more than one fragile signal.

Clarvivo reconciles browser and downstream business evidence.

Connect complete revenue data

What this tool reads, and what it keeps