Meta Events Manager: How to Check Your Pixel and Conversions
In Meta Events Manager, you see which events from your website arrive at Meta. Here is how to read the views correctly and find errors before they cost ad budget.

Meta Events Manager is the Meta tool in which you see which events your website sends to Meta: page views, purchases, leads, basket actions. It shows whether the pixel is running, whether the Conversions API is delivering data, how well Meta can match the events to people, and which errors there are. If you advertise on Facebook and Instagram, you should look here regularly, because Meta Ads Manager only optimises for the events that arrive cleanly in Events Manager.
What is Meta Events Manager?
Events Manager is one of Meta’s business tools and can also be reached from Meta Business Suite. It used to be called Facebook Events Manager, and today it runs under the Meta name, but the function is the same. It manages all the data sources that deliver events to Meta. The most important one is the Meta Pixel on your website. Alongside it come the Conversions API, which sends events from the server, offline events from a CRM and app events.
For you as an advertiser, Events Manager has three tasks. First, you check there whether measurement works at all. Second, you define which events count as conversions, for example through custom conversions. Third, you get notices when something is not right, for example missing parameters or double-counted purchases. Without this view, Meta may optimise your campaigns for wrong or incomplete data.
| Area | What you check there | Typical mistake |
|---|---|---|
| Overview | Count per event, route via browser or server | More Purchase events than real orders |
| Test events | Events from your own test run, live | Lead fires on the click instead of after submission |
| Diagnostics | Notices on parameters, domains and duplicates | Pixel and Conversions API without a shared event ID |
| Event match quality | A value from 0 to 10 per event | Hardly any customer data sent along |
| Settings | Advanced matching, allowed domains, access | Former service providers still have access |
Understanding data sources, pixel and dataset
On the left in Events Manager, you find the data sources. Meta now groups pixels and server events under the term dataset. A dataset has an ID, which is at the same time your pixel ID. Everything sent with this ID ends up in the same pot, whether it comes from the browser or from the server.
A common mistake in accounts that have grown over time: there are several pixels. One was created by a former agency, one hangs on the shop plugin, and a third was created for a test. The website then sends to one pixel while the campaigns optimise for another. So first check which pixel ID actually fires on your site, for example with the Meta Pixel Helper browser extension. Then compare it with the ID stored in your ad sets.
→ Cookie banner with Consent Mode v2: compliant, with no monthly licence
How do you check that purchases and leads arrive correctly?
In the overview of a dataset, you see a list of all received events with the count in the chosen period. Standard events such as PageView, ViewContent, AddToCart, InitiateCheckout, Purchase and Lead have fixed names that Meta knows. Next to each is shown whether an event arrives through the browser, through the server or through both.
Pay attention to the ratios. In a healthy shop, there are clearly more PageView events than ViewContent, more ViewContent than AddToCart and, at the end, the fewest Purchase events. If Purchase and InitiateCheckout are almost equal, the purchase probably fires already on the checkout page instead of on the confirmation page. If there are more Purchase events than orders in your shop system, something is being counted twice. Comparing with the real orders of one day is the quickest plausibility test.
- Purchase clearly higher than real orders: duplicate installation or missing deduplication
- Purchase without value or currency: the value and currency parameters are missing
- Lead fires on the click of the submit button instead of after successful submission
- Events only via the browser: the Conversions API is not active
- Sudden drop on one day: usually an update to the theme, a plugin or the cookie banner
Meta test events: checking events live
The Test events tab is the most important tool when you have changed something. You enter the address of your website, Meta opens it in a new window, and every action you carry out there appears in the list after a few seconds. That way you see exactly which event arrives with which parameters.
Run through a real flow: view a product, add it to the basket, go to the checkout, complete a test order. For a trades business with a contact form, you fill in the form and submit it. Then check whether every event appears exactly once and whether Purchase has a value and a currency. If there is a cookie banner on the page, do the test twice: once with consent, once with refusal. Without consent, the pixel must not send anything in the EU.
For server events, the tab shows a test code. The server has to send this code along in the test_event_code field, and then the events from the Conversions API also appear in the test view. According to Meta, events with a test code are not discarded but feed into measurement and delivery. So remove the code after the test, because it is meant only for checking.
→ Setting up Google Consent Mode v2 correctly: no warning in Tag Assistant
Diagnostics and event match quality
Under Diagnostics, Meta collects notices about problems. Typical messages concern missing parameters, invalid values, duplicate events without deduplication, or events from domains that do not belong to your business. Not every message is urgent, but you should take notices about Purchase and Lead seriously, because exactly these events steer your campaigns.
Event match quality rates how well Meta can match an event to a Meta account. It is shown per event as a value from 0 to 10. The basis is the customer data sent along, such as email address, phone number, name, IP address or the click ID that comes from the fbclid parameter of the ad URL. Contact details such as email address and phone number are hashed with SHA-256 before sending, while technical values such as the click ID and IP address are not. A low value does not mean events are missing. It means Meta can match them to people less well, and the campaigns learn less. Sending more customer data is only permitted with consent and a suitable privacy policy. This article is not legal advice.
Conversions API as a second source, and deduplication
The Meta Pixel runs in the browser. Ad blockers, strict browser settings and network problems can stop events from arriving. The Conversions API additionally sends the same events from the server to Meta. In Events Manager, you then see for each event whether it comes through the browser and the server.
So that a purchase is not counted twice, each event needs the same event name and the same event ID on both routes. This is how Meta recognises that it is the same event, so it counts it only once. If the ID is missing or differs, Diagnostics shows duplicate events. Your cost per purchase then suddenly looks much better than it is. For the Conversions API too, you generally need the person’s consent in the EU.
Domain verification and settings
In the Business settings of Meta Business Suite, you can verify your domain, through a DNS TXT record, a meta tag line in the head of the page or an uploaded HTML file. This shows that the domain belongs to your business. You also decide, for example, who may edit link previews for this domain.
In the settings of the dataset, it is worth looking at automatic advanced matching and at the list of allowed domains. With such a list, you stop other sites from writing events into your dataset using your pixel ID. Also check who has access to the dataset. Former service providers should no longer be listed there.
Worked example: finding duplicate purchases in an online shop
A small online shop for coffee accessories saw almost twice as many purchases in Meta Ads Manager as in its shop system. Events Manager showed the reason: the shop plugin sent Purchase through the pixel and the Conversions API, while a second pixel tag was active in Google Tag Manager at the same time. The event IDs did not match. After removing the duplicate tag and aligning the IDs, the numbers matched the orders again.
Such errors often go unnoticed for a long time. In the free Trackum check, a real browser tests your site three times and shows findings with a fixed price to fix them, with no sign-up. Trackum sets up the Meta Conversions API as an extra for €50: in addition to the pixel, from the server, only with consent and without double counting. In the subscription for €19 a month, Trackum tests your site every day and repairs, at no extra charge, whatever breaks in the set-up measurement after an update. All prices excl. VAT.
Frequently asked questions
Where do I find Events Manager on Facebook?
Meta Events Manager is part of Meta’s business tools. You reach it through the menu in Meta Ads Manager or in Meta Business Suite. There you select your pixel or dataset on the left under Data sources.
How do test events work in Meta Events Manager?
In the Test events tab, you enter the address of your website and open it. Every action you carry out there appears in the list after a few seconds. For the Conversions API, there is a separate test code that the server has to send along.
What does event match quality mean?
Event match quality shows, on a scale of 0 to 10, how well Meta can match the events it receives to a Meta account. The more matching customer data is sent along, the higher the value. A low value does not mean events are missing, but that they are matched less well.
Why does Events Manager show duplicate purchases?
Usually the page sends the same event twice, for example through a pixel in the theme and in Google Tag Manager at the same time. With the pixel plus the Conversions API, the shared event ID (event_id), by which Meta recognises duplicates, is often missing.
Sources
- Meta Help Centre: Overview of Meta Events Manager facebook.com
- Meta for Developers: Conversions API developers.facebook.com
- Meta for Developers: Handling duplicate Pixel and Conversions API events developers.facebook.com
- Meta for Developers: Using the Conversions API (test events) developers.facebook.com
- Meta for Developers: Domain verification developers.facebook.com
Read more
FeaturesCookie banner with Consent Mode v2: compliant, with no monthly licence
Reject on the first layer, settings per purpose, Consent Mode v2 with every consent type and a record of each choice. No monthly licence.
FeaturesSetting up Google Consent Mode v2 correctly: no warning in Tag Assistant
The most common warning in Tag Assistant says a tag read consent before a default was set. How to avoid it, and what else matters.
FeaturesMarketing dashboard with GA4 and Google Ads: every number on one page
Visitors, leads, orders, ad spend and ROAS per campaign on one page, compared with the previous period. One link, nothing to set up.
FeaturesRevenue from your CRM, shop and ERP in one dashboard: HubSpot, Shopify, Odoo and more
Google Analytics only sees what happens on the website. Orders by phone or email are missing. With a data connection, the real revenue from your system appears in the dashboard.
FeaturesWebsite leads with their source in your CRM: HubSpot, Pipedrive, Brevo, Salesforce or webhook
Where did the lead come from? The CRM handover writes source, campaign and click ID into the CRM with every enquiry, without a form plugin.
FeaturesOffline conversions: report sales from your CRM to Google Ads and Meta
Google Ads and Meta learn from what you report to them. If they only get form fills, they optimise for form fills. With offline conversions, they optimise for sales.