Establish the event key
Compare the pixel ID, event name and event ID used on both paths.
One event key. Two delivery paths. Spot mismatches in your Pixel and server-side conversion exports before they muddy the conversation.
Paste or upload event data. Input is processed in this browser tab only. Do not upload raw customer identifiers or secrets.
CSV or JSON. Headers: channel, pixel_id, event_name, event_id, amount, currency, order_ref, timestamp_ms.
Inspect exceptions before publishing a conclusion.
Load the illustrative sample to see the workflow, or use your own sanitized event records.
EventProof reviews uploaded CSV or JSON locally. It does not verify platform delivery, consent, attribution, or whether an ad conversion was credited.
Read the implementation field guide ↗Compare the pixel ID, event name and event ID used on both paths.
Review unpaired events, repeated sends and inconsistent conversion values.
Export a scoped exception register for your tracking engineer to investigate.