Clarvivo

Free tool by Clarvivo · no login

See the Meta Pixel events your browser actually sends

Use a public page to identify Meta browser events and pixel IDs without creating a lead or purchase.

Public page to inspect

Load a public page and inspect recognised Meta Pixel events, pixel IDs and browser-side timing without clicking, submitting, or purchasing.

This tool answers: Which Meta Pixel events fire here, and do they have the IDs and values they need?

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

Why this happens

The Meta Pixel is often installed by several hands over time: the theme, an app, a tag manager, a developer. The result is pages that fire to two pixel IDs, conversion events on the wrong pages, or no Purchase event at all after a checkout change. Events Manager shows you aggregates, not what a specific page actually sends.

When Meta reports fewer conversions than you expect, or optimises toward the wrong events, the first question is simple: what does the browser send to Meta on this page? Which events, to which pixel, with which values?

This checker loads a public page and lists every Meta Pixel event the browser sends, so you can confirm the right events fire on the right page to the right pixel.

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. We load the page in a real browser

    The public URL is opened in an isolated browser session without clicking, submitting or purchasing.

  2. We capture Meta Pixel requests

    Every request to Meta's pixel endpoint is recorded with its event name and pixel ID.

  3. We check for conversion events

    We report whether a conversion event such as Purchase, Lead or CompleteRegistration fired, as opposed to only PageView or ViewContent.

Common causes and fixes

Pixel not installed on the page
Templates added after setup, landing-page builders and checkout pages on another domain often miss the Pixel.
Two pixel IDs on one page
Old pixels from agencies or previous accounts keep receiving events. Remove pixels you no longer use.
Conversion event on the wrong page
A Purchase or Lead on a page that isn't a completed action inflates conversions. Fire conversions only after success.
Pixel blocked by consent
If consent hasn't been granted, the Pixel may not fire at all, or may wait for an update command that never arrives.

Frequently asked questions

Which events count as conversions?
Standard conversion events such as Purchase, Lead, CompleteRegistration, Subscribe and similar. PageView and ViewContent are not conversions.
Can it see Conversions API events?
No. CAPI events are sent from your server. Use the Meta Pixel + CAPI Dedup Checker for the browser side of deduplication.
Why do I see two pixel IDs?
Usually an old pixel left in place by a previous agency, app or theme. Each one receives its own events.
Does it check event parameters?
This tool focuses on which events fire. Use the Meta Event Parameter Validator for value, currency and event ID.
Does it click or buy anything?
No. The scan is passive: it loads the page and records requests without clicking, submitting or purchasing.

Use clean Pixel evidence before optimizing spend.

Clarvivo compares platform claims with the revenue that follows.

Connect Meta to revenue

What this tool reads, and what it keeps