For companies managing multiple brands or properties within a single HubSpot portal, Meta conversion-event tracking currently creates a significant attribution issue.
When a Meta ad account is connected through HubSpot’s Ads tool and a conversion event is created through Marketing → Ads → Create Event, HubSpot adds that Meta account’s base pixel to the portal-wide HubSpot tracking code.
Because the same HubSpot tracking code is installed across multiple brand websites, the Meta pixel for one brand can then fire across every website connected to the portal.
For organizations with multiple brands, properties or business units, this can result in:
-
Meta pixels firing on websites they are not intended to track
-
Duplicate or inflated conversion events
-
Cross-brand attribution contamination
-
Unreliable campaign optimization and reporting within Meta
-
Difficulty maintaining separate advertising ecosystems while still using one HubSpot portal
HubSpot Support confirmed that this is currently expected behavior and that there is no setting to scope a Meta conversion event or base pixel to a specific Brand, domain or website.
Requested functionality
Allow HubSpot customers to define where an Ads conversion event and its associated Meta pixel are deployed, ideally by:
-
HubSpot Brand
-
Root domain or subdomain
-
Specific website/domain rules
For multi-brand organizations, conversion tracking needs the same level of segmentation that exists elsewhere in the platform. A Meta pixel connected for Brand A should not automatically fire on Brands B, C and D simply because they share a HubSpot portal.
This would make HubSpot’s native Ads conversion-event functionality significantly more usable for companies managing multiple brands, locations, properties or business units from one account.