Meta Conversions API payload validator
Paste the JSON body you POST to /{pixel_id}/events. Checks run in your browser against rules from Meta's docs (Meta: Main body parameters · Meta: Server event parameters · Meta: Customer information parameters · Meta: Handling duplicate Pixel and Conversions API events). Nothing is sent anywhere.
Want server-track-lab to build this body for you? Send one event to the playground and see the exact payload. Related: dedup guide · hashing tool · event_id generator.
POST /api/v1/track call: we normalize, hash, dedupe on event_id and forward to Meta CAPI. Free for 1,000 events a month, then CA$2 per 1,000. Get a free API key · Try the playground · API docsFAQ
Does this send my payload to Meta?
No. All checks run in your browser. Nothing is sent to Meta or to server-track-lab. To see what server-track-lab would send, use the playground.
Which rules does it check?
Only rules from Meta's own Conversions API docs that our guides cite: the data array, event_name, event_time and the 7-day limit, event_id for deduplication, action_source, event_source_url and client_user_agent for website events, and which user_data fields must be hashed or left unhashed.
Does a pass mean Meta will accept my event?
No. It means the body passes these documented checks. Meta can still reject events for other reasons, such as an invalid access token or pixel ID. Use Meta's Test Events tool to confirm delivery.
Why is a missing event_id only a warning?
Meta marks event_id as optional, but recommends it for deduplication. If the same conversion is also sent from the browser Pixel, you need it.