GA4 Ecommerce Purchase Event Not Firing: What to Check
When the GA4 purchase event is not firing, the order completed but no purchase data reached GA4. The break is somewhere between the order finishing and the GA4 request being sent. Trace the flow from order completion to the purchase event to find where the data stops, because the fix depends on which step fails.
Table of Contents
- 01.The purchase flow you are debugging
- 02.What to check first
- 03.Is the order data available
- 04.Is the purchase event being generated
- 05.Is the GA4 tag firing
- 06.Measurement ID and consent
- 07.Confirmation page reloads and dynamic checkout
- 08.How to test it
The purchase flow you are debugging
A GA4 purchase event has to be generated after an order completes. The customer finishes checkout, the order data becomes available, the purchase event is generated with transaction_id, value, currency and items, the GA4 request is sent, and GA4 receives the purchase. If any step fails, GA4 shows no purchase for that order. The event does not create itself, so a missing purchase usually means the generation step never ran or the request never reached GA4.
| Step | What happens | Where it can break |
|---|---|---|
| 1. Order completes | Customer finishes checkout | Checkout error, no confirmation |
| 2. Order data available | Order ID, value and items exist | Data layer not populated |
| 3. Purchase event generated | Event pushed with ecommerce data | Event never pushed |
| 4. GA4 request sent | Tag sends the event to GA4 | Tag not firing, wrong trigger |
| 5. GA4 receives purchase | Event appears in GA4 | Wrong measurement ID, consent |
What to check first
- Confirm the order actually completed in your store backend.
- Check whether a purchase event is pushed to the data layer on the confirmation page.
- Confirm the GA4 purchase tag fires for that data layer event in GTM preview.
- Confirm the GA4 request is sent with the correct measurement ID.
- Check GA4 DebugView for the purchase event.
Is the order data available
The purchase event depends on order data existing first. On the order confirmation or thank-you page, the order ID, value, currency and items have to be available to the tracking layer. If the confirmation page loads but the order data is not pushed into the data layer, no purchase event can be generated from it. Inspect the data layer on the confirmation page and confirm the ecommerce purchase object is present with a transaction_id. A confirmation page with no ecommerce data is the first place this flow breaks.
Is the purchase event being generated
Order data existing is not the same as a purchase event being generated. The platform or the tracking implementation has to push a purchase event into the data layer. If you use a native integration, confirm it is configured to send the purchase event. If you use GTM, confirm a data layer push fires for the purchase action. A confirmation page that has order data but no purchase event push means the generation step is missing.
Is the GA4 tag firing
Once the purchase event is in the data layer, a GA4 tag has to fire to send it. In GTM preview, check whether the purchase tag fires for the data layer event. A tag that is skipped usually means the trigger condition does not match the event name. A tag that is not fired means the trigger never evaluated true. The trigger has to match the exact event name your data layer pushes. This is the same firing flow covered in the guide on GA4 GTM tags not firing.
Measurement ID and consent
A tag that fires with the wrong measurement ID sends the purchase to the wrong property, so it looks missing in the one you are checking. Confirm the measurement ID in the tag matches your GA4 property. Consent can also stop the purchase event if the tag waits for consent and the visitor did not accept. On a confirmation page, consent state matters because the visitor may have just passed through checkout. Confirm the consent state in preview and whether the tag has a consent condition.
Confirmation page reloads and dynamic checkout
Some checkout flows redirect to a confirmation page, others update the page dynamically without a reload. If the confirmation is dynamic, a trigger that fires on page load misses the purchase because no new page load happens. The trigger has to fire on the data layer event, not on page load. Also watch for confirmation page reloads, which can fire the purchase event twice if the data layer push runs on every load. Duplicate purchases are covered in the guide on GA4 purchase event firing twice.
How to test it
- 1.Complete a test order and reach the confirmation page.
- 2.Inspect the data layer and confirm the purchase object with transaction_id is present.
- 3.Open GTM preview and confirm the purchase tag fires for the data layer event.
- 4.Confirm the GA4 request is sent with the correct measurement ID.
- 5.Check GA4 DebugView for the purchase event with the correct parameters.
Frequently Asked Questions
Why does my GA4 purchase event not fire on the thank-you page?
The order data may not be pushed into the data layer, or the GA4 tag trigger may not match the purchase event name. Inspect the data layer on the confirmation page and confirm the purchase tag fires in GTM preview.
Do I need transaction_id for the GA4 purchase event?
transaction_id is the identifier that distinguishes one purchase from another and helps prevent duplicate counting. Without it, GA4 cannot deduplicate purchases if the event fires more than once. The guide on GA4 purchase transaction ID missing covers this in detail.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
GA4 Purchase Event Missing Transaction ID: Why It Matters and What to Check
transaction_id is what makes a purchase deduplicatable and reconcilable. Trace the order ID from the confirmation page through the data layer to the GA4 tag to find where the identifier drops.
GA4 Purchase Revenue Is Wrong: How to Troubleshoot Value and Currency
A wrong purchase value usually comes from tax, shipping or discounts being included or excluded differently at some step. Define what the value should represent, then check each step in the flow.
GA4 Ecommerce Data Layer Not Working: How to Find the Problem
The data layer is the foundation under every GA4 ecommerce event. If the push is missing, mistimed or malformed, no tag configuration can recover the data. Find where the data stops.