TL;DR
Most articles about Shopify Plus tracking rehash the same Customer Events setup that works on every plan. The actual Plus-only territory is narrower but genuinely more complex: B2B wholesale portals create separate buyer journeys that standard pixel logic misses entirely, Markets Pro splits your storefront across regions in ways that fragment attribution without explicit deduplication, and Hydrogen stores run on custom domains where standard checkout attribution breaks. If you're on Plus, these are the surfaces worth auditing first.
Key Takeaways
- Customer Events and the Web Pixels API are available on every Shopify plan, not Plus-only. Migrating from checkout.liquid to Checkout Extensibility is required for all stores, though Plus stores hit the deadline earlier [2].
- B2B customer-account portals run on a separate buyer journey that standard storefront pixels don't cover. You need explicit pixel placement inside the account portal to capture wholesale conversions.
- Markets Pro multi-region storefronts can generate duplicate purchase events across regional URLs if you run a single pixel without deduplication logic. Stores operating across more than two regions almost always need multi-pixel coordination.
- Hydrogen storefronts run on custom domains. Standard Shopify checkout attribution assumes the same domain context, so cross-domain referral settings must be configured explicitly or sessions break at the cart handoff.
- Admin and POS order events, where orders are created outside the browser session entirely, require server-side or admin-level event capture. This is not covered by browser-based Customer Events.
- If you are on standard Plus (no B2B, no Markets Pro, no Hydrogen), your tracking priorities are the same as any well-run DTC store. The complexity multiplies when you layer in the Plus-specific surfaces.
Does Customer Events Require Shopify Plus?
No. Customer Events is available on every Shopify plan, and the Web Pixels API that powers it is a standard developer feature [3]. This is the dominant misconception driving searches for "shopify plus checkout extensibility customer events attribution tracking."
What Checkout Extensibility does change for Plus stores is the migration deadline. Shopify ended support for checkout.liquid customizations on a plan-by-plan timeline, with Plus stores required to migrate first [1][2]. If you were relying on custom scripts in checkout.liquid for GA4 or Meta purchase events, that path is now closed regardless of plan. The replacement, Customer Events inside Checkout Extensibility, works across all plans.
The confusion is understandable. Checkout Extensibility unlocked a lot of new capability at the same time Plus stores were forced to migrate, so the two got bundled in people's mental models. They are separate things. Checkout Extensibility governs how you customize the checkout UI. Customer Events governs where tracking pixels fire. Both apply to all plans.
Which Tracking Surfaces Actually Require Plus?
Five surfaces are genuinely Plus-only or Plus-relevant in ways that change your tracking architecture.
1. B2B / wholesale customer-account portal tracking. Shopify B2B is a Plus-exclusive feature. Wholesale buyers log into a customer-account portal with separate pricing, catalogs, and order flows. Standard storefront pixels fire on the public-facing store, not inside the authenticated portal. If you're running B2B alongside DTC, a meaningful portion of your revenue is invisible to your attribution stack unless you instrument the portal separately.
2. Markets Pro multi-region pixel deduplication. Markets Pro lets you operate localized storefronts across regions, sometimes with distinct URLs or subdomains per market. A single pixel setup will attribute the same purchase event multiple times if regional domains are not treated as separate pixel contexts. Stores running more than two active Markets Pro regions consistently need multi-pixel coordination rather than a single global tag. For more on how multi-pixel setups work in practice, this breakdown of multi-pixel configuration for multi-account stores covers the deduplication logic in detail.
3. Hydrogen / headless attribution across custom domains. Hydrogen storefronts run on developer-controlled domains. When a buyer moves from your Hydrogen storefront to Shopify's hosted checkout (on checkout.shopify.com or a custom checkout domain), the session context changes. Without explicit cross-domain tracking configuration, GA4 treats the handoff as a new session and the original traffic source is lost. You have to set cross-domain measurement explicitly in GA4 and confirm referral exclusions cover your checkout domain.
4. Customer-account portal pixel coverage. Even outside B2B, the new customer account portal (which Shopify has been rolling out to replace legacy account pages) runs in a separate context. Standard storefront pixels do not automatically carry over into the portal. If you are tracking post-purchase engagement, loyalty activity, or reorder flows that run through the account portal, you need explicit pixel placement there.
5. Admin and POS order events. Orders created through Shopify Admin (manual orders, wholesale orders entered by your team) or through Shopify POS do not generate browser sessions. There is no page load, no Customer Events context, and no client-side pixel to fire. Capturing these conversions requires server-side or webhook-based event forwarding. This is covered in more depth in the admin and POS order event tracking guide, but the short version is: if admin or POS volume is more than 5% of your order mix, you are underreporting conversions to every ad platform.
How Does Markets Pro Affect Tracking?
The core issue is that Markets Pro can surface your store under different regional URLs, and ad platforms treat those URLs as different properties unless you configure them as a single tracking unit.
If you are running a German storefront at /de with a regional checkout and a US storefront at /en, a single Meta pixel with no region-aware deduplication will fire Purchase events based on whichever checkout domain completes. If you have also set up a separate German ad account (common for VAT compliance or budget separation), you now have two pixels seeing some overlap in events, and Meta's deduplication logic will not catch it cleanly without explicit event_id matching.
The decision on whether to use multi-pixel vs. a single pixel comes down to one question: are you running separate ad accounts per region? If yes, multi-pixel with server-side deduplication is the right shape. If you are running one global ad account with market-level audience segmentation, a single pixel with regional event parameters is cleaner and less maintenance.
Verify on your own store: check for Markets Pro tracking fragmentation
- Go to Shopify Admin → Settings → Markets and count how many active markets you have with distinct checkout URLs or subdomains.
- In Meta Events Manager → Overview, look at the "Received Events" column for your pixel. If you see
Purchaseevent counts significantly higher than your Shopify order count for the same window, duplicate firing is likely. - In GA4 → Reports → Engagement → Conversions, filter the
purchaseevent bypage_location. If regional URLs are showing as separatepurchasesources with session counts that don't match Shopify's order source breakdown, cross-domain or multi-region attribution is fragmented. - In GA4 → Admin → Data Streams → your stream → Configure tag settings → List unwanted referrals, confirm your checkout domain and any regional checkout subdomains are excluded from referral traffic.
- Check Shopify Admin → Analytics → Reports → Sales by channel against GA4's purchase count for the same 7-day window. A gap larger than 10-15% on a Markets Pro store almost always points to a cross-region attribution problem, not just standard browser tracking loss.
How Does B2B / Wholesale Affect Conversion Tracking?
Wholesale buyers on Shopify Plus go through a separate authentication flow, and that flow does not share a session context with your public storefront. The practical result is that a Meta pixel installed through Customer Events fires correctly for DTC buyers and does nothing for a wholesale buyer placing a $40,000 order through the account portal.
The gap is not theoretical. A Plus store doing a significant share of revenue through B2B but only tracking the DTC storefront will see ROAS numbers that are structurally wrong. If your Google Ads account is optimizing on a $150 average order value when your true blended AOV including wholesale is $600, Smart Bidding is training on bad data. The bid strategy will optimize toward the wrong buyer profile.
To close the gap, you need pixel events firing inside the authenticated customer-account portal at the order confirmation step. This requires placing your tracking code inside the portal context, not just on the public storefront. Server-side forwarding is more reliable here than client-side because it doesn't depend on the portal's specific page load behavior.
One useful segmentation approach: pass a customer_type parameter on B2B purchase events so your ad platforms and analytics can distinguish wholesale conversions from DTC conversions. This lets you report on each segment separately rather than blending them, which is especially useful if your B2B and DTC CAC targets are different.
Plus + Hydrogen: Where Standard Attribution Breaks
Hydrogen attribution breaks at the domain boundary. A standard Shopify DTC store has one domain, one checkout, and one first-party cookie context. A Hydrogen store has your custom frontend domain and Shopify's hosted checkout on a different domain. GA4 will report the checkout domain as a referral unless you configure cross-domain measurement, and the referral exclusion alone is not enough.
The correct setup has three parts. First, GA4 cross-domain measurement must include both your Hydrogen frontend domain and your checkout domain under Admin → Data Streams → Configure tag settings → Configure your domains. Second, your checkout domain must be on the referral exclusion list so it doesn't overwrite the original traffic source. Third, the GA4 Measurement ID or GTM container must be present on both domains so the session stitching actually works.
If any one of these three is missing, you will see a specific symptom: traffic source for purchased sessions shows as "referral / checkout.shopify.com" or "referral / [your-checkout-domain]" instead of the paid channel that drove the visit. That is the diagnostic flag for a Hydrogen cross-domain attribution break.
Decision Matrix: Your Plus Setup and Your Tracking Priorities
| Your Setup | Top Tracking Priorities |
|---|---|
| Standard Plus, DTC only | Checkout Extensibility migration complete, GA4 + Meta server-side, standard purchase event deduplication |
| Plus + Markets Pro (2+ regions) | Multi-pixel or deduplication logic per region, ad account structure matches pixel structure, referral exclusions cover all regional checkout domains |
| Plus + Hydrogen | Cross-domain measurement configured in GA4, referral exclusion for checkout domain, GTM/pixel present on both frontend and checkout |
| Plus + B2B / Wholesale | Pixel coverage inside customer-account portal, customer_type parameter on purchase events, server-side forwarding for admin-created wholesale orders |
| Plus + B2B + Markets Pro | All of the above plus market-level event parameters to separate regional wholesale from regional DTC in reporting |
If you are on standard Plus with no B2B, no Markets Pro, and a standard Shopify storefront, your tracking priorities are identical to a well-run DTC store on any other plan. The complexity above only applies when you are using the Plus-specific commercial features.
FAQ
Does Shopify Plus include better conversion tracking than standard plans?
Not inherently. The tracking infrastructure, Customer Events, Web Pixels API, server-side Conversions API support, is the same across all plans [3]. What Plus adds is specific commercial surfaces (B2B, Markets Pro, Hydrogen support) that each introduce tracking complexity that doesn't exist on standard plans.
What is the checkout.liquid migration deadline for Plus stores?
Shopify deprecated checkout.liquid customizations for Plus stores on August 13, 2024 [1][2]. After that date, checkout.liquid modifications outside the specific supported areas no longer work. Any tracking that relied on custom scripts in checkout.liquid needed to be migrated to Customer Events inside Checkout Extensibility before that date.
How do I track B2B wholesale orders in GA4 on Shopify Plus?
You need pixel coverage inside the customer-account portal context, not just on the public storefront. Server-side event forwarding triggered by the order creation webhook is the most reliable approach, since it doesn't depend on the portal's client-side page load. Pass a customer_type event parameter to segment B2B purchases from DTC in your GA4 reports.
When does a Shopify Plus store need multi-pixel tracking instead of a single pixel?
Use multi-pixel when you are running separate ad accounts per region or per brand. If you have one Meta ad account and use audience segmentation to separate regions, a single pixel with regional event parameters is cleaner. The trigger for multi-pixel is ad account structure, not storefront count.
Does Shopify POS data flow into GA4 automatically on Plus?
No. POS orders are created server-side without a browser session, so no client-side Customer Events pixel fires. Capturing POS orders in GA4 requires server-side event forwarding via Shopify's order webhook. The same applies to manual orders created in Admin.
WeltPixel Conversion Tracking Covers the Plus-Specific Gaps
The five surfaces covered in this article, B2B portal tracking, multi-region pixel deduplication, Hydrogen cross-domain attribution, customer-account portal coverage, and admin/POS order events, are all surfaces that WeltPixel Conversion Tracking handles without requiring code changes on your end.
Multi-pixel for Markets Pro multi-region stores and multi-ad-account setups, customer-type segmentation for B2B vs. DTC, and server-side forwarding for admin and POS orders are all included. If you are on Plus and any of the scenarios above applies to your store, the app is worth testing before building a custom solution.
Install WeltPixel Conversion Tracking