Quick Answer: Most headless Shopify tracking problems share one root cause: there's no theme layer, so tracking apps have no automatic hook to plug into. On top of that, seven specific setups create their own gaps: checkout that redirects to another platform, custom popups and quizzes, multiple Meta Pixels, landing page builders like Funnelish, subscription renewals, health and wellness data restrictions, and the fact that headless builds have no baseline layer catching what gets missed. Each needs its own check. Purchases themselves are the safest part, because orders still land in Shopify and can be sent to Meta and Google server-side from Shopify's order data.
Key Takeaways
- On headless, every custom element is its own small integration. Nothing inherits tracking just because it lives on the same domain.
- If checkout leaves your domain entirely, no script can see the purchase. You need an order data connection back from that platform.
- Running more than one Meta Pixel means verifying each pixel separately against Shopify orders.
- Funnel builders have their own script placement rules, so a fix on your main storefront doesn't carry over.
- Subscription renewals and health and wellness restrictions can distort Meta data even when the implementation is technically correct.
Most headless Shopify tracking problems come from the same root cause: no theme layer means no automatic hook for tracking apps to plug into. But a handful of specific setups create their own version of that problem, and they don't show up until a brand happens to have exactly that configuration. These are worth knowing before you assume your headless build is a standard case, and before a Meta Pixel or Conversions API setup gets blamed for a gap it didn't cause.
Here are the corner cases we see most often, and what's actually happening in each one.
1. What happens when checkout redirects to another platform?
Some brands route checkout through a separate platform entirely, such as Walmart, Amazon, or Instacart, rather than keeping the transaction on their own domain. In that setup, your Meta Pixel never sees the purchase happen. The order may exist in Shopify, but the conversion event doesn't, because the transaction happened on infrastructure your pixel has no access to.
Server-side tracking can't quietly work around this. It requires a specific integration with whatever platform actually processes the order. It's worth checking for explicitly, since it's easy to assume "checkout" always means "checkout on my own domain." We cover this case in depth in "Tracking Purchases Without a Shopify Checkout Page."
2. Do custom popups and quizzes need separate tracking?
Yes. If an email capture popup or a quiz isn't running through Shopify's native tools or a supported email platform like Klaviyo, Omnisend, or Sendlane, it likely isn't wired into your Conversions API setup automatically. A quiz built on a third-party tool needs its own explicit Lead event tracking. It won't inherit anything from your core Purchase or PageView implementation just because it lives on the same domain.
This matters more on headless builds, because there's no theme-level default doing any of this work already.
3. How do you verify tracking when running more than one Meta Pixel?
Multi-brand operations and agency-managed accounts sometimes run more than one Meta Pixel on the same store. If that's your setup, the standard verification check, comparing Meta purchase events against Shopify order counts, has to run per pixel, not once for the account.
A clean match on one pixel says nothing about a second. Each needs its own comparison before you can trust the Meta ROAS numbers either pixel reports. Our guide to fixing the Shopify vs. Meta revenue discrepancy walks through that comparison.
4. Why does script placement matter for landing page builders?
Funnelish, Checkout Champ, and similar tools sit outside your core storefront, and they come with their own script placement requirements. On Funnelish, the tracking script has to load in the page head, not the body, and it can't be lazy-loaded. A lazy-loading delay is enough to break event timing: the trigger fires too late, or against a page state that's already changed.
The exact rules depend on which tool you use, which is why generic server-side tracking advice doesn't always hold up on a funnel builder. See "Funnelish and Checkout Champ Tracking on Headless Shopify" for the full breakdown.
5. How should subscription brands handle rebills and renewals?
System-generated rebills and renewals get counted as new purchases by default, which inflates purchase counts and distorts Meta ROAS. Handling this correctly means keeping one-time purchases, first subscription orders, and renewals distinct, rather than letting every recurring charge count as a fresh conversion.
A manual implementation has to build that separation explicitly. Aimerce keeps automatic renewals out of your Meta Purchase event using Shopify order tags, with no setup, while the first subscription order still goes to Meta. It also sends three custom events, OTP (one-time purchase), Subscribe (first subscription), and Renewal, so you can build custom metrics for each in Ads Manager.
6. Why do health and wellness brands see different tracking results?
Since early 2025, Meta has restricted the event data brands in health and wellness categories can share, and many can no longer optimize for Purchase or other lower-funnel events. That has nothing to do with headless architecture. Brands in this category may see event data limited no matter how well their Conversions API is implemented, because the restriction happens on Meta's side.
If you're auditing a health or wellness brand and the numbers look off after everything else checks out, check the data source category in Meta Events Manager before rebuilding anything. Our post on Meta's health and wellness data sharing restrictions explains the levels.
7. Why do these edge cases matter more on headless builds?
None of these are exclusive to headless. A checkout redirect, a stray popup, or a multi-pixel setup can exist on a theme store too. But on a theme store, the core tracking layer usually still works when one of these is missed, so the damage stays contained.
On headless, there's no baseline layer catching everything else by default. Miss one of these, and it's not an exception to an otherwise solid setup. It's one more gap in a system where every piece had to be built by hand.
The exception is the purchase itself. On a headless store that still uses Shopify's checkout, orders are created in Shopify, so server-side tracking on Shopify can send them to Meta and Google from Shopify's order data, whatever the frontend does.
The 7 corner cases at a glance
| Corner case | What you'll see | Where to start |
|---|---|---|
| Checkout redirects off-site | Real orders with no Purchase event anywhere | Build an order data connection back from the checkout platform |
| Custom popups and quizzes | Leads collected but no Lead events in Meta | Add explicit Lead event tracking per tool |
| Multiple Meta Pixels | One pixel matches Shopify, another doesn't | Verify each pixel against Shopify orders separately |
| Landing page builders | Near-zero events from funnel pages while orders come in | Check script placement rules for each builder |
| Subscription renewals | Purchase counts and ROAS higher than reality | Keep renewals out of the Purchase event |
| Health and wellness restrictions | Limited or missing lower-funnel events despite a clean setup | Check the data source category in Events Manager |
| No baseline layer on headless | Gaps that would be contained on a theme store spread further | Treat each element as its own integration and verify it |
FAQ
Does headless Shopify tracking need different handling for subscription products? Yes, if accurate Meta ROAS matters. Without separating one-time purchases from renewals, recurring charges inflate purchase counts and distort attribution, regardless of framework.
Can Meta Pixel track a purchase that happens on a third-party checkout platform? Not without a specific integration to that platform. If checkout redirects to Walmart, Amazon, or a similar service, the transaction happens outside your domain, and the Conversions API has no visibility into it by default.
Why would tracking still look broken for a health and wellness brand after fixing implementation issues? Meta restricts the event data health and wellness brands can share. Some of what looks like a tracking gap may be a platform-level restriction rather than an implementation problem.
Do landing page builders need their own server-side tracking setup? Yes, in most cases. Tools like Funnelish and Checkout Champ sit outside the core storefront and have their own script placement rules, so a setup built for the main site doesn't automatically extend to them.
Do headless Shopify stores still send purchases server-side? If the store uses Shopify's checkout, yes. Orders are created in Shopify, so a server-side tracking tool can send them to Meta and Google from Shopify's order data regardless of the frontend.
Sources
[1] Aimerce, "Here's What to Know: 2025 Meta Health & Wellness Data Sharing Restrictions," [2] Aimerce, "How to Fix the Shopify vs. Meta Revenue Discrepancy," [3] Aimerce, "How to Set Up Server-Side Tracking for Shopify,"
Related reading
Try Aimerce Pixel Risk-Free
for 30 Days
Most teams see results within 2 weeks.
Money-back guarantee.
It pays for itself, or you don't pay anything.
30-Day Aimerce Pixel Free Trial