Pixel Tracks PageView but Not Purchase? 6 Fixes
Why does my Meta pixel track PageView but not Purchase?
PageView comes with the pixel base code; Purchase does not. It must be set up separately, on the order confirmation page or by your store's integration. When PageView arrives but Purchase doesn't, check six things: a missing or misspelled event, a confirmation page the pixel never loads on, an off-site checkout, iframes, ad blockers and value parameters.
A pixel that logs PageView is installed, and that is all it proves. Meta’s base code sends PageView on every page by itself, while Purchase fires only where a Purchase event was added: on the thank-you page, on a buy button, or by your store’s app. So when PageView arrives and Purchase never does, look at the last step of checkout, not at the pixel. The event is missing, misnamed, or running on a page the pixel cannot see.
Why does PageView work when Purchase doesn’t?
Because they are set up in different places. Meta says the PageView event “is automatically included as part of your pixel base code”, so it fires on any page that loads the base code (Best practices for Meta pixel standard event setup). Every other standard event has to be added. Meta defines Purchase as “a person has finished the purchase or checkout flow and lands on thank you or confirmation page”, with currency and value required (Meta pixel reference).
That makes the confirmation page the single point of failure. If the Purchase code is not on it, or the page loads somewhere your pixel does not run, Events Manager shows healthy PageViews and no sales. This is different from a pixel that has gone silent everywhere, which is covered in why does my Meta pixel show no recent activity?
Which of the six causes is stopping Purchase?
Match what you see in Events Manager to the row below. Each cause comes from Meta’s or Shopify’s own troubleshooting pages, linked in the sections that follow.
| What you see | Likely cause | Fix |
|---|---|---|
| No Purchase event has ever arrived | Purchase was never set up; only the base code is installed | Add Purchase through your store’s integration, the Event Setup Tool or code |
| A custom event called “purchase” or similar appears | The event name is misspelled or in the wrong case; events are case sensitive | Rename it to exactly Purchase |
| Purchase arrived until your Shopify thank-you page was upgraded | The Purchase code lived in additional scripts, which Shopify says must be replaced on the upgraded pages | Track Purchase through the Facebook & Instagram app pixel or a custom pixel |
| Purchase is missing for orders paid on another domain | The confirmation page sits on a payment or checkout domain without your pixel | Add the base code there, or send Purchase from your server |
| The Event Setup Tool cannot add the event | The pixel or button sits in an iframe, or you use an image pixel | Set up Purchase in code instead |
| Purchase arrives for some buyers but not others | Ad blockers stop the browser pixel | Send Purchase through the Conversions API as well |
How do I confirm where Purchase stops?
Test with a real order, because the confirmation page only exists after one. Meta’s tools for this are Test events, Diagnostics and the Meta Ads Data Advisor Chrome extension (Best practices for Meta pixel standard event setup).
- Open Events Manager, select your pixel under Data sources, and open the Test events tab.
- Place a test or low-value order on your site and watch which events arrive, in order.
- Install Meta Ads Data Advisor in Chrome and load the confirmation page to see whether Purchase loads there.
- Open the Diagnostics tab in Events Manager and look for “Event name mismatch” or missing value and currency.
- On Shopify, open Settings, then Customer events, and check which app or custom pixel is meant to send Purchase.
- Fix the cause, then repeat steps 1 to 3 with a new order.
Meta notes that parameters can take 20 minutes to attach to events in Events Manager, so a fresh test may look incomplete at first (Troubleshoot the Event Setup Tool).
Is the Purchase event misspelled or missing?
Check the name before anything else. Meta says standard events are case sensitive, and that a misspelled name creates a custom event instead of the standard one. Events Manager flags this as “Event name mismatch”, with a “See affected URLs” link to the pages carrying the wrong code (Troubleshoot Meta pixel errors and warnings).
Placement matters as much as spelling. Meta’s advice is to put Purchase code only on a page that confirms the purchase, such as a thank-you page, or on an inline action like a Buy now click. The only Meta code that belongs in the site header is the base code. A Purchase snippet pasted into the header fires on every page, which shows up as the opposite problem: Meta raises a “Redundant purchase events” error when it receives four or more Purchase events for one order.
Did Shopify’s thank-you page upgrade break my Purchase event?
It can, if Purchase was hand-coded. Shopify made the additional scripts section in Checkout settings view-only on 28 August 2025, and 26 August 2026 was the deadline for stores on non-Plus plans to upgrade their Thank you and Order status pages. Scripts used for tracking have to be replaced on the new pages, and Shopify points to app pixels to keep tracking customer events (Shopify checkout upgrade).
Shopify’s pixels run on the storefront, checkout, Thank you and Order status pages (Pixels overview). With data sharing on in the Facebook & Instagram app, Shopify tracks Purchase along with six other events; turn it on under Sales channels, Facebook & Instagram, Settings, then Data sharing settings (Meta data sharing). If you use a custom pixel instead, it can subscribe to the checkout_completed event (Custom pixel code). Shopify notes custom pixels need JavaScript knowledge, run in a sandbox where not all pixel functions work, and are not supported by Shopify. If two installs are now competing, see why is my Meta pixel not firing on Shopify?
What if checkout or payment happens on another domain?
Then the pixel never sees the confirmation page. For partner integrations and third-party redirects, Meta’s fix is to add your pixel base code to the third-party site, or set up the base code on your own site in code (Troubleshoot the Event Setup Tool). Where you cannot touch the third-party page, send Purchase from your server through the Conversions API, which Meta recommends alongside the pixel because it “shares website events the pixel may miss” (Best practices for Meta pixel standard event setup).
Check one setting while you are there. Meta lets you create a domain allow list or block list for the domains allowed to send events through your pixel, so a checkout domain left off an allow list will not be accepted (Troubleshoot Meta pixel errors and warnings). Wallet and express flows raise a related gap, covered in does express checkout break my Meta pixel tracking?
Do ad blockers and value parameters matter?
Yes, in different ways. Meta says the pixel “may not fire if someone is using an ad blocker”, which removes some purchases but not all (About conversion count differences). Shopify’s Standard data-sharing level uses the pixel alone and can be blocked; Enhanced and Maximum add the Conversions API, which browser ad blockers cannot stop. Value problems do not hide Purchase, but they break ROAS: Meta wants a three-letter currency code and a value that is a decimal number of zero or more, with no currency symbols or commas. For how the pixel and server fit together, see How Do Meta Pixel and CAPI Work Together?
Can software help?
Bach.ai (by Wittelsbach) connects to a Meta ad account, audits it daily, finds revenue leaks with an estimated revenue impact, and proposes fixes. It applies a change on Meta only after you approve it; the pixel and checkout fixes above are made in your store and Events Manager.
FAQ
Can I track purchases with a URL rule instead of code?
Yes, as a fallback. When the Event Setup Tool cannot reach a button, Meta suggests setting up a custom conversion for URLs, such as your confirmation page address. It counts visits to that page as conversions. Code or a store integration is still better, because it can send the order value and currency.
Why does Purchase show up several times per order?
The Purchase code is firing on more than one page, often because it sits in the site header or the page reloads. Meta raises a “Redundant purchase events” error at four or more Purchase events for one purchase. Move the code to the confirmation page only and keep the header to the base code.
Does a missing value stop Purchase from being recorded?
No, but it weakens the event. Events Manager warns when the value parameter is empty or badly formatted, or the currency code is missing. Meta requires both for Purchase, and without them your reported purchase value and ROAS will be wrong even though the event arrives.
Sources
Sources: Meta Business Help Center, Best practices for Meta pixel standard event setup, Troubleshoot Meta pixel error and warning messages, Troubleshoot the Event Setup Tool and About conversion count differences; Meta for Developers, Meta pixel reference; Shopify Help Center, Checkout upgrade, Pixels overview, Meta data sharing and Custom pixel code (checked 2 Oct 2026).