Meta CAPI Payload Validator
Test and inspect your Meta Conversions API (Graph API) request bodies. Detect un-hashed customer data (PII leaks), missing action_source, improper Unix timestamps, and schema errors before sending to Meta.
Ready for inspection
Paste a CAPI payload or click 'Valid Sample' to evaluate parameters against Meta Graph API v19+ specs.
Payload Specification Audit
- Top-Level 'data' ArrayAwaiting input
- event_name & event_timeAwaiting input
- action_source ('website', 'app')Awaiting input
- user_data SHA-256 HashingAwaiting input
- event_id (Deduplication Key)Awaiting input
Need error-free Meta CAPI implementation?
I configure server-side GTM containers that format, validate, and hash Meta CAPI events automatically with 100% schema compliance.
How to use the Meta CAPI Payload & Server Event Validator
Meta Conversions API (CAPI) requires server payloads to strictly adhere to Graph API schemas. Missing required parameters, improper timestamp formatting, unhashed user data, or syntax errors cause silent event drops in Events Manager. This validator checks JSON payloads against official Meta specifications.
Step by step
- Paste your raw Meta CAPI JSON payload or server event request into the editor.
- Click Validate to parse the data array, event_name, event_time, user_data, and custom_data objects.
- Check for missing required parameters (like event_source_url, action_source, or user identifiers).
- Review automated syntax error warnings and format corrections.
How to read your result
Schema Valid (Ready for CAPI)
Payload adheres strictly to Meta Conversions API Graph API specifications and will process with high Event Match Quality.
Schema Validation Errors Detected
Payload contains formatting errors, unhashed PII, or missing mandatory fields that will cause Meta API error responses.
Common mistakes
- Sending event_time as a millisecond timestamp instead of Unix epoch seconds (10 digits).
- Forgetting action_source: "website" on server events.
- Passing unhashed plain-text email or phone strings inside user_data.
Questions
What fields are mandatory in a Meta CAPI request?
Every event requires event_name, event_time (Unix seconds), action_source ("website"), and at least one user_data parameter (like em, ph, or client_ip_address).
How do I test live Meta CAPI events?
Use the test_event_code parameter inside your server payload and monitor incoming hits in Events Manager → Test Events tab.
Need error-free Meta CAPI implementation?
I configure server-side GTM containers that format, validate, and hash Meta CAPI events automatically with 100% schema compliance.