Meta Purchase Event Not Firing After an Order: What to Check
A Purchase event that does not fire after an order means Meta never learns about the sale. The break is somewhere between the order completing and the event reaching Meta. The order data may not be available where the tag fires, the trigger may point at the wrong page or consent may block the event at the finish line.
Table of Contents
- 01.The Purchase event journey
- 02.What to check first
- 03.Is the tag on the right page
- 04.Is the purchase data available
- 05.Consent at the finish line
- 06.How to test it
The Purchase event journey
A Purchase event follows a specific path. The order completes, the purchase data becomes available, the Purchase event fires with that data and Meta receives it. If any step fails, the sale is invisible to Meta even though it happened in your store.
| Step | What must happen | Common failure |
|---|---|---|
| 1. Order completed | Customer reaches confirmation | Order fails or redirects away |
| 2. Purchase data available | Value, currency and IDs exposed | Data layer empty on confirmation |
| 3. Purchase event fires | Tag fires on thank-you page or event | Trigger points at wrong page |
| 4. Meta receives event | Network request reaches Meta | Consent blocks at checkout |
What to check first
- Complete a real test order and reach the thank-you page.
- Confirm the Purchase tag fires on that page using Test Events.
- Check whether the data layer or purchase variables are populated.
- Confirm the trigger matches your actual confirmation page URL.
- Check whether consent blocks the tag at checkout.
Is the tag on the right page
Most Purchase events fire on the order confirmation or thank-you page. If your trigger points at a URL that no longer exists or uses a path that changed after a platform update, the tag never fires. Complete a test order and note the exact confirmation URL, then compare it to your trigger condition. A trigger built for an old checkout flow is a frequent cause of a Purchase event that silently stopped working.
Is the purchase data available
The tag can fire on the right page but with no value if the purchase data is not exposed. If you rely on a data layer, confirm it is populated with the order total, currency and transaction ID on the confirmation page. If the data layer is empty or fires after the tag, the event reaches Meta with missing or zero value. Check the data layer in devtools before you assume the tag itself is broken.
Consent at the finish line
Checkout is where consent problems bite hardest. If your consent banner is configured to block tags until accepted and the customer reaches the confirmation page without accepting, the Purchase event never fires. Some setups fire a delayed event after consent, others do not. Confirm how your consent setup treats the confirmation page before blaming the tag.
How to test it
- 1.Place a real test order with a small product value.
- 2.On the confirmation page, open devtools and check the data layer.
- 3.Confirm the Purchase event fires in Test Events.
- 4.Confirm the value and currency in the event match the order.
- 5.If the event is missing, check the trigger URL, then the data layer, then consent.
If the value is wrong rather than missing, the issue is in how the purchase value is calculated, which is a separate problem covered in the guide on Meta Purchase value being wrong.
Frequently Asked Questions
Should I fire the Purchase event on the checkout button click instead?
No. Purchase should fire after the order is actually completed, usually on the confirmation page. Firing it on a button click counts clicks as purchases and inflates your data. The event must represent a completed order.
Why did my Purchase event stop firing after a platform update?
Platform updates can change the confirmation page URL or the data layer structure. A trigger built for the old URL or old data layer will stop matching. Re-run a test order and compare the current confirmation page and data layer with your trigger conditions.
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
Meta Purchase Value Is Wrong: How to Troubleshoot Value and Currency Tracking
A wrong purchase value is a definition and mapping problem, not a tag bug. Decide what the value should represent, confirm the tag pulls that exact figure and make the currency match.
Meta CAPI Purchase Events Missing: How to Trace the Server-Side Event Flow
A missing CAPI Purchase is a server-side flow problem. Confirm the order triggers the server logic, confirm the payload carries the order data and check the CAPI response.
Meta AddToCart Event Not Firing: Common Tracking Problems and Fixes
AddToCart fails most often because the trigger type does not match the cart behavior. Find out whether your cart reloads or updates in place before choosing a trigger.