How do I check whether my Meta pixel is tracking properly?
How do I check whether my Meta pixel is tracking properly?
You can check it yourself in about ten minutes, by placing a test order on your own store and watching the events arrive in Meta Events Manager. If the Purchase event does not appear, or appears with a value that does not match the order, the problem is in the tracking rather than in the advertising.
What should a working pixel be recording?
A standard Shopify and Meta setup sends a small set of named events as a shopper moves through the store: PageView when a page loads, ViewContent on a product page, AddToCart, InitiateCheckout, and Purchase once the order is paid for. Purchase is the one that matters for reporting, because it carries the order value and the currency, and every ROAS figure in Ads Manager is built on it. Shopify's own Meta sales channel configures most of this during setup, which makes it easy to assume the job is done and never look at it again.
How do I run a test order?
Create a product priced at a pound or two and leave it out of your collections and search results, so no customer finds it. In Meta Events Manager, open your pixel, then the Test Events tab, and paste in your store URL. Go through the whole journey on the live site: load the product page, add it to the basket, start the checkout and pay. The events appear in a live list as you go, usually within a few seconds of each step. When you are finished, refund the order and archive the product.
If Purchase never appears, that is your answer. If every event appears except Purchase, the break is at the checkout rather than on the site itself.
What if Purchase fires but the value is wrong?
Check what the event value is actually made of. Depending on how the pixel was configured it may include shipping, and in the UK it may include VAT, which means the revenue Meta reports is higher than the money the business keeps and the ROAS built on it reads better than it should. A value of zero, or a value that matches a different order, usually points to a conversion-tracking app layered on top of the native setup.
What if the same order is counted twice?
A browser pixel and a server-side Conversions API connection can both report the same purchase. They are meant to be matched and merged using a shared event ID; when that is missing, one order is counted as two. Events Manager flags duplicates in its diagnostics, and the symptom is reported sales running consistently above the orders in Shopify.
What we've seen in practice
Pixels rarely break outright. They break partly. The Purchase event keeps firing for some shoppers and not others, so reported sales drop by a third rather than to zero, and nothing looks broken enough to investigate. The cause is usually a change made for a different reason — a theme update, a new checkout or upsell app, a cookie banner set to block scripts until consent is given. When a merchant brings us a month that looks bad, the first thing we ask for is the date of the last change to the theme or the apps. The two dates line up more often than not.
Compass reads the orders in the Shopify store rather than relying on the pixel, so a broken event shows up as a gap between the store and the platform instead of as a quiet drop in reported sales.
Recent Posts










