This guide is about the tool. For what to do when Purchase does not fire at all, see Meta Pixel purchase event not firing on Shopify.
Where to find it
Meta's developer documentation gives the path: Events Manager > Data sources > your pixel > Test events. Meta also calls the pixel a dataset. Meta's help, as far as we could read it, lists the tab next to Overview, Diagnostics and Settings.
Test events has two parts, one for browser events and one for server events. They work differently.
Test browser events
Browser events come from the Meta Pixel in the shopper's browser. On Shopify that is usually the Facebook & Instagram app's pixel, or a custom pixel in Settings > Customer events.
- 1In Test events, enter your store's address and open it from there. Your visit is then marked as a test, and its events show in the tool.
- 2Accept cookies on your banner. A pixel that waits for marketing consent sends nothing until you do.
- 3View a product, add it to the cart and check out.
- 4Wait for the Thank you page to load fully, then watch the list.
Meta's help, as far as we could read it, says that if nothing shows you can turn off ad blockers and refresh the site, and that not every browser works with the tool. Try another browser before you change any settings.
Test server events
Server events come from the Conversions API. On Shopify they come from the Facebook & Instagram app at the Enhanced or Maximum level, or from an app or service that sends them for you.
Meta's developer page says the Test events tool generates a test ID, and that you send it as the test_event_code parameter to see server events in the Test events window. In practice:
- A sender that lets you enter the code shows its events in Test events within moments. The code goes into the sender's settings, not into Meta.
- In our experience, a sender with no field for the code does not show its server events there. Its events still arrive. You check them later in Overview, by opening the Purchase event and reading where the events came from.
Meta says the test_event_code field is for testing only and must be removed from production requests. A sender that keeps it on would mark every real purchase as a test.
What a test purchase does to your data
Test events is not a sandbox.
Meta's developer page says events sent with test_event_code are not dropped, and that they flow into Events Manager and are used for targeting and ads measurement. A browser purchase you made from the Test events tool is a real event from a real browser.
So:
- A purchase you place while testing can show up in your Purchase count and in your ads results.
- Use a low price product and refund or cancel the order afterwards, so your Shopify sales stay right.
- Shopify's test payment method creates a test order in Shopify. Whether a sender passes a test order to Meta depends on that sender. See Test orders showing up in Meta or GA4.
How to read what arrives
Open each Purchase in the list and check four things:
- 1Where it came from. Browser, server, or both. A Purchase from both sources is normal in Meta's recommended setup, as long as they share an event ID.
- 2The event ID. If browser and server both arrive, the two copies should carry the same ID. Different IDs mean Meta counts the order twice. See Meta event deduplication on Shopify.
- 3Value and currency. Compare them with the order in Shopify. A total with shipping where you expect the subtotal is a setting of the sender, not a bug in Meta.
- 4The customer details received. Meta lists the parameters that came with the event, such as e-mail or phone. Few details mean weak matching. See Low Event Match Quality for Purchase in Meta.
Meta's help, as far as we could read it, says the tool keeps test activity for 24 hours, or until you click Clear activity. Clear it before each new test, so you do not read an old event as a new one.
What Test events does not tell you
- That every order arrives. One test order shows that the path works once, in your browser, with your consent. It says nothing about shoppers with ad blockers or who close the tab early. For that, compare a week of Meta's count with your paid orders: see Meta shows fewer purchases than Shopify.
- What Ads Manager will credit. Ads Manager credits purchases to ads by its attribution setting, and can take hours.
- What the deduplicated count is. Meta's guide says Overview shows events before deduplication. The Event Deduplication tab under Event Details shows how many copies Meta matched.
The other checks are in checking deduplication in Events Manager.
FAQ
Why does Test events show my browser Purchase but no server Purchase?
Either nothing sends one from a server, or the server sender does not carry your test code. Check the sender's settings for a test code field, then check Overview after a few hours. See CAPI received nothing in Events Manager.
Can I test without placing a real order?
For browser events you need the checkout to reach the Thank you page. Some senders offer their own test event that is not a Purchase. It shows the connection works, not that purchases arrive.
Does the test code expire?
Meta does not say on the pages we read. If a sender reports that Meta accepted an event but nothing shows, copy a fresh code from the tool and try again.
Where Tikra fits
Tikra sends each paid online order of your store from our server to Meta through the Conversions API, as a Purchase, and keeps a record for each order: what was sent, when, and Meta's answer. In Tikra, Send test on the Meta card takes the code from your Test events tab and sends one event named ConnectionTest. It is not a Purchase, so it does not count as a sale. Test orders from Shopify's test payment method are marked Test and do not go to a live platform.
A new Meta connection starts in a check before sending, and Meta gets nothing from Tikra during it. With a key that can read your pixel's statistics, Tikra reads Meta's own count every day for at least 48 hours and shows whether another connection still sends your purchases; with another key, sending starts after you turn the store's own Meta purchase tracking off and confirm it on the Meta card. Tikra applies your customers' consent choices to every order, and in Strict mode an order is sent only with the buyer's consent. A written guarantee in our Terms covers eligible orders: at least 97 % reach each platform, fixed within 12 hours or a month's fee credited (Terms of Service, section 8).
The free diagnosis sends none of your orders anywhere, not even as test events. It shows your paid orders of the last 7 full days, how many came from a Meta, Google or TikTok ad, and, after a full day and 10 paid online orders, how many your shoppers' browsers reported. With a key that can read your pixel's statistics, it also shows Meta's count.