Facebook CAPI Deduplication – Send Matching event_id in Both Pixel & Server Events
P
Pascal Scott
Currently, our Pixel and CAPI events are missing a shared event_id, which prevents Facebook from properly deduplicating events. This results in inflated event counts and inaccurate tracking. We need to ensure that the same event_id is passed in both the browser (Pixel) and server (CAPI) events — especially for Purchase and InitiateCheckout to maintain clean, accurate data and avoid over-reporting. ( Picture reflect the native pixel and CAPI Setup in a sale funnel)
Log In
H
Homero Perez
THIS PROBLEMA IS HUGE! GHL should do something asap
M
Miquel Agencia FC
M
Miquel Agencia FC
Sales and Marketing could you please take into account this case?
Could be possible to capture event_id to be used in both workflows with the Facebook API conversion action and the same time to be used with browser (pixel) that could be included in pages via script something like this <script>
fbq('track', 'CompleteRegistration', {
event_id: 'unique_registration_id_xxxxxxxxxxx' // Replace with your unique ID
});
</script>