Hubspot injecting previously called fb/google pixels

[JBR69007]

Hi all,

so we recently activated Hubspot CRM connection to Facebook CAPI/Google/LinkedIn for to send offline events as custom conversion events in the ads platforms, and to do so we had to connect pixels in Hubspot.

Since then, Facebook is giving me the warning that my pixels started receiving events from other domains. 

I checked, and it's true, I have two websites for two different brands, and both brands have their own ad accounts/pixels.

And now both websites call both pixels because hubspot injects them. We don't want hubspot to inject anything as we already use GTM for this kind of tracking. Does anyone have a solution to keep the ad accounts connected in hubspot with leadgen sync and offline events but not the injection of pixels that are already declared ?

[SanjayKumar]

Hi @JBR69007,

 HubSpot auto-injects tracking pixels across forms, landing pages, and domains. But if you’re already handling all tracking via GTM, and don’t want HubSpot to double-fire or cross-fire pixels.To overcome this situation, you can do :
 1. Stop HubSpot Injecting Pixels but Keep the Integration
 To do this

• Go to Ads → Settings → Tracking.
• Here you’ll see the option for “Automatically add tracking pixels to my HubSpot content”.
• Toggle it off

( this will stop HubSpot from injecting Facebook/LinkedIn/Google pixels into your sites and forms, but the ad accounts remain connected for: Offline conversions (CAPI) | Lead syncing)

2. Validate the setup
In Facebook Events Manager, check the Event Deduplication tab:

• Make sure you’re sending event_id with both GTM and HubSpot events to prevent double-counting.
• In Google Ads, confirm your CAPI/Offline conversions from HubSpot are showing in Conversion Uploads.

Since you’re already pushing events via GTM, make sure GTM handles: Web pixel firing (Pageview, Leads, etc.)If you still see cross-domain issues, you can restrict which domains HubSpot tracks by going to HubSpot Ads. Tracking Settings and ensuring only the correct domain is included.

[JBR69007]

Thanks @SanjayKumar, this is the option I've been looking for, but can't find it : 

neither through Parameters > Marketing > ads nor through the left menu > Marketing > ads.

Event when going to Parameter > Tracking & analytics

Do you perhaps have a url or can send a screenshot of how it looks on your side so that I can investigate or contact the support to ask them why I don't have this option ?

Thank you very much

[BérangèreL]

Hi @JBR69007 and welcome, we are so glad to see you here!

Thanks for asking the HubSpot Community and thanks for your help @SanjayKumar and @GiantFocal!

I'd love to put you in touch with our Top Experts: Hi @Teun, @AnzeKoprivec and @derekcavaliero do you have other suggestions to help @JBR69007, please?

Have a great day and thanks so much for your help!
Bérangère

[BérangèreL · Accepted solution]

Hi @JBR69007, I hope that you are well!

I just wanted to check in on you, do you still need help?

Currently, when you connect your Facebook, Google, or LinkedIn ad accounts to HubSpot for lead syncing and offline events, HubSpot will inject the respective tracking pixels onto your website by default.

This can indeed result in pixels being fired on multiple domains if your HubSpot tracking code is present on more than one site.
 

At the moment, there isn’t a native setting in HubSpot that allows you to keep the ad accounts connected for lead syncing/offline events but prevent automatic pixel injection. 

You might want to check the "Limit data use" section on this article "Install pixels from external ad networks" that might be of interest.

If you still need help, let's see if other Experts and Community Members can help: Hi @AnzeKoprivec, @AudreyBouclin, @wacmediya, @matthew-aire and @PremKannan do you have other suggestions to help @JBR69007, please?

Have a wonderful day and thanks so much!
Bérangère

[GiantFocal]

Hi @JBR69007,

Sometimes, tracking codes are added directly into templates, header, or footer HTML instead of through HubSpot’s tracking or integration tools. Even after disconnecting or disabling these tools, remnants can remain in custom code areas.

What you can do is inspect all templates and global modules for any leftover tracking code. Remove any outdated pixel scripts you find there.