FB Pixel: Install Natively or Via HubSpot?

[rlifestorage]

Our dev team noticed that we had accidentally installed the Facebook pixel twice on our site via Google Tag Manager: once from Facebook natively, and once from Hubspot's tracking code. They are essentially asking, which piece of code should we keep? Both pieces of code contain the Facebook pixel, but one piece of code comes from HubSpot, and one comes natively from Facebook.

We don’t need or want two instances of the Facebook pixel, so the question is: is there any benefit to installing the Facebook pixel within HubSpot’s code versus installing it from Facebook’s code?

If we were to remove Facebook's version of the code, our concern is losing the conversion event tracking that we set up manually using Facebook's method. I understand that if we don't have the HubSpot tracking code on our website, we will lose some website tracking in HubSpot so I wouldn't want to remove that, but it seemed like they were toying with the idea of editing the HubSpot code to remove "facebook.js" since we already have the Facebook pixel installed natively. What do you think?

[Krystina]

Hi @rlifestorage,

The only benefit to leveraging a HubSpot Facebook pixel is that you can then build your ad audiences in HubSpot. But if you're using Facebook Business Manager to manage your audiences and launch ads, then that wouldn't really make sense. 

I'd recommend just leverageing the generic HubSpot tracking pixel like the one below and keep Facebook separate. 

Facebook's pixel can also do advanced event tracking as you mentioned to track different objectives. I wouldn't remove it. 

[HEvola]

hi krystina, we are implementing hubspot tracking code and are taking your advice to not use the hubspot pixel code. Just to confirm, if we install the hubspot tracking code and SKIP the part where we use facebook pixel within hubspot then we will be all clear to embed the pixel code from facebook onto our website. 

thanks in advance

[anthonyrichards · Accepted solution]

We use Hubspot to launch it so we aren't double counting, but we use Google tag manager to fire additional lead tracking: 

<script>
  fbq('track', 'Lead');
</script>

based on certain triggers we set up. It amends that Lead code to your base pixel. 

Everything works like a charm.