What the integration covers
- Per-channel Pixel: each sales channel gets its own Meta Pixel, switched on independently.
- Standard commerce events: ViewContent, AddToCart, InitiateCheckout, Purchase and Lead fire against the platform’s actual catalog and order data.
- Custom events alongside the standard ones: a B2B-specific audience (RFQ submitted, quote accepted) is added without replacing or breaking the standard events that reporting and lookalike audiences depend on.
Why that separation matters
Custom event names are added next to the standard set rather than replacing them, so building a quote-request audience for retargeting does not come at the cost of accurate Purchase reporting.
The visitor’s consent decides, not the code
The Pixel only loads after acceptance in the consent banner, the same mechanism as Google Tag Manager and LinkedIn Ads. No Meta script runs before that acceptance, so turning the Pixel off for a given sales channel is a consent-configuration change, not a code change.