# Facebook CAPI duplication - event\_id missing.

**URL:** <https://community.hubspot.com/t/facebook-capi-duplication-event-id-missing/135141>\
**Category:** APIs & Integrations\
**Tags:** professional\
**Created:** [June 25, 2025, 8:16am UTC](https://community.hubspot.com/t/facebook-capi-duplication-event-id-missing/135141 "2025-06-25T08:16:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![HCarless](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/hcarless/32/29368_2.png) [@HCarless](https://community.hubspot.com/u/HCarless)\
**Post date:** [June 25, 2025, 8:16am UTC](https://community.hubspot.com/t/facebook-capi-duplication-event-id-missing/135141/1 "2025-06-25T08:16:28Z")

</div>

When sending both CAPI and client-side events to the Facebook Pixel, the event\_id parameter is required for event de-duplication.  
Hubspot’s native Facebook Pixel integration sends an external\_id parameter (for both client and server-side events) which tells Facebook who the user is, but no event\_id is sent.

This is resulting in duplication of Lead events when a form is submitted.  
1. User submits form  
2. Client-side ‘Lead’ event is sent with external\_id identifying the user

3. Server-side ‘Lead’ event is sent with external\_id identifying the user

Outcome: Facebook Pixel records 2 Lead events.  
This was mentioned by several users during the beta testing of this feature circa 2021, but it isn’t clear whether this was ever fixed.  
Is there something I’m missing here?

---

<div class="post-metadata">

**Author:** ![GiantFocal](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/giantfocal/32/41969_2.png) [@GiantFocal](https://community.hubspot.com/u/GiantFocal)\
**Post date:** [June 26, 2025, 5:30pm UTC](https://community.hubspot.com/t/facebook-capi-duplication-event-id-missing/135141/2 "2025-06-26T17:30:22Z")

</div>

Hi @HCarless,

You’re not missing anything. This is a known limitation with HubSpot’s native Facebook Pixel integration. Currently, HubSpot sends the external\_id for both CAPI events, but does not include the event\_id parameter. The event\_id is what Facebook uses to de-duplicate events, so without it, you’ll see duplicate Lead events when both client and server events are triggered by the same form submission.

This issue has been raised by users since the feature’s beta, but as of now, HubSpot hasn’t updated its integration to support event\_id for de-duplication.

If accurate reporting is important for you, you have a couple of options:

- Use a custom implementation of the Facebook Pixel and CAPI outside of HubSpot, where you can control and sync the event\_id parameter yourself.
- Consider using a third-party integration or middleware that supports event\_id mapping for both client and server events.

If you stick with the native HubSpot integration, unfortunately, there’s no built-in fix at the moment. I recommend upvoting or commenting on related HubSpot Ideas or threads to help push this feature request forward.

Let me know if you need tips on custom setup or tools that can help!

---

<div class="post-metadata">

**Author:** ![JBahmann](https://avatars.discourse-cdn.com/v4/letter/j/cab0a1/32.png) [@JBahmann](https://community.hubspot.com/u/JBahmann)\
**Post date:** [November 24, 2025, 10:03am UTC](https://community.hubspot.com/t/facebook-capi-duplication-event-id-missing/135141/3 "2025-11-24T10:03:13Z")

</div>

**WE NEED THAT! HubSpot too often doesn’t think its features through completely.**