Shopify Purchase Tracking Not Working After Checkout Upgrade? 9 Issues UK Stores Should Check

shopify-purchase-tracking-not-working

Shopify Purchase Tracking Not Working After Checkout Upgrade?

Your Shopify store is receiving orders, customers are completing checkout, and payments are being processed. Yet Google Analytics 4 shows fewer purchases than expected, or Google Ads and Meta Ads have stopped reporting conversions.

Shopify purchase tracking not working after a checkout upgrade can be caused by legacy scripts that were not migrated, disconnected pixels, incorrectly mapped checkout events, sandbox restrictions, consent settings, duplicate integrations or reporting differences.

The first step is identifying where the purchase measurement process is failing. A completed Shopify order does not automatically guarantee that GA4 or an advertising platform has recorded it.

Why Did Shopify Purchase Tracking Change After Checkout Upgrades?

Shopify's Checkout Extensibility introduced a more secure, app-based approach to checkout customisation and analytics.

Previously, some merchants relied on JavaScript added through the Additional scripts field, legacy Thank You pages, Order Status pages or checkout.liquid customisations.

Those implementations could send purchase information directly to analytics platforms. However, they were dependent on checkout features that Shopify subsequently deprecated or replaced.

The relevant migration deadlines were:

  • 28 August 2025: Deadline for Shopify Plus merchants to upgrade legacy Thank You and Order Status page customisations.
  • January 2026: Shopify began automatic upgrades of affected legacy configurations.
  • 26 August 2026: Final upgrade deadline for merchants on non-Plus Shopify subscription plans.

These deadlines have passed. Merchants using older checkout tracking implementations should now verify that their integrations operate with the upgraded checkout.

Shopify's official checkout upgrade documentation explains the supported replacement approach.

App Pixels vs Custom Pixels: What's the Difference?

Shopify now uses Customer Events and its Web Pixels API to make customer actions available to compatible tracking integrations.

App pixels are managed by installed applications or sales channels. They can provide established connections to services such as Google Analytics and Meta.

Custom pixels are manually configured JavaScript integrations added through Shopify's Customer Events interface. They offer flexibility but require additional technical responsibility.

Shopify generally recommends choosing a compatible app pixel when one is available.

Custom pixels are appropriate when an existing app cannot meet a specific, legitimate measurement requirement.

A checkout upgrade does not automatically break analytics. Problems arise when the existing tracking implementation is no longer compatible, has been configured incorrectly or cannot transmit the expected purchase data.

How to Identify Where Shopify Purchase Tracking Is Failing

Before changing any tracking code, understand the complete measurement journey.

Shopify order completed → Customer event generated → Pixel receives event → Event transmitted → Destination processes event → Purchase appears in reporting or advertising attribution.

Each stage represents a different outcome.

A Shopify order is the transaction recorded in the merchant's order management system.

A Shopify customer event represents an action observed through Shopify's event framework.

A transmitted pixel event means data was sent towards an external platform.

A recorded GA4 purchase means Google Analytics processed the event for measurement.

An advertising conversion is a purchase credited according to an advertising platform's eligibility and attribution rules.

These results are not automatically identical.

Shopify Purchase Tracking Diagnostic Table

SymptomFirst investigation
Shopify orders exist but GA4 shows no purchasesGA4 connection and purchase event delivery
Pixel exists but appears disconnectedShopify Customer Events configuration
checkout_completed is missingEvent subscription and checkout completion flow
Pixel receives events but GA4 does notDestination configuration and event payload
GA4 reports too many purchasesDuplicate implementations
Purchase revenue appears incorrectValue, tax, shipping and currency mapping
Only some purchases are trackedConsent, browser restrictions and checkout conditions
Meta purchases are missingMeta integration, event delivery and attribution
Shopify and GA4 figures differReporting definitions, periods and processing delays

These are diagnostic starting points, not guaranteed explanations.

Start by confirming completed Shopify orders, identifying affected reporting platforms and establishing when the discrepancy began.

Then review connected apps, custom pixels, consent configurations and recent checkout changes.

Avoid modifying several integrations simultaneously. Otherwise, it becomes difficult to identify which change fixed or created the problem.

9 Reasons Shopify Purchase Tracking Is Not Working

1. Legacy Checkout Tracking Scripts Were Not Migrated

One possible cause of missing purchases is tracking code that previously relied on Shopify's legacy checkout customisations.

For example, a retailer may have placed a GA4 purchase script inside the old Additional scripts field.

Following the checkout upgrade, the previous page implementation is replaced. Unsupported scripts may no longer execute.

Common symptoms: Product views and cart activity continue appearing in analytics, but purchase events suddenly disappear after a checkout change.

How to investigate:

Review your historical implementation, including old developer documentation, installed applications and any records of checkout scripts.

Compare those records with the store's current Customer Events configuration.

Determine whether the original purchase measurement has been replaced by a supported integration.

Safe corrective action: For Google measurement, assess the Google & YouTube app. For other platforms, investigate their compatible Shopify app pixels before considering custom development.

Do not attempt to restore deprecated Additional scripts or unsupported checkout.liquid tracking as a permanent solution.

If multiple legacy integrations existed, a Shopify developer may be needed to document the previous setup and migrate each required event without introducing duplicates.

2. Shopify Customer Events Pixel Is Disconnected or Misconfigured

Installing or creating a pixel does not guarantee that it is actively tracking customers.

Shopify separates pixel installation, connection, event subscription and actual data transmission.

To investigate, open Shopify Admin → Settings → Customer events.

Review the available app pixels and custom pixels.

For a custom pixel, check whether it is connected. Shopify's management interface distinguishes connected and disconnected custom pixels.

Also check that the code has been saved, the correct event subscription exists and there are no relevant JavaScript errors.

For app pixels, review the application's configuration and permissions.

Common symptoms: The integration appears in Shopify but does not record purchases, or a custom pixel remains disconnected after being created.

Safe corrective action: Correct the relevant configuration and use Shopify's supported testing tools before making further changes.

Shopify Pixel Helper can show whether supported pixels receive customer events. However, receiving an event in Shopify does not prove that GA4 or Meta successfully processed it.

Do not install multiple replacement pixels merely because one appears inactive.

Where an integration has been configured correctly but still cannot transmit events, contact the app provider or an experienced integration developer.

3. The Shopify checkout_completed Event Is Not Captured

Shopify's checkout_completed event is the standard customer event associated with a completed purchase.

According to Shopify's developer documentation, it normally fires once per checkout, typically on the Thank You page.

However, there is an important exception.

When a checkout includes a post-purchase upsell, the event may fire on the first upsell offer page instead.

It does not fire again on the Thank You page.

If the page where the event is supposed to occur fails to load, Shopify documents that the event might not trigger.

Common symptoms: Shopify records valid orders, but browser-based purchase tracking misses certain transactions, particularly during specific checkout journeys.

How to investigate: Complete controlled test orders using the relevant payment and checkout paths. Inspect whether the pixel receives checkout_completed.

Include post-purchase offers if the store uses them.

Safe corrective action: Ensure the integration subscribes to the appropriate Shopify event and handles its payload correctly.

Do not replace purchase tracking with a generic page-view trigger. Visiting or revisiting a page does not necessarily represent a new completed purchase.

A developer should investigate if the event behaves differently across supported checkout flows or if a custom implementation assumes that purchases always occur on the same page.

4. Google Tag Manager Is Affected by Shopify's Pixel Sandbox

Shopify's Customer Events framework runs pixels within an isolated environment known as a sandbox.

This helps protect the storefront and customer information but changes what tracking scripts can access.

Older Google Tag Manager implementations may rely on the page's Document Object Model, form elements, click detection or data-layer values available in the main browser window.

Those assumptions might not hold inside Shopify's pixel sandbox.

Common symptoms: Storefront activity is recorded, but GTM checkout tags do not work as expected. Some event parameters are missing, or standard Tag Assistant debugging cannot observe the custom-pixel implementation.

Shopify documents that GTM can technically run through a custom pixel. However, tags loaded within that pixel remain subject to sandbox restrictions.

There is also a crucial distinction between technical capability and official product support.

Google states that running Google tags inside Shopify custom pixels is not a supported Google tagging implementation.

How to investigate: Identify whether the purchase measurement uses GTM, a custom pixel or the native Google & YouTube integration.

Review any tags that depend on direct page access or old checkout variables.

Safe corrective action: For GA4 and Google Ads purchase measurement, prioritise Google's supported Google & YouTube app unless there is a verified reason to use another architecture.

Do not assume that copying a conventional GTM container into Customer Events will reproduce its previous behaviour.

Complex tag management requirements may need a specialist to assess compatibility, consent handling and alternative supported integrations.

5. GA4 or an Advertising Platform Is Configured Incorrectly

A Shopify pixel can receive the correct customer event while sending data to the wrong analytics property, web stream or advertising account.

For example, an agency may have created a replacement GA4 property, but the Shopify store still sends purchases to an older measurement ID.

Another common misunderstanding involves event names.

Shopify generates checkout_completed, while GA4 expects a properly structured purchase event.

The integration must perform the appropriate mapping.

Common symptoms: Shopify Pixel Helper detects checkout activity, but no corresponding purchase appears in the expected GA4 property.

How to investigate:

Check the Google & YouTube sales channel, connected Google account, selected GA4 property and relevant web data stream.

Compare these with the reporting property your team actually uses.

For Google Ads, confirm that the appropriate purchase conversion action exists and is connected to the intended measurement source.

For Meta, review the Facebook & Instagram integration and corresponding Events Manager diagnostics.

Safe corrective action: Correct the existing integration rather than adding another tracking installation immediately.

If GA4 records purchases but Google Ads does not, investigate attribution, account linking and conversion actions separately.

For broader Google Ads diagnosis, XCONS has a related guide: Google Ads Conversion Tracking Not Working? 9 Issues UK Businesses Should Check.

Avoid creating duplicate conversion actions without checking which actions advertising campaigns already use for optimisation.

A customer can successfully purchase products while declining optional analytics or marketing tracking.

In the UK, that distinction matters.

Shopify pixels operate according to their configured privacy permissions and the visitor's consent choices.

A customer who declines the permissions required by a particular pixel may complete checkout without that pixel collecting the purchase.

This does not indicate a payment failure.

Common symptoms: Purchase measurement works for some visitors but not others, even though Shopify records orders normally.

Another possibility is an incorrectly connected third-party cookie banner.

A visitor may grant valid consent, but that decision is not properly communicated to Shopify's Customer Privacy API.

How to investigate:

Review Shopify Admin → Settings → Customer privacy and the consent requirements shown in Customer Events.

Check whether your cookie banner synchronises consent correctly.

Perform controlled checkout tests with consent granted and consent denied, using the relevant permissions for each test.

Compare the observed pixel behaviour with the expected result.

Safe corrective action: Repair consent synchronisation or incorrect permission configuration while respecting visitors' choices.

Do not bypass consent, automatically grant marketing permissions or remove a lawful consent mechanism simply to increase tracking totals.

Where a third-party consent platform is involved, assistance from both the integration provider and a privacy professional may be appropriate.

7. Multiple Pixels Are Recording the Same Purchase

Missing tracking is not the only problem. Some Shopify stores accidentally report more purchases than actually occurred.

This can happen when multiple integrations transmit the same purchase to the same destination.

Examples include:

  • Google & YouTube alongside a separate GA4 custom implementation.
  • Two tracking apps recording the same transaction.
  • Theme-level tracking combined with Customer Events.
  • Duplicate purchase logic inside custom pixels.
  • Browser and server tracking without appropriate deduplication.

Common symptoms: GA4 reports unusually high purchase counts, repeated events appear for the same transaction, or advertising platforms show unexpectedly inflated conversions.

How to investigate: Place one approved test order and trace each event sent to the relevant destination.

Inspect transaction identifiers, event payloads and configured integrations.

For GA4, a consistent transaction_id helps Google identify repeated events representing the same transaction.

For Meta browser and Conversions API integrations, corresponding event identifiers and event names are relevant to deduplication.

Safe corrective action: Identify overlapping senders and decide which supported implementation should own purchase measurement for each destination.

Do not immediately delete existing pixels. They may support other business processes or advertising dependencies.

Having GA4 and Meta tracking the same genuine order is normal. The problem arises when one destination records the same purchase more times than intended.

Transaction identifiers help prevent duplication, but they do not replace a properly designed measurement setup.

8. Purchase Event Parameters Are Missing or Incorrect

A GA4 purchase event may be transmitted without the information needed for meaningful ecommerce reporting.

Google's ecommerce documentation identifies important purchase parameters, including:

ParameterPurpose
transaction_idUnique identifier for the purchase
valueMonetary value of purchased items
currencyTransaction currency, such as GBP
itemsProducts included in the purchase
item_id or item_nameItem identification
priceItem unit price
quantityQuantity purchased
shippingShipping amount
taxTax amount

Under Google's recommended purchase-event specification, value should represent the sum of item prices multiplied by quantities, excluding shipping and tax, with those amounts provided separately where applicable.

If value is supplied, the appropriate currency parameter is necessary.

For a UK order denominated in pounds sterling, the currency would normally be GBP.

However, a Shopify store selling in multiple currencies should not automatically label every purchase GBP.

Common symptoms: Purchase events appear, but revenue is zero, product-level reports are incomplete or reported totals differ unexpectedly.

How to investigate: Inspect one controlled purchase payload using suitable diagnostic tools.

Compare the transaction identifier, item quantities, discounts, currency, tax and shipping values with the corresponding Shopify order.

Check whether the integration maps Shopify's event data to the fields expected by GA4.

Safe corrective action: Correct the mapping and validate another test transaction using Google's recommended ecommerce event specification.

Do not send customer names, payment details or unnecessary personal information through debugging tools.

Where product identifiers, multi-currency pricing or custom checkout logic are involved, developer-level assistance may be necessary.

9. Shopify Orders and Analytics Reports Are Being Compared Incorrectly

Not every difference between Shopify and GA4 indicates a broken tracking installation.

Shopify stores completed orders in its own systems, while GA4 and advertising platforms collect and report information using different measurement methods.

Differences can result from browser restrictions, ad blockers, consent choices, reporting time zones, processing delays, refunds, cancellations or attribution settings.

For example, a Shopify customer may discover a product through organic search and make a purchase without ever clicking a paid advertisement.

Shopify can record the order, and GA4 may record the purchase, but Google Ads will not necessarily attribute that purchase to advertising.

Similarly, a purchase attributed to one advertising platform may not be counted identically by another.

Common symptoms: Shopify records more orders than Google Ads, revenue differs between dashboards, or the same transaction appears under different reporting dates.

How to investigate: Compare the same date range, time zone, sales channel and metric definitions.

Separate total purchases from purchases attributed to paid advertising.

Consider reporting delays and check whether refunds or tax calculations affect the comparison.

Safe corrective action: Reconcile comparable data rather than attempting to force every platform to display identical totals.

A specialist may be required when differences remain unexplained after technical tracking, consent and reporting definitions have been checked.

There is no reliable basis for promising perfect agreement between Shopify, GA4, Google Ads and Meta Ads.

How to Test Shopify Purchase Tracking After a Checkout Upgrade

A controlled test is more useful than repeatedly changing tracking scripts.

Follow this diagnostic sequence.

Step 1: Confirm a completed order.

Open Shopify Admin and verify that a legitimate order was created. Record a non-sensitive reference for comparison.

Step 2: Identify the tracking destinations.

List the relevant systems, such as GA4, Google Ads, Meta Ads and any third-party analytics integrations.

Step 3: Review existing pixels.

Open Customer Events and identify connected app pixels and custom pixels. Check for obvious duplication.

Step 4: Verify consent requirements.

Determine what permissions each pixel needs. Ensure testing reflects appropriate consent choices.

Step 5: Complete a controlled checkout.

Use a Shopify-supported test payment method or an approved test environment where possible. Avoid unnecessary live charges.

Step 6: Inspect Shopify's customer event.

Use Shopify Pixel Helper where supported to confirm whether the pixel received checkout_completed.

Step 7: Check destination delivery.

For GA4, examine DebugView or Realtime reporting, using an appropriate debugging setup.

For Meta, use the relevant Events Manager testing and diagnostic features.

Step 8: Validate the event payload.

Check transaction ID, purchase value, currency and item information.

Step 9: Look for duplicates.

Confirm that one test purchase is not unnecessarily transmitted or recorded multiple times within the same destination.

Step 10: Review normal reporting.

Allow for legitimate processing delays before checking standard ecommerce or advertising reports.

Step 11: Document and retest.

Record the test date, consent state, expected result, actual event, destination result, errors and changes made.

A successful Shopify Pixel Helper result does not guarantee that GA4 recorded the purchase.

Likewise, seeing a purchase in GA4 DebugView does not prove that Google Ads will attribute it to a paid campaign.

Can Missing Shopify Purchase Data Be Recovered?

Sometimes, but recovery depends on what information was originally collected and what records remain available.

Potential sources include Shopify order records, existing CRM systems, historical event logs, analytics exports and supported server-side integrations.

However, Shopify's order database and GA4's event collection are different systems.

A Shopify order may provide evidence that a transaction occurred without preserving all the information required to reconstruct its original analytics session or advertising attribution.

Installing a new pixel does not automatically restore historical missing purchases.

Some advertising and analytics platforms support specific data-import mechanisms, subject to technical, privacy, eligibility and timing requirements.

These mechanisms should be evaluated individually.

Do not fabricate historical purchase events or assign unsupported attribution information.

If reliable historical measurement cannot be reconstructed, the appropriate next step is to correct future event collection and clearly document the historical reporting limitation.

How Can Incorrect Shopify Purchase Tracking Affect Advertising Decisions?

Inaccurate measurement can affect how businesses evaluate ecommerce marketing.

Underreported purchases may make successful campaigns appear weaker than they actually are.

Duplicated conversions may make campaigns appear more profitable than the underlying orders justify.

Incorrect event values can also distort reported revenue and return on ad spend.

Hypothetical example: A retailer completes 80 Shopify orders during a reporting period, but GA4 records only 55 purchases.

The difference does not establish that 25 orders were lost. It establishes that the merchant needs to investigate why the recorded figures differ.

If the business makes advertising decisions without recognising the discrepancy, it may misinterpret campaign performance.

Accurate conversion measurement supports better decisions, although correcting tracking does not itself guarantee higher sales or improved advertising performance.

Merchants seeking support with campaign measurement can also review XCONS Solutions' Google Ads Management services.

Advertising-related purchase tracking generally requires appropriate consent under the UK's Privacy and Electronic Communications Regulations (PECR).

Where personal data is processed, UK GDPR requirements also apply.

The Information Commissioner's Office explains that storage and access technologies used for online advertising require consent, including associated advertising measurement.

That does not necessarily mean a separate additional consent is required solely for measuring advertisements when valid advertising consent already covers that intrinsically linked purpose.

Certain narrowly defined statistical analytics activities may qualify for different exceptions under the updated legal framework. Those exceptions must not be treated as permission to perform advertising tracking without consent.

Shopify's Customer Privacy API provides mechanisms for communicating applicable permissions to Shopify-managed surfaces and pixels.

Merchants should ensure that their consent management platform, Shopify settings and relevant tracking integrations behave consistently.

A server-side integration is not automatically exempt from privacy or data-protection requirements.

Similarly, customer identifiers should not be transmitted to advertising platforms without an appropriate legal basis, transparency and compliance with the relevant platform rules.

For current guidance, refer to the ICO's rules on storage and access technologies for online advertising.

Businesses with complex tracking architectures should obtain appropriate privacy advice.

When Should You Hire a Shopify Tracking or Integration Specialist?

Not every analytics discrepancy requires professional development support.

Basic issues such as selecting the wrong GA4 property, leaving a custom pixel disconnected or comparing different reporting dates may be resolved through existing settings.

More complex situations can require specialist investigation, particularly when:

  • Legacy checkout scripts were not migrated correctly.
  • Custom pixel subscriptions or event mapping require JavaScript changes.
  • GTM behaves differently inside Shopify's sandbox.
  • Purchase revenue or transaction identifiers are malformed.
  • Multiple platforms are recording duplicate events.
  • Consent management is not synchronised.
  • Custom apps or third-party integrations require debugging.

Depending on the cause, the appropriate professional may be a Shopify developer, ecommerce analytics specialist, tracking app provider or privacy adviser.

The objective should be to identify the actual failure before proposing development changes.

Are Shopify Orders Missing From Your Analytics Reports?

If your Shopify store is processing orders but GA4 or advertising platforms are not reporting purchases correctly, the cause may involve Customer Events, pixel configuration, checkout compatibility, consent settings or ecommerce integrations.

Identifying the affected stage of the tracking process is the first step towards more reliable measurement.

XCONS Solutions Ltd, a digital agency based in Ilford, East London, supports UK businesses with Shopify development and relevant ecommerce integrations.

Explore our Shopify Development services or contact XCONS Solutions to discuss your store's technical requirements.

Share This :