Page views are not purchases
If Events Manager shows PageView but no Purchase, your pixel works, just not fully. Open your pixel and look at the list of events it has received. The page view event comes with the pixel base code, so it fires on every page. Purchase is a separate standard event. Meta defines it as the completion of a purchase, such as landing on a thank-you or confirmation page. That code must fire on your order confirmation page, after the order is placed. If only the base code is on your site, Meta sees visitors but never sees a sale. Check this before anything else.
Place a test order in Test events
- Open Events Manager and click Data sources in the left menu.
- Select your pixel, then click Test events.
- Enter your store's address and click Open website.
- Add a product to the cart and place a test order, such as a COD order you cancel later.
- Keep the Test events tab open and look for Purchase, with its value and currency.
Check the event with Ads Data Advisor
Meta's free Chrome extension shows what fires on each page. It used to be called Pixel Helper, and it is now Meta Ads Data Advisor. Meta says it can verify that your pixel is installed and that your events fire. It also flags broken events and missing parameters, such as price or currency. Turn off your ad blocker first, or the extension cannot see the pixel. Then open your thank-you page after a test order and look for Purchase in the list.
Send the value in rupees
A Purchase event with no value tells Meta that a sale happened, but not what it was worth. Meta's default code sends USD 0.00, which makes your return on ad spend useless. Set the real order total, and set the currency to INR. Meta says the value must be a decimal number of zero or more, with no currency symbols or commas. So a ₹1,499 order goes in as 1499.00. The value must change with each order, so your developer or platform has to fill it in from the cart.
Why Ads Manager shows fewer sales
Sometimes purchases do arrive, but the numbers do not match. That is often normal. Events Manager counts events from everyone, including organic visitors and people from other channels. Ads Manager counts only events linked to someone who was shown your ad. It also removes duplicates. So Ads Manager will usually show fewer purchases than Events Manager does. A small gap is fine. A total blank is not. Compare both with your own order list before you decide tracking is broken.
Domain checks and old iOS rules
Older guides tell you to verify your domain and rank eight events for iOS users. Meta has dropped that. Under its updated Aggregated Event Measurement, you no longer need to prioritise eight conversion events per domain. You are also not required to verify your domain for event setup. You may still verify it for other reasons, such as control over who can edit your links. One domain problem does matter. If Meta blocks your domain for a policy breach, its events cannot be used, so check the Diagnostics tab.
Cookie consent can hide sales
If your pixel loads only after a shopper accepts cookies, buyers who decline are not counted. That is the right trade for privacy, but Meta will always see fewer sales than you make. Meta's terms also require you to tell visitors how you use cookies. On The Storemate, the pixel ID you add in the tracking settings loads only after a shopper accepts marketing cookies in your cookie banner. So test with cookies accepted, and judge your ads against real delivered orders.