Quick Answer: Yes. Funnelish, Checkout Champ, Lightfunnels, and any custom landing page outside your core storefront need their own tracking, even if your headless Shopify store's tracking works perfectly. They're separate environments with their own codebases and script placement rules, so nothing carries over automatically. On Funnelish, the tracking script has to load in the page head and can't be lazy-loaded, or events fire too late and go missing. Verify each funnel builder separately by comparing Meta events from its URLs against real orders for the same window.
Key Takeaways
- Your headless storefront and your funnel builder are two different tracking environments. Fixing one does nothing for the other.
- On Funnelish, a lazy-loaded or body-placed script is the most common cause of silent tracking failure.
- Placement rules differ between Funnelish, Checkout Champ, and Lightfunnels, so check each one on its own.
- The same applies to agency-built campaign pages and any other page outside your main codebase.
- Funnel pages get missed because a different team usually sets them up. Give someone explicit ownership.
Most headless Shopify tracking conversations focus on the core storefront: Hydrogen versus custom JavaScript, and the theme layer that's no longer there. But a lot of brands running headless also run a separate landing page builder on top of it, such as Funnelish, Checkout Champ, or Lightfunnels, for specific campaigns or funnels. That layer has its own server-side tracking requirements, and it doesn't inherit whatever's working on the main site.
Why is a landing page builder a separate tracking problem?
From a tracking standpoint, your headless storefront and your landing page builder are two different environments. Fixing Meta Pixel tracking on your Hydrogen or custom JavaScript storefront doesn't touch a Funnelish page, because that page isn't part of the same codebase. It's a separate tool rendering its own pages, and any tracking script has to be added to it independently.
That makes funnel pages a common blind spot. Your main site's tracking working tells you nothing about your landing pages. Every builder in use is its own implementation, with its own placement rules. And if the funnel runs on a different domain from your store, cross-domain tracking has to be configured too, or a shopper's session splits in two between the funnel and checkout.
Where does the Funnelish tracking script need to go?
On Funnelish, the tracking script has to load in the page head, not the body, and it can't be lazy-loaded. Lazy loading introduces a delay, and that delay is enough to break event timing.
In practice, AddToCart or Purchase events from that landing page show unusually low, sometimes near-zero, volume in Meta Events Manager, even while real orders come in through Shopify. Nothing throws an error. The page just quietly stops reporting what's actually happening on it.
Do Checkout Champ and Lightfunnels follow the same rules?
The principle is the same, but the exact placement rules differ by platform. Any landing page builder sitting outside your core storefront needs its own explicit tracking implementation, checked independently. A script that works on Funnelish won't necessarily behave the same way on Checkout Champ or Lightfunnels, because each has its own rendering behavior and its own rules for where a script needs to sit.
Does this apply to fully custom pages too?
Yes. Funnelish and Checkout Champ are the common examples, but the same issue applies to any custom page outside your core storefront: a bespoke landing page built by an agency, a one-off campaign page, anything that isn't part of your main Hydrogen or custom JavaScript codebase. If it's a separate build, it needs its own tracking script, checked on its own.
If you'd rather not hand-write that script, Aimerce generates the tracking JavaScript for Funnelish, Checkout Champ, and custom landing pages, ready to place in the page head.
How do you check whether your landing pages are tracking correctly?
Run the same verification you'd use for the core storefront, scoped to landing page traffic:
- Filter by URL. Pull Meta events from landing page URLs specifically, not the domain as a whole.
- Compare with real results. Check purchase or lead events from those pages against actual orders or leads for the same window.
- Check Funnelish placement. Confirm the script is in the head and not lazy-loaded, the single most common cause of silent failure on that platform.
- Check cross-domain setup. If the funnel and your store use different domains, confirm the session carries across.
- Repeat per builder. A fix on Funnelish says nothing about Checkout Champ.
- Watch for double counting. If both the funnel tool and your store send purchases, make sure they share an event ID. Our guide to deduplication errors in Meta Events Manager explains how.
Landing page builders compared
| Headless storefront | Funnelish | Checkout Champ and Lightfunnels | Agency or custom pages | |
|---|---|---|---|---|
| Inherits storefront tracking? | Not applicable | No | No | No |
| Script placement | Built into your frontend | Page head, not lazy-loaded | Platform-specific rules | Depends on the build |
| Most common failure | Missing or mistimed events | Lazy-loaded script misses events | Script placed where the platform doesn't run it in time | No tracking added at all |
| How to verify | Meta purchases vs. Shopify orders | Events from funnel URLs vs. orders | Events from funnel URLs vs. orders, per platform | Events from page URLs vs. orders or leads |
Why does this tracking gap get missed so often?
A landing page builder usually gets set up by whoever runs a specific campaign, often a media buyer or an agency, not the team that owns the core storefront's tracking. That split in ownership is exactly why this layer gets missed. Nobody's explicitly responsible for checking it, so it doesn't get checked until a campaign's numbers look off and someone finally traces it back to the landing page.
FAQ
Does a Funnelish landing page need its own Meta Pixel setup? Yes. Funnelish sits outside your core storefront, and its tracking script must load in the page head and can't be lazy-loaded. A working Conversions API setup on your main site doesn't extend to Funnelish automatically.
Why would a landing page builder's tracking fail without any errors? Script placement issues, like lazy-loading a tag on Funnelish, delay when the script fires. It can miss the event entirely or fire against outdated page data, and none of this shows an error. It just shows up as lower event counts.
Do Checkout Champ and Lightfunnels have the same tracking requirements as Funnelish? The principle is the same: each is a separate environment that needs its own tracking. The specific placement rules differ by platform, so verify each one independently.
Does headless Shopify tracking cover landing page builders automatically? No. A headless storefront's tracking covers the storefront itself. Landing page builders are separate tools that need their own script and their own verification.
Do funnel pages on a different domain need cross-domain tracking? Yes. If the funnel and your store run on different domains, cross-domain tracking has to be configured, or the session that started on the funnel won't connect to the purchase.
Sources
[1] Aimerce, "How to Fix Event ID Deduplication Errors in Meta Events Manager,"
[2] 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