Does this inspect CAPI?

No. Server events never pass through the browser.

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.

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.

A Meta Pixel can load while the event that matters never fires, fires on the wrong page, or fires twice.

Account reporting cannot show the exact browser request that produced an event, which makes first-pass debugging slow.

These answer the questions this one tends to raise.

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

Identify Pixel requests
We recognise browser-side Meta Pixel endpoints and group their events.
Surface timing
The result distinguishes initial load, navigation and refresh evidence.

Legacy and GTM tags overlap: Two installations commonly create duplicate browser events.
A pageview trigger is mistaken for success: A visitor can view a page without converting.

Clarvivo compares platform claims with the revenue that follows.

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.