Shopify Meta Pixel on Framer: Events That Actually Fire
Does the Shopify Meta pixel work on a Framer storefront? Partly. Shopify fires purchase events at its own checkout, but catalog and cart events on your Framer pages are yours to send. Pair a Framer-side pixel with the Conversions API so both halves of the funnel get attributed instead of just the last one.
That split is the whole problem. A Framer + Shopify store is two domains wearing one brand, and Meta treats them as two domains. Most teams discover this when ROAS looks fine in Shopify and terrible in Ads Manager — the purchases are real, the signals leading to them simply never arrived. If you set this up years ago as a Shopify Facebook pixel and never revisited it, the install is almost certainly scoped to the wrong half of your store.
Event ownership is the term worth defining early: for every event in your funnel, exactly one surface is responsible for firing it, and on a split-domain store that surface is not always the one you assume.
Does the Shopify Meta pixel reach your Framer pages?
No — and the documentation is explicit about where it stops. Shopify's pixels load on its storefront, checkout, thank-you page and order-status page, with customer account pages limited to page views after you connect a custom subdomain, per Shopify's own pixels overview. A Framer storefront is none of those surfaces.
So the Shopify side of your stack keeps working perfectly and keeps reporting a funnel that starts at checkout. Everything a shopper did on your Framer product page — viewed it, picked a variant, added to cart — is invisible unless you send it yourself. This is the same architectural seam that breaks Google Analytics 4 on a Framer-fronted Shopify store, and it has the same shape: Shopify's tooling is scoped to Shopify's pages.
Which events do you own, and which does Shopify?
Start with the table, because the answer is per-event rather than global. Five events, five different owners and failure modes:
| Event | Where it must fire | Browser or CAPI | Cross-domain issue | How to verify |
|---|---|---|---|---|
| PageView | Every Framer page | Browser pixel | None — same domain as the pixel | Test Events shows it live as you browse |
| ViewContent | Framer product/collection pages | Browser, CAPI as backup | Blocked browsers drop it entirely | Filter Test Events by ViewContent, check content_ids |
| AddToCart | Framer cart interaction | Browser + CAPI, shared event_id |
Shopify's pixel never sees it | Confirm one event, not two, in Events Manager |
| InitiateCheckout | The handoff to Shopify's domain | CAPI preferred | _fbp does not travel to the new domain |
Compare counts against sessions reaching checkout |
| Purchase | Shopify checkout | Shopify's pixel + CAPI | Attribution lands on Shopify's domain | Match order count in Shopify to Purchase count |
Two lines deserve emphasis. AddToCart is pure gap — neither Shopify's pixel nor any Shopify app can fire it from a page Shopify does not serve. And InitiateCheckout is where identity breaks: Meta stores the browser ID in a _fbp cookie and the click ID in _fbc, both set under your domain. Your domain is the Framer one. The moment the shopper lands on Shopify's checkout, those cookies are not readable there.
Why is my Shopify Meta pixel not working on custom pages?
Usually because something fired, just not what you think. Three causes, in the order they actually occur:
- The base pixel never loaded on Framer. Shopify's Meta app installs into Shopify, not into your Framer site. You need the base code as a Framer custom script.
- The event fired but carried nothing. A
ViewContentwith nocontent_idsis a page view with extra steps — it cannot be matched to a catalog product or optimized against. - The event fired twice. Browser and server both sent it without a shared ID, so Meta counted two.
The third one is the expensive one, because it inflates reported conversions and quietly corrupts optimization.
How do you stop double-counting between pixel and Conversions API?
Send a shared event_id and let Meta collapse the pair. The dedup rule is specific: when Meta finds a match between events sent within 48 hours of each other, it keeps only the first, and when a server and browser event arrive within five minutes it favors the browser event. For a redundant setup to deduplicate at all, both events need an identical event_name plus either a matching event_id or a combination of external_id and fbp.
Two practical constraints fall out of the same docs. Server events accept an event_time up to seven days old, and a single event older than that returns an error for the entire request — so a nightly batch job that retries a stale queue can silently drop a whole day. And event match quality is scored out of 10, for web events only, which is Meta telling you plainly that thin user_data is a ranked, visible weakness rather than a neutral choice.
For purchases, use the Shopify order ID as event_id. It is unique, stable, and available on both sides of the handoff.
What does Shopify server-side tracking actually cover?
It covers the fifteen customer events Shopify fires, and nothing outside them. The standard events list runs from page_viewed and collection_viewed through product_added_to_cart, checkout_started and checkout_completed — genuinely useful, but scoped to Shopify-served surfaces. A custom pixel subscribes to those events; you still write the forwarding code.
That sandbox has teeth. It cannot render UI, and it cannot detect DOM-scraped events, DOM-scraped metadata, emails or phone numbers lifted from the page, outbound link clicks, scrolling or heatmap clicks. Shopify is also direct about the support position:
"Adding and using custom pixels is unsupported by Shopify." — Shopify Help Center, Create custom pixel code
Which is a reasonable trade if you own the code. It is not a reasonable trade if a plugin owns it and you cannot see what it sends. The same transparency question decides whether a Buy Button is enough or a limit for your build.
How do you verify each event in Events Manager?
Verify per event, with Test Events open and a real session in another tab. Shopify conversion tracking on a split-domain store is never one green checkmark. Walk the funnel once: Framer home, product page, add to cart, checkout, purchase. You should see five distinct events, each once, each with a payload.
Then check three things nobody checks. Does ViewContent carry content_ids matching your Shopify product IDs? Does Purchase show one event per order rather than two? And is event_source_url pointing at your Framer URL, since Meta requires that field for website events sent through the Conversions API and expects it to match a verified domain?
If AddToCart counts sit near zero while Purchase looks healthy, you have confirmed the gap rather than fixed it. The cart events are simply not being sent — the same silence that makes abandoned cart email on a Framer storefront harder than it should be.
A build order that holds up
Base pixel on Framer first, so PageView is clean. Then ViewContent with real content_ids. Then AddToCart from the browser with an event_id, mirrored server-side. Then InitiateCheckout as a server event at the handoff, because that is the one the browser cannot carry across. Purchase last, keyed to the order ID.
A sync layer that already knows your product IDs makes steps two and three far less fiddly — FramerLink exposes the Shopify product data your events need to reference, so content_ids are not something you hand-maintain. But the sequence matters more than the tooling. Fire fewer events with complete payloads, verify each one, and your Framer storefront stops looking like a traffic source and starts looking like the funnel it is.
Frequently asked questions
Can I add the Meta pixel to a Framer site?
Yes. Framer lets you add a site-wide custom script, so the Meta base pixel loads on every Framer page and fires PageView normally. What it cannot do is reach Shopify's hosted checkout, so catalog and cart events come from Framer while Purchase stays on Shopify's side.
Do I need the Conversions API if I already have the Meta pixel?
On a split-domain store, effectively yes. The browser pixel is blocked or trimmed for a meaningful share of sessions, and your Framer domain cannot read Shopify's checkout. Server events fill both gaps, and Meta scores how matchable each one is on a 10-point scale.
Why does my Shopify purchase event show but not AddToCart?
Because Purchase happens on a Shopify-hosted page where Shopify's own pixel runs, and AddToCart happens on your Framer page where it does not. Shopify's pixels load on its storefront, checkout, thank-you and order-status pages only — not on a storefront you host elsewhere.
Does Shopify's custom pixel send events to Meta automatically?
No. A custom pixel subscribes to Shopify's customer events and you write the code that forwards them. It also runs in a restricted sandbox, so it cannot scrape the DOM for emails, phone numbers or outbound clicks, and Shopify lists custom pixels as unsupported.
Sources
- Server Event Parameters — Conversions API — Meta for Developers
- Conversions API Best Practices — Meta for Developers
- Customer Information Parameters — Conversions API — Meta for Developers
- Web Pixels API: Standard Events — Shopify
- Pixels overview — Shopify Help Center