← Selected work
MX Shop
The problem
Meta was not getting strong server-side signals.
Conversion reporting was hard to trust when browser data was blocked, and there was no clean way to test events or prove that deduplication worked.
The system
Layer 01
Dataset connection
Correct dataset selected in Events Manager, with the dataset ID and a test event code for validation.
Layer 02
GTM trigger + CAPI tag
A Conversions API tag with pixel ID, access token, and test event code, fired by a controlled trigger.
Layer 03
Deduplication
An Event ID variable added to both the Pixel tag and the CAPI tag so Meta can mark duplicates.
Layer 04
Fire control
CAPI fires only on selected events; the GA4 config carries client_id, transport_url, and event_id.
What I implemented
- 01Connected the correct Meta dataset and collected the dataset ID
- 02Generated a test event code to validate CAPI during setup
- 03Built the GTM trigger and Facebook Conversions API tag
- 04Imported the Event ID template and passed the ID into the Pixel and CAPI tags
- 05Confirmed browser and server events in Meta Test Events
Validation
Result
Browser + Server
Events validated in Meta Test Events
Processed
Browser PageView received and processed by Meta.
Deduplicated
Server PageView matched by event_id, no double counting.
Proof
Events visible in Meta Test Events, so tracking is working.
