Pingverablog ← Blog
Home › Blog › GA4 Purchase Event Not Firing: Check Conversion Tracking Before Black Friday

GA4 Purchase Event Not Firing: Check Conversion Tracking Before Black Friday

November 16, 2026 · 13 min read

GA4 Purchase Event Not Firing: Check Conversion Tracking Before Black Friday

If GA4 shows fewer purchases than your store admin, or none at all, the tag that sends the purchase event is usually missing from the order confirmation page, blocked before it runs, or sending a transaction ID that makes GA4 merge separate orders. The fastest way to find out which is to place one real test order, watch it arrive in GA4 DebugView, and then compare a full day of orders in your store admin with purchases in GA4.

Do it this week. Black Friday falls on 27 November 2026 and Cyber Monday on 30 November. Ad platforms bid on the conversions you send them, so a purchase event that stopped firing in August means your campaigns have been optimising on incomplete data for three months. Shopify stores have a specific reason to look: as of 26 August 2026, Shopify upgraded every remaining Thank you and Order status page automatically, and legacy additional scripts do not run on the new pages.

At a glance

  • Start by comparing one day of orders in your store admin with purchases in GA4. That tells you whether a gap exists and how large it is.
  • Shopify stores that relied on additional scripts for tracking have lost that tracking since the upgrade. Replacement is an app pixel or a custom pixel under Settings > Customer events.
  • GA4 merges purchases that share a transaction ID, and it merges every purchase sent with an empty transaction ID. A static or blank ID can make a hundred orders look like one.
  • Consent settings change what you can see. Pixels and DebugView only show events for visitors who granted the required consent, so a test order placed without accepting the banner proves nothing.
  • Off-site payment methods and post-purchase upsell pages move the point where the purchase event fires. Test each payment method you will use on Black Friday.

Why it matters now

Shopify's help centre states that 26 August 2026 was the deadline to upgrade the Thank you and Order status pages, and that stores which had not upgraded by then were upgraded automatically. Its page on additional scripts is direct: "Additional scripts for tracking and analytics and page customizations aren't supported on the new Thank you and Order status pages." The same page says tracking scripts need to be replaced with pixels. Once the upgrade completes, an additional script cannot be reactivated. The additional scripts box in checkout settings has been view-only since 28 August 2025.

The storefront looks the same after this happens. Orders still come in, and the only symptom is a reporting gap that someone has to notice.

WooCommerce and custom stores have no single deadline, but the same failure appears for ordinary reasons: a theme update that replaces the order-received template, a caching or optimisation plugin that delays or strips the tag, a consent banner that now blocks analytics by default, or a payment provider that stops redirecting customers back to the store. Pre-peak plugin updates, the kind covered in How to Update WooCommerce Safely, are a common trigger.

On the GA4 side, Google's guidance on transaction IDs (opened November 2026) says that GA4 "will deduplicate purchases if 2 purchases are registered with the same transaction ID", that the ID "must be unique for each order", and that you should not send an empty string because GA4 "will deduplicate all purchase events that have transaction_id=""". A broken variable that outputs a fixed value or nothing at all still fires the event, and GA4 then collapses your orders into one.

Step by step: find where the purchase event breaks

1. Measure the gap

Pick a recent full day with normal traffic. Count orders in your store admin, excluding test orders and orders cancelled for fraud. In GA4, open the ecommerce purchases report for the same day and read the transaction count. Use the property's reporting time zone, which can differ from the store's.

Some gap is normal because of consent choices and ad blockers. What you are looking for is a step change: a ratio that was stable for months and then dropped on a specific date. Write that date down. It usually lines up with a deploy, a plugin update or a platform change.

2. Turn on DebugView

Open GA4, go to Admin, then DebugView under Data display. Google's documentation says debug mode must be enabled first. The simplest way is to open your store through Tag Assistant (tagassistant.google.com) or Google Tag Manager preview mode. Accept analytics and marketing cookies in your own banner, because Google notes that events are not visible in debug mode when consent has not been given for analytics cookies.

3. Place a real test order

On Shopify, place a test order with the test payment gateway or Shopify Payments test mode, as described in Shopify's "Placing a test order" guide. On WooCommerce or a custom store, use your gateway's sandbox on a staging copy, or place a low-value live order and refund it. Then go through the checkout with each payment method you expect customers to use on Black Friday: card, wallet, and any method that sends the customer to another site to pay.

4. Check what arrives

In DebugView, find the purchase event and open its parameters. Check for:

  • transaction_id equal to the real order number shown in your admin
  • value and currency present, with currency set at the event level (Google's ecommerce documentation recommends setting currency whenever you send value)
  • an items array with the products you bought

If the event never appears, the tag did not run. If it appears with an empty or repeated transaction_id, the tag runs but the data layer is wrong.

5. Shopify: confirm the pixel is connected

Go to Settings > Customer events. Every app pixel and custom pixel should show "Connected" in the Status column. Shopify's testing guide says to click a pixel, then Test, which opens the Shopify Pixel Helper, and then complete a test checkout to check checkout_completed. Its stated limits: you can test one custom pixel at a time, logs clear when you navigate, and the helper does not work on headless stores or stores in private mode.

Two details from Shopify's developer documentation matter here. checkout_completed fires once per checkout, usually on the Thank you page, but when a post-purchase upsell is installed it fires on the first upsell page and does not fire again on the Thank you page. And if the page where it should fire fails to load, the event does not fire at all.

Custom pixels run in a sandbox. Shopify says the page URL a custom pixel reports includes a sandbox version, and that you should read the real URL from the page_viewed event. A custom pixel that filters on /thank_you in the URL will stop matching.

6. WooCommerce and custom stores: check the confirmation page

Open the order-received page source after the test order and confirm the tag is there. Then check three common blockers:

  • a caching or script optimisation plugin that delays, combines or excludes the analytics script on the order-received page
  • a theme override of the thank-you template that dropped the hook your tracking plugin relies on
  • payment methods where the customer does not return to the store, so the confirmation page never loads in their browser

For the third case, server-side tracking or the GA4 Measurement Protocol sent from an order webhook is more reliable than a browser tag. Either way, compare the result with real order counts.

7. Look for duplicates

If GA4 reports more purchases than you have orders, check whether two systems send the same event: an old hard-coded gtag plus a plugin, or an app pixel plus a custom pixel. Shopify warns that connecting an app pixel before deactivating an additional script creates "a short period of duplicate events". A unique transaction_id lets GA4 merge those, but ad platforms may count both.

Who checks what

Risk Owner Check Frequency
Purchase tag missing after a theme or plugin update Developer or agency Test order with DebugView open After every deploy that touches checkout
Shopify tracking lost after the Thank you page upgrade Store owner with app vendor Settings > Customer events, all pixels "Connected" Once now, then monthly
Static or empty transaction ID merging orders Developer transaction_id matches the admin order number Every test order
Duplicate purchase events Marketing lead GA4 purchases vs admin orders, ratio above 1 Weekly, daily during peak
Off-site payment method skips the confirmation page Developer Test order with each payment method Before peak and after gateway changes
Orders and analytics drifting apart unnoticed Ecommerce manager Daily order count vs GA4 purchase count Daily from 20 November to 7 December

Copyable test plan

Paste this into your ticket system or client handover note and fill it in.

PURCHASE TRACKING TEST - <store name> - <date>
Tester:
GA4 property / stream:
Consent accepted in banner: yes / no

Baseline (yesterday, store time zone)
  Orders in admin (excl. test/fraud):  ____
  Purchases in GA4:                    ____
  Ratio GA4 / admin:                   ____

Test orders (one row per payment method)
  Method | Order no. | Purchase in DebugView? | transaction_id = order no.? | value + currency? | items? | Ads conversion seen?
  Card   |           |                        |                             |                   |        |
  Wallet |           |                        |                             |                   |        |
  Off-site redirect |  |                       |                             |                   |        |

Shopify only
  Settings > Customer events: all pixels Connected?   yes / no
  Pixel Helper shows checkout_completed?              yes / no
  Post-purchase upsell installed? (event fires on upsell page) yes / no
  Any custom pixel filtering on URL path?             yes / no

Duplicates
  More than one source sending purchase?              yes / no  (list)

Result: PASS / FAIL
Follow-up owner and date:
Re-test after fix: date ____ result ____

Worked scenario (illustrative)

A small Shopify store selling homeware normally sees GA4 record about 80% of the orders in its admin. The figures here are invented for illustration. In late October, while building a Black Friday campaign report, the ecommerce manager notices the ratio fell to roughly 15% in the last week of August and stayed there.

They place a test order through Shopify Payments test mode with the cookie banner accepted. DebugView shows page_view and begin_checkout, but no purchase. In Settings > Customer events, the GA4 app pixel is listed as connected, but the purchase tag the previous agency had set up lived in additional scripts, and the app pixel had been installed later only for page views. A second finding: the store's post-purchase upsell app means checkout_completed fires on the upsell page, and the agency's notes had assumed the Thank you page.

The developer enables purchase tracking in the app pixel, removes a stale custom pixel that filtered on the old /thank_you path, and re-runs the test plan for each payment method. The ratio returns to its previous level the next day, and the manager keeps a daily comparison running until 7 December.

Common mistakes

  • Testing with the consent banner rejected and concluding that tracking is broken.
  • Comparing GA4 with the store admin across different time zones or different definitions of an order.
  • Fixing the tag on a staging site and never re-testing on production after the deploy.
  • Hard-coding transaction_id during a test and leaving it in place.
  • Treating GA4 as the source of truth for revenue. It is a sample shaped by consent and blockers. Your order database and payment provider are the records you reconcile against.

Limitations: this procedure checks that the event fires and carries the right data. It does not fix attribution, and it cannot recover data for orders that were never tracked. Ad platforms have their own conversion tags and deduplication rules, which you need to test separately in each platform's own diagnostics. For the wider question of how much to trust any attribution model, see Marketing Attribution Without Self-Deception.

FAQ

Why does GA4 show fewer purchases than Shopify?

Some gap is expected because visitors decline consent or block scripts. A sudden drop usually means the tag stopped running, often after the Thank you page upgrade removed additional scripts, or that a wrong transaction_id is merging orders.

Can I still edit additional scripts on Shopify?

No. Shopify made the additional scripts section view-only on 28 August 2025, and scripts cannot be reactivated once the Thank you and Order status pages have been upgraded. Use an app pixel or a custom pixel under Settings > Customer events.

How often should I check purchase tracking during peak?

Run a full test order after every change to checkout, theme or payment settings. Between 20 November and 7 December, compare the daily admin order count with GA4 purchases every morning so a break costs you at most one day of data.

Sources

  • Shopify Help Center: Upgrading the Thank you and Order status pages
  • Shopify Help Center: Upgrade guide
  • Shopify Help Center: Additional scripts
  • Shopify Help Center: Pixels overview
  • Shopify Help Center: Custom pixels
  • Shopify Help Center: Testing custom pixels
  • Shopify Help Center: Placing a test order
  • Shopify Developers: checkout_completed standard event
  • Google Analytics Developers: Measure ecommerce
  • Google Analytics Help: Minimize duplicate key events with transaction IDs
  • Google Analytics Help: Monitor events in DebugView

Last reviewed: 2026-11-16

For a broader review of analytics data before peak, see the Ecommerce Analytics Data Quality Audit. The daily check in this article needs a count of real orders that does not depend on a browser tag. On WooCommerce stores, Pingvera's WordPress connector records each order as it is created and alerts when order flow drops below its hourly baseline while the site stays up, so you can tell a tracking gap (orders normal, GA4 down) from a sales problem (both down). The method is described in Uptime Green, Orders Zero.

Know about problems before your customers do

Pingvera watches whether an online business actually works — uptime, checkout, orders, domain, SSL and server — and alerts you in Telegram, email or a webhook before a customer has to tell you.

Start free

Read next: Ecommerce Analytics Data Quality Audit: One-Day Checklist · Shopify Script Tags Deprecation: Audit Your Store Before March 2027.

Read next: WooCommerce 11.3: What to Test Before Black Friday · Merchant Center Availability Mismatch: Black Friday Fix · WooCommerce Coupon Not Working? Fix It Before Black Friday · How to Update WooCommerce Safely Before Black Friday · Run a free site check.

← All articles · Privacy policy · pingvera.com