Book a call
Max Tymoshyn, founder of Norml Studio
Max TymoshynFounder, Norml Studio

Shopify conversion tracking that follows shoppers into checkout

On Shopify, the storefront and the checkout are tracked in different places. The checkout does not load your theme's code, so a Tag Manager container added to the theme stops recording at the cart, and checkout and purchase events have to come through Shopify's customer events. On a headless storefront the shopper also changes systems, and often domains, when checkout starts. We list everything that already sends data, decide where each event should come from, and check that the purchases your analytics and ad platforms report match the orders Shopify saved. On a trading store, those checks use real purchases you approve, each refunded afterwards.

A few clients we’ve worked with

99Legal / Kremenchuker Law GroupAstraZenecaCoxitDiet vs DiseaseFlorida seal — Regional Counsel projectMetroplex HomebuyersNasdaq Private MarketOffice of Criminal Conflict and Civil Regional Counsel, Second Region of Florida — Ita M. NeymotinPolaclubThe Farm Soho

What we do

Norml reviews, repairs and sets up conversion tracking on Shopify stores, including headless storefronts that use Shopify's checkout. The work covers Tag Manager on the storefront, pixels in Shopify's customer events, the Google and Meta apps, consent settings and a written record of every test.

Tracking work on a Shopify store, part by part

Some stores need only a review and a ranked list of fixes. Others need tracking repaired after a recent change broke it, or set up for a new theme or a headless storefront. Each part can be done on its own.

Solution
Integrations
Connected systems
Shopify + Google Analytics 4
Data flow
A shopper views products and adds them to the cart on your Shopify theme or a headless storefront, then starts checkout and pays in Shopify's checkout. Product and cart events come from Tag Manager in the theme, from a pixel in customer events or, on a headless build, from the storefront's code. Checkout and purchase events come from a pixel in Shopify's customer events. Google Analytics 4 and your ad platforms, such as Google Ads or Meta, each receive one copy of every event. A purchase event includes the order ID, the order value and currency, and the products bought. Shopify's orders are the reference: purchases placed to check the setup, and a sample of recent real orders, are matched against what every destination recorded, and any event that is missing, counted twice or separated from the visit's traffic source is listed for your team.
  • An inventory of what sends data todayWe list each place that sends data: the Tag Manager container in the theme, app pixels and custom pixels in Shopify's customer events, apps that add their own tags, snippets pasted into theme files and, on a headless build, the storefront's own code. For each one we note what it does and who looks after it, including any server container the store already sends events to.
    01
  • Tag Manager repaired after a change broke itWhen tracking stopped after an edit, we compare the container's version history with the last version that worked, bring back removed tags that are still needed and settle conflicting edits made in separate workspaces. Page views are checked on the first page of a visit as well as on later ones.
    02
  • Checkout and purchase events from customer eventsCheckout start, the payment step and the purchase are reported by a pixel in customer events: one that an app installs, or a custom pixel we write. We check what each event carries on the storefront and in checkout, and which destinations receive it.
    03
  • Headless storefronts that hand over to Shopify's checkoutWhen product pages and the cart run on your own front end and checkout runs on Shopify, we decide which side sends each event and which identifiers carry the visit and its traffic source into checkout. Tracking changes in the storefront's code are made by us or by your developers, on a preview deployment first.
    04
  • Each order counted once per platformEach order should reach each destination once, identified by its order ID and carrying the value, currency and items. We agree whether the value includes tax, shipping and discounts, and every destination gets the same rule. Where two apps, or an app and Tag Manager, report the same sale, one route stays and the other is switched off.
    05
  • Google Analytics 4, Google Ads and Meta checked against each otherFor add to cart, checkout start and purchase, we check which events each destination receives, whether values match the order and where a conversion appears in one platform but not in another. The Google and Meta apps for Shopify send events of their own, so we record which route each destination relies on.
    06
  • Consent settings in ShopifyPixels in customer events load only after the visitor gives the consent they require, collected through Shopify's privacy settings or a consent app connected to them. We set each custom pixel and each Tag Manager tag to the rules you decide, and record the consent each app pixel requires, since its developer sets that. Then we test the store with consent given and refused.
    07
  • A record of the final setupYou get a map of which source sends each event to each destination, a log of every order we checked and what each destination recorded for it, notes on what we changed, and the checks to repeat before the next theme, app or tag change.
    08
Josiah BallCo-Founder & CEO, HOMEEC

“Norml Studio's professionalism and responsiveness were impressive.”

Clutch review
Lucas SeyhunCEO, The Farm Soho

“They were proactive in suggesting improvements we hadn't considered.”

Clutch review
Gaius CooperDirector, Streamline Pump Solutions

“They delivered what they said they would, on time.”

Clutch review
Emma EstefaClient Success Manager, Metroplex Homebuyers

“They focused on how to make our daily operations easier, not just on building features for the sake of it.”

Clutch review
Bret MillerManager, Door Knock Pro

“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”

Clutch review
Saima AhmedFounder, GoPetZen

“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”

Clutch review

Before work on your store starts

  • Access to Shopify and your Google and Meta toolsA staff or collaborator account on Shopify with access to apps, customer events and themes, and user invitations to Tag Manager, Google Analytics, Google Ads and Meta, so no passwords are shared.
    01
  • Headless storefront codeFor a headless storefront, access to its code repository and a preview deployment, or time with the developer who maintains it.
    02
  • Your go-ahead for refunded checkout testsShopify's test mode for payments blocks real orders while it is on, so it is never switched on while your store is trading. On a live store, each checkout test is a real order: it is placed only with your approval, at a time you agree, and refunded afterwards, and your payment provider may charge its usual fees. A development store, or a store before launch, can use test mode instead.
    03
  • The change that broke tracking, and mismatched ordersThe date of the change after which tracking broke, if there was one, and order numbers or screenshots where Shopify, analytics and an ad platform disagree.
    04
  • Consent choices for your storeThe cookie banner or consent app your store uses, and which pixels and tags are allowed to run before a shopper accepts, decided by you with your legal advisor.
    05
  • Other people who maintain trackingWho looks after any tracking app, server container or agency setup that already sends your store's events, so changes on both sides are agreed.
    06
  • A decision-maker for the event mapSomeone who decides which shopping steps count as conversions, approves the event map and accepts the test results.
    07

Shopify tracking, step by step

  1. [Inventory and test the current setup]

    We list every tag, pixel and app that sends data, read the Tag Manager version history and watch which events reach each destination as we browse the store. Recent Shopify orders are set against the purchases each destination reported for the same days. Where you approve it, one real purchase, refunded afterwards, shows what checkout sends today.

    Step 01
  2. [Choose what each event sends and where]

    You approve the event map: the side that sends each event, the details it includes, where it goes, and the old tags and apps to remove. A review ends at this point, with the problems found and how we would fix them.

    Step 02
  3. [Make the changes]

    We change tags in a copy of the theme that goes live only after checks, change headless storefront code on a preview deployment and prepare Tag Manager edits in their own workspace. A pixel in customer events runs on the live store from the moment it is connected, so we connect it at an agreed time and test it straight away. Old tags are removed after their replacements pass.

    Step 03
  4. [Test each step of a purchase]

    We view products, add to cart, start checkout and pay, in mobile and desktop browsers, once with consent accepted and once with it declined, and across the domain change on a headless storefront. On a trading store the payment is real: you approve each purchase and it is refunded afterwards. Each event is checked in Shopify's Pixel Helper or the platforms' debugging tools, and against the order in Shopify.

    Step 04
  5. [Publish, then compare with real orders]

    We publish the tested container version and keep earlier versions for rollback. After real orders have come in for a period we agree, each destination's purchases are compared with Shopify's orders, any remaining gap is looked into and you receive the setup record.

    Step 05

The people who do this work.

Meet the whole team

No account layer between you and them. These are the Norml specialists this work runs through.

Max Tymoshyn, founder of Norml Studio

Let's chat

“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”

Max TymoshynFounder & Architect

From the Norml blog.

Questions about Shopify conversion tracking

Can you review our tracking without changing anything?
Yes. A review changes no tags, pixels or settings. It lists every source that sends data and compares recent Shopify orders with the purchases each destination recorded. With your approval, a real purchase that is then refunded shows where checkout events go missing. You get a ranked list of problems, each with the reason it happens and the change we suggest. Your developers can work from it, or we can make the fixes.
Why does our Tag Manager container miss checkout and purchase events?
A container added to the theme only runs on theme pages, and Shopify's checkout is not one of them. In the browser, checkout events come from customer events, through an app's pixel or a custom pixel. Tag Manager can run inside a custom pixel, but Google's Tag Assistant does not detect tags there, so those events are checked with Shopify's Pixel Helper and an approved purchase that is refunded afterwards.
Do you set up server-side tagging?
No. We do not build, host or repair server-side Tag Manager containers, and we do not connect servers directly to Google Ads, Meta or other ad platforms. If your store already sends events to a server container, we list the browser events that feed it and agree any change to them with whoever maintains it. Matching its server events with browser events, so a sale is not counted twice, stays with them.
Our storefront is headless. Can you track purchases in Shopify's checkout?
Yes, within what Shopify's checkout allows. When checkout runs on another domain and the visit is not carried across, analytics can start a new visit at checkout and credit the sale to your own storefront rather than the ad or search result that brought the shopper. A real purchase started from a link with campaign tags, approved by you and refunded afterwards, shows whether the order keeps its original source; anything the checkout cannot pass on is listed as a reporting limit.
Can we keep the app we already use for Meta tracking?
Yes, if it records each order once. We test it alongside the Google setup, make sure no second route sends the same purchase to Meta, and note what it covers so a later change cannot break it unnoticed.
Why does analytics show fewer orders than Shopify?
Shopify records every order, while analytics only sees purchases made in a browser that loaded the tracking. Point-of-sale orders, subscription renewals and some other sales channels never pass through it, and shoppers who decline consent or use ad blockers are missing as well. We compare the two over an agreed period and show which of these causes affect your store.
Who owns the tags, pixels and accounts afterwards?
You do. The container, the analytics property and the ad accounts belong to your company, and custom pixels sit in your own Shopify admin. Removing our access does not stop the tracking.
Will fixing the tracking improve our ad performance?
Ad platforms report on the purchases they receive and use them for automated bidding, so missing or doubled purchases mislead both. Bids, budgets, audiences and ads remain the job of whoever manages your campaigns, and we do not promise any change in ad results.
Will you also run our ads or change checkout settings?
Neither is part of this work. Running Google Ads campaigns is a separate service we scope on its own, and so are reports built on the tracked data and storefront builds or redesigns. Shopify's checkout and payment settings stay with whoever looks after the store; a checkout or payment fault found during testing goes into the record with its evidence for them.

Read the co-working, nutrition and pump store projects

They describe tracking built from nothing on one WordPress site, an inherited Tag Manager setup cleaned up on another, and a WooCommerce store launched together with its Google Ads.

See all case studies