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.

Shopify Facebook & Instagram App + Multiple Pixels: The Global Track Bug and Duplicate Events

The Shopify Facebook & Instagram app sends events with `fbq('track', ...)`; if other Pixel IDs are initialized in the page, F&I events leak onto every pixel. Source, diagnosis and three fixes for duplicate events in multi-pixel Shopify setups.

TL;DR

The Shopify Facebook & Instagram app sends its events through fbq('track', ...), and that call reaches every Pixel ID initialized on the page. If a second Pixel ID exists in the store, the app's AddToCart and Purchase events land there too. The result is duplicate events in Events Manager, polluted EMQ and attribution conflicts. There are three ways out, and the choice depends on the constraints of the existing setup.

View Subscription Sign In