# Conversions API

**URL:** <https://community.hubspot.com/t/conversions-api/124776>\
**Category:** Reporting & Analytics\
**Tags:** how-to, enterprise\
**Created:** [January 26, 2025, 10:53am UTC](https://community.hubspot.com/t/conversions-api/124776 "2025-01-26T10:53:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![CBeardsley](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/cbeardsley/32/205041_2.png) [@CBeardsley](https://community.hubspot.com/u/CBeardsley)\
**Post date:** [January 26, 2025, 10:53am UTC](https://community.hubspot.com/t/conversions-api/124776/1 "2025-01-26T10:53:27Z")

</div>

I am wanting to connect Linkedin to Hubspot in order to use the Conversions API as documented here [Create and sync ad conversion events with your LinkedIn Ads account](https://knowledge.hubspot.com/ads/create-and-sync-ad-conversion-events-with-your-linkedin-ads-account)  
However, I’m also sending events via the pixel in Google Tag Manager. How would I deduplicate the same events coming from both sources? Could I send an eventId as a hidden field to Hubspot which then sends this on to Linkedin using the above integration and then also send the eventId with the same pixel event, after which Linkedin deduplicates? I know that’s how it SHOULD work but I’m unsure if the native Hubspot-Linkedin integration would actually send the eventId to Linkedin allowing for this.

---

<div class="post-metadata">

**Author:** ![GodMode9](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/godmode9/32/77269_2.png) [@GodMode9](https://community.hubspot.com/u/GodMode9)\
**Post date:** [January 27, 2025, 7:54am UTC](https://community.hubspot.com/t/conversions-api/124776/2 "2025-01-27T07:54:40Z")

</div>

The Conversions API is a game-changer for tracking events server-side. It ensures more accurate data and better privacy compliance compared to browser-based tracking. If you have not implemented it yet, it is definitely worth considering for improving conversion accuracy!
