LAB 02 / CONVERSION TRACKING
One conversion.
Two signals. One event ID.
See how a browser-side event and server-side event can share the same event ID so a downstream platform can deduplicate them. This is an in-browser simulation: it does not send data to Meta, GA4, GTM or any server.
DEMO DATA ONLY — Event payloads shown here are examples, not validated network traffic or proof of a real production integration. Never enter personal or sensitive information.
Generate a test event
In an actual build, browser and server events would use consent-aware instrumentation, a backend and platform-specific validation tools.
Latest event outcome
Unique conversions simulated: 0 · Raw signals: 0
Generate an event to inspect the payloads.
What this proves—and what it doesn't
It demonstrates event mapping, shared IDs, payload structure and simple deduplication logic. It does not prove integration with Meta's Conversions API, production delivery, cookie consent compliance or accurate advertising attribution. Those require platform credentials, real events and testing.