WORKSPACES / EVENT RECONCILIATION
PRIVATE BY DESIGNDocumentation ↗

The detail is
the difference.

One event key. Two delivery paths. Spot mismatches in your Pixel and server-side conversion exports before they muddy the conversation.

RECONCILIATION MODELFIG. 001
INPUT / ASHARED EVENT KEYINPUT / B
PIXEL Browser
CAPI Server
01 MATCHED Same identifier
02 REVIEW Value / currency
03 UNPAIRED Check delivery path
ILLUSTRATIVE LOGIC · NOT A LIVE RESULTPIXEL × CAPI ↗
01 Import your export02 Match identifiers03 Examine exceptions04 Download the audit
INTERACTIVE / LOCAL TOOL 03
YOUR WORKBENCH, READY

Audit the actual records.

Paste or upload event data. Input is processed in this browser tab only. Do not upload raw customer identifiers or secrets.

EVENTPROOF / WORKSPACE 01YOUR DATA NEVER LEAVES THIS BROWSER
Event reconciliation / workspace
01

Input records

CSV or JSON. Headers: channel, pixel_id, event_name, event_id, amount, currency, order_ref, timestamp_ms.

No records loaded
02

Audit results

Inspect exceptions before publishing a conclusion.

EVENTS—
PAIRED KEYS—
EXCEPTIONS—
EXCEPTION REGISTERAWAITING INPUT
Clarity starts with a comparison.

Load the illustrative sample to see the workflow, or use your own sanitized event records.

LOCAL PROCESSING · No upload, no server storageCOMPARISON ≠ PLATFORM DELIVERY CONFIRMATION

Measure what
the exports can prove.

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 ↗
01

Establish the event key

Compare the pixel ID, event name and event ID used on both paths.

IDENTIFY
02

Surface conflicting records

Review unpaired events, repeated sends and inconsistent conversion values.

TRIAGE
03

Hand over clear evidence

Export a scoped exception register for your tracking engineer to investigate.

HANDOFF