Clarvivo

Free tool by Clarvivo · no login

Validate the Meta event parameters your browser exposes

Check browser-visible Meta events for purchase value, currency and event-ID structure without sending data to Meta.

Public event page

Inspect public Meta browser events for event name, value, currency and event-ID parameter shape. Server-side events are reported as an explicit limitation.

This tool answers: Are the Meta event parameters visible in this browser request structurally complete?

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

Why this happens

Meta's value optimisation and deduplication depend on a handful of parameters. A Purchase without value and currency can't be used for value-based bidding or ROAS reporting. A purchase-like event without an event_id can't be matched with its Conversions API twin, so it's either counted twice or not deduplicated at all.

These parameters break quietly when templates change, when an app replaces the native integration, or when a developer hard-codes a test value. Events Manager may show warnings days later, but not which page or request caused them.

This validator inspects the Meta Pixel events a public page sends and checks the structure of purchase-like events: event name, value, currency and event ID.

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 capture Meta Pixel events

    The page is loaded passively in an isolated browser and every Meta Pixel event is recorded.

  2. We focus on purchase-like events

    Purchase, Subscribe and CompleteRegistration are checked for value and currency, because those are the events used for value-based optimisation.

  3. We check for an event ID

    We report how many purchase-like events carry an event_id. Without one, Meta can't deduplicate the browser event against a Conversions API event for the same action.

Common causes and fixes

Value or currency not passed
Map value and currency from your order data. Static tag fields or renamed variables leave them empty.
No event_id on browser events
Generate one ID per action (for example the order number) and send it with both the Pixel event and the matching CAPI event.
Different event IDs for Pixel and CAPI
If each side generates its own random ID, deduplication fails. Use the same ID on both.
Currency as a symbol
Send ISO codes such as USD or EUR, not symbols.

Frequently asked questions

Why does event_id matter?
Meta deduplicates a browser event and a server event when they share the same event name and event_id. Without it, both may be counted.
Can it see server-side events?
No. Conversions API requests never pass through the browser, and the result says so explicitly.
Which events are checked for value and currency?
Purchase-like events, meaning Purchase, Subscribe and CompleteRegistration, because those drive value-based optimisation.
What if no purchase-like event fires?
Then the page isn't a conversion page, or the event fires elsewhere. Test the page reached after a completed action.
What should I check next?
Compare Meta's reported purchases with your store using the Shopify vs Meta Purchase Gap Analyzer.

Make every Meta conversion structurally useful.

Clarvivo reconciles event claims with payment truth.

Validate Meta revenue signals

What this tool reads, and what it keeps