The Instagram pixel on Shopify
Also called the Meta pixel, used for Instagram ads · Updated
There is no Instagram pixel. Instagram ads are bought through Meta Ads Manager and tracked with the Meta pixel, so the ID you need is the same one Facebook ads use. If Instagram conversions are missing from your reports, the cause is almost never a missing pixel — it is a pixel that stops at the cart, or events the browser dropped before they reached Meta.
Instagram pixel at a glance
- ID format
- The Meta pixel ID — 15 or 16 digits
- Where to find the ID
- Meta Events Manager → Data sources → your pixel
- Server-side API
- Conversions API
- Ad surfaces covered
- Instagram feed, Stories, Reels, Explore, Shopping tags
Copy the ID from Instagram’s own dashboard rather than typing it — a transposed digit produces a pixel that installs cleanly and reports nothing.
Events the Instagram pixel accepts on Shopify
| Event name | When it fires |
|---|---|
ViewContent | Product views from a Reels or Stories tap-through. |
AddToCart | The step Instagram traffic drops off at most. |
InitiateCheckout | Needed for checkout-intent audiences. |
Purchase | Attributed to the Instagram placement in Ads Manager. |
Server-side tracking: Conversions API
The same Conversions API setup covers Instagram placements. There is no Instagram-specific endpoint or token.
What goes wrong with the Instagram pixel on Shopify
- Instagram in-app browser sessions are still browser sessions. iOS tracking prevention applies, which is why server-side tracking usually recovers more Instagram conversions than Facebook ones.
- Instagram Shopping product tags and pixel tracking are separate systems. A working catalog does not mean a working pixel.
- Attribution windows shortened after iOS 14. A Reels view that converts three days later may simply fall outside the window rather than be missing.
Why Instagram conversions look lower than Facebook’s
Instagram traffic is overwhelmingly mobile and overwhelmingly iOS, which is the worst combination for browser-based tracking. App Tracking Transparency, Safari’s Intelligent Tracking Prevention and short cookie lifetimes all bite hardest exactly where Instagram’s audience sits, so the same pixel setup reports a smaller share of Instagram sales than Facebook sales.
The practical consequence is that Instagram usually shows the largest lift when server-side tracking is switched on. Stores that see a modest improvement on Facebook placements often see a much larger one on Reels and Stories, because those are the placements where the most events were being lost in the first place.
In-app browsers and what they break
A tap on an Instagram link opens Instagram’s own embedded browser, not Safari or Chrome. That browser has its own cookie jar, which is discarded more aggressively, and it does not share state with the browser the shopper would normally use. A shopper who browses in-app and then returns later in Safari looks like two different people to a browser-based pixel.
Server-side events sidestep this because they are keyed off the Shopify order and the customer information attached to it, not off a cookie that may already have been thrown away. It is the same mechanism that fixes the iOS problem, applied to a different symptom.
Step-by-step installation
This page is the reference. For the click-by-click walkthrough, including the Events Manager side of the setup, read the full guide.
Meta pixel setup for Shopify, start to finish →Related reading
- The Facebook Conversions API on Shopify
How the Meta Conversions API recovers Shopify conversions lost to iOS 14, ad blockers and Safari, what event deduplication does, and how to set it up.
- Facebook pixel not working on Shopify: 7 causes and fixes
Why your Shopify Facebook pixel shows no activity, misses purchases or fires twice, and how to fix each cause. Covers checkout, blockers and duplicates.