Events Manager Warnings? 9 Diagnostics Explained
What do Meta Events Manager diagnostics warnings mean?
Each diagnostic is Meta telling you an event arrived wrong or in an unexpected way. Red icons are critical; yellow are warnings. Meta documents nine pixel messages: invalid currency, missing value, pixel and server value mismatch, unusual value, event name mismatch, multiple events per action, redundant purchases, invalid email and duplicate automatic events, plus new-domain alerts.
A diagnostic is not a penalty. It is Meta telling you that an event reached it in a form it cannot use well: a currency it cannot read, a purchase counted four times, a domain it has never seen. Fixing the ones about Purchase comes first, because those change the revenue and ROAS you see in Ads Manager. The list below covers the messages Meta itself documents for the pixel, what triggers each, and the fix.
Where do I find Events Manager diagnostics?
Meta’s steps (View diagnostics in Meta Events Manager):
- Go to Events Manager and click the Data sources tab on the left.
- Click your pixel or dataset. A red icon next to it means there are critical issues.
- Click the Diagnostics tab and review the issues under Active.
- Click Learn how to fix this issue on each one, and follow Meta’s steps.
- Mark web and app issues as resolved once fixed, to move them to Previously detected.
What do the red and yellow icons mean?
Meta sorts issues into two types (About diagnostics in Meta Events Manager):
- Critical (red icon). Fix as soon as possible. Meta says these cover high-priority changes, such as platform updates, privacy regulations and violations of its policies.
- Warning (yellow icon). Lower priority. Meta’s examples are a value parameter that may be set up wrong, or a pixel that recently started sending events from a new domain.
Issues also move between three tabs. Active holds anything detected in the last 24 hours. If you do nothing for three days after first detection, an issue moves to Previously detected and Meta removes its fix instructions. If Meta does not see an issue the following day, it moves it there for you, and moves it back to Active if it returns after three days. Ignored holds issues you dismissed. For web and app events, marking an issue resolved or ignored applies to everyone in the business portfolio.
What do the 9 pixel diagnostics mean, and how do I fix them?
Meta lists these errors and warnings for the pixel (How to troubleshoot Meta pixel error and warning messages):
| Diagnostic | What triggers it | Fix |
|---|---|---|
| Currency parameter has a missing or invalid 3-letter code | No currency, or one that is not an ISO code | Send codes such as USD or GBP with every value |
| Missing or invalid price in value parameter | Value empty, missing or wrongly formatted | Send a decimal number of 0 or more, with no letters, symbols or commas |
| Mismatches in currency and/or value parameters | Pixel and Conversions API send different value or currency for one event | Make both read the same order total and currency |
| Price in value parameter is higher/lower than normal | A value far outside your usual range | Check that the value field holds the real order amount |
| Event name mismatch | A name close to a standard event, such as purchase | Use the exact, case-sensitive name, such as Purchase |
| Multiple events on an action | Several events fire for one click or page load | Add event code only where the action happens; keep only the base code in the header |
| Redundant purchase events | Four or more Purchase events for one purchase | Fire Purchase only on the order confirmation page |
| Invalid email provided | Advanced matching sends a malformed email | Pass the customer’s real email field, correctly formatted |
| Duplicate events detected | Your code and Meta’s automatic events log the same event | Turn off automatic events for that dataset |
Meta’s page also lists a tenth alert, New domain sending data, covered below, plus two restricted-data messages that need their own review.
Why do value and currency warnings matter most?
They change your reported revenue. Meta says that when pixel and server values differ and the events are deduplicated, the retained event may not carry the true value, “which may lead to inaccurate return on ad spend (ROAS) calculations”. The default standard event code includes a value of zero, so a copied snippet that was never edited reports zero-value purchases. Meta’s rule for the field is a decimal number greater than or equal to zero, without currency symbols or commas.
To find where the mismatch comes from, compare one order across both sources in the Test events tab, then follow how do I diagnose duplicate events between pixel and CAPI? If purchases arrive with no value at all, work through why do my Meta purchase events show no conversion value?
What does “Redundant purchase events” mean?
Meta raises it when the pixel receives four or more Purchase events for a single purchase. It warns this can over-report purchases and hurt delivery of ads using the conversion or catalogue sales objectives. Meta points to two causes: Purchase code in the site’s header template, and Purchase code on pages that do not confirm a purchase.
Meta’s fix: add purchase event code only to a page that confirms the purchase, and keep only the base code, which contains the PageView event, in the header. Click See affected URLs in the diagnostic to find the pages. “Multiple events on an action” has the same fix for other events.
What does “Duplicate events detected” mean?
It means the same event arrives twice, once from your own code and once from Meta’s automatic events, which Meta describes as events its AI detects on your website (Set up automatic events). To turn them off:
- Go to Events Manager and click Datasets in the left menu.
- Select your dataset and click Settings.
- Toggle Automatic events off below Event setup.
Meta notes that from 3 August 2026, new pixels ask you to confirm the automatic events setting during setup, and it is on by default. Check it on any pixel created since then.
What does “New domain sending data” mean?
Your pixel started receiving events from a domain it had not seen before. Meta says this happens when someone else puts your public pixel ID on their site, or when a partner integration, iframe or redirect sends events from another domain (About Meta pixel traffic permissions). Meta emails one person with full control of the business portfolio or ad account and shows the alert in Diagnostics.
If the domain is yours or your checkout’s, leave it. If not, add an allow list in the Traffic permissions setting in Events Manager. Meta suggests an allow list over a block list, and you can use one or the other, not both.
What about the warnings not in the table?
Meta documents two more: “Event parameters blocked” and “Your data is restricted”. Both mean Meta found data that may break the Meta Business Tools Terms; the second places the pixel in a core setup that restricts custom parameters and parts of URLs. Treat them as a data review, not a tracking fix, and work through why does Meta say my pixel is sending restricted data? before requesting an unblock.
If the Diagnostics tab is clean but events have stopped, the problem is upstream: read why does my Meta pixel show no recent activity? For a full pre-launch run, use what should I check when setting up Meta Pixel and CAPI? and the account-wide Meta ads audit checklist.
FAQ
Should I ignore Events Manager warnings?
Ignore one only after you have read it and decided it does not apply, such as a new domain that is your own checkout. Ignored issues stay in the Ignored tab until you move them back. Value, currency and redundant purchase warnings affect reported revenue, so fix those rather than dismiss them.
How long does a diagnostic take to clear after a fix?
Meta checks daily. If it does not detect the issue the following day, it moves the issue from Active to Previously detected on its own. For web and app events you can also mark it resolved. If the issue appears again after three days, Meta moves it back to Active.
Do diagnostics cover Conversions API events too?
Yes. Meta says the Diagnostics tab covers web, app and offline events, and some messages, such as mismatched currency or value, only appear when the pixel and the Conversions API disagree. For server events, Meta also suggests hovering over the ! icon in Diagnostics for detail on each connection issue.
Why did a diagnostic disappear before I fixed it?
Meta moves an issue to Previously detected if you do not interact with it within three days of first detection, and removes the fix instructions when it does. It can also move there because Meta did not see it the next day. Check the Previously detected tab before assuming the problem is gone.
Sources
Sources: Meta Business Help Center, About diagnostics in Meta Events Manager, View diagnostics in Meta Events Manager, How to troubleshoot Meta pixel error and warning messages, Set up automatic events, About Meta pixel traffic permissions, Monitor and improve your Conversions API setup (checked 2 Oct 2026).