Membership Required
You need to sign in and have a Premium subscription to access this content.
- 01
fbq('track', ...)fires the event on every initialized Pixel ID on the page; withouttrackSingle, scoping an event to a specific pixel isn't possible. Meta's official guidance confirms this. - 02 The Shopify F&I app uses the standard
fbq('track', ...)call; if extra pixels are present in the store, F&I events leak onto them. - 03 Shopify custom pixel Lax sandbox is isolated from the F&I global call; for multi-pixel scenarios, custom pixel + sandbox is the safest path.
- 04 Three clean fixes: single Pixel + CAPI, custom pixel sandbox isolation for extras, or all events routed through sGTM.
- 05 Disabling the F&I app affects Catalog and dynamic ads; weigh tracking cleanliness against the F&I feature set.
+ Does the Pixel installed by the Shopify F&I app affect Pixel IDs added through another channel?
Yes. When the F&I app calls fbq('track', 'AddToCart', ...), every Pixel ID currently initialized on the page receives the event. Meta's official docs confirm this: using track on pages with multiple Pixels causes over-firing; trackSingle is required to scope events to a specific Pixel.
+ Which events show this problem most clearly?
AddToCart, ViewContent, InitiateCheckout, Purchase. All standard events. PageView is affected too, but having PageView fire on every pixel is usually intended. Custom events (trackCustom) follow the same pattern.
+ How do I confirm the duplicate in Events Manager?
Run a test purchase with the same order id and watch Test Events. You'll see the same event_name on two different Pixel IDs, with different event_ids or no event_id. If the same Purchase shows on multiple pixels without event_id, Diagnostics will surface a 'Multiple events from same browser' warning.
+ Is disabling the F&I app's Pixel and using only Conversions API enough?
It's one clean fix. Turning off the F&I app pixel and routing CAPI through Shopify Customer Events / sGTM removes the duplicate entirely. The trade-off is that F&I app features like Catalog sync and dynamic ads weaken without a pixel. It's a deliberate trade-off.
+ We work with multiple agencies, each wants its own pixel. What now?
The cleanest path is one Pixel ID + CAPI, then share reports. If separate Pixel IDs are mandatory, add them as custom pixels in Shopify's Lax sandbox (don't inject into the theme); custom pixels run in their own sandbox and are not affected by the F&I app's global track call.