Events Manager Warnings Explained, One by One
What Meta Events Manager's event statuses and diagnostics mean, using Meta's own wording: Warning and Error statuses, mismatched and IPv4 IP addresses, FBC coverage, placeholder emails and phones, deduplication, freshness and rejected events.
Written by Qualimize Team
Founder, Qualimize
- Published
- Last updated
- Reading time
- 12 min read
Table of contents
- 01 The short answer
- 02 Event statuses: Active, Inactive, Warning, Error
- 03 IP address warnings
- 04 Click ID and placeholder warnings
- 05 Deduplication warnings
- 06 Freshness and events that never arrive
- 07 Pixel setup issues and missing parameters
- 08 How to work through the list
Full article
The short answer
Events Manager warnings are Meta's way of saying an event is arriving but with a problem that may hurt matching, attribution or optimisation. Meta labels an event Warning when there are one or more issues with its signal that may affect performance, and Error when it has a critical configuration issue that requires action. Most warnings trace back to missing or placeholder customer data, IP addresses, deduplication or late sending.
This guide covers only warnings and statuses whose wording appears in Meta's own documentation, explains what each means, and says whether it matters for events sent from a CRM. The labels you see may differ slightly by account and language.
Event statuses: Active, Inactive, Warning, Error
Meta's Ads Data Advisor documentation defines the statuses an event can show. Active means your event is being sent correctly. Inactive means it is not currently sending data. Warning means there are one or more issues with your event signal that may affect performance. Error means a critical configuration issue that requires action, with examples such as blocked parameters, duplicate events and compliance violations. There is also Auto-detected, for events Meta picked up from website activity without extra code.
Inactive on a CRM event is often not a fault. If your team marked nobody as Converted this week, the Purchase event will go quiet. Check your CRM before checking your code.
Error needs attention first. Warnings can wait for your weekly review, but understand each one before you dismiss it.
Statuses apply per event, not per dataset, so one healthy event can sit next to a broken one. A common pattern for lead businesses is a website Lead event marked Warning because of browser data issues, while CRM events such as SubmitApplication show Active. Read each event's status on its own, and do not assume the whole setup is broken because one row is yellow.
Meta's general advice in the same documentation is simple: if any errors or warnings are displayed, implement the suggested fixes, and click into the event for detail. The sections below explain what those suggestions mean, so you can judge which ones matter for your setup.
IP address warnings
Meta's Dataset Quality API documentation lists two IP diagnostics by name. 'Server sending mismatched IP addresses' means your server is sending client IP addresses that do not match those from the Meta Pixel. The usual cause is a server that sends its own address, or a proxy's, instead of the visitor's. The fix is to send the client_ip_address captured from the customer's own browser, not your server's address.
'Update your IPv4 IP addresses to IPv6 IP addresses' means your server is sending IPv4 addresses through the Conversions API, and Meta recommends sending IPv6 addresses instead. In practice that means capturing the visitor's IPv6 address when their connection has one, which may need your web server or hosting to accept IPv6 traffic. The same documentation also lists Empty IP (events sent without a client IP) and Relay IP (an address belonging to a privacy relay, not the customer) as issue types.
For CRM stage events, these mostly do not apply. A status change made by a rep in an office has no customer browser behind it, so there is no customer IP to send. IP warnings matter for website events sent from your server.
Click ID and placeholder warnings
FBC coverage is listed by Meta as an issue when the fbc click identifier is present on too small a share of events. fbc comes from the fbclid that Meta adds to ad click URLs. If your website form does not capture fbclid and pass it on, server events lose the most direct link to the ad click.
Email placeholder and Phone placeholder are listed when a large share of events use the same placeholder email or phone number. This happens when a form makes the field mandatory and people type test@test.com, or when a system fills a default like 9999999999 when the field is empty. Placeholder values do not identify anyone and can confuse matching; send nothing for that field instead.
For Instant Form leads with a stored Meta lead ID, low fbc coverage is expected, because those leads never visited your website. The lead ID does that job.
Deduplication warnings
Deduplication only matters when the same event reaches Meta from two sources, usually the Pixel in the browser and the Conversions API from your server. Meta's verification documentation points to the Event Deduplication tab in each event's details in Events Manager, which shows Rate of Events Deduplicated and Rate of Deduplication Key Usage, and says a warning appears when the deduplication rate is too low.
Meta deduplicates when the browser's eventID matches the server's event_id and the event names match, within 48 hours of the first event with that ID. If the server sends an event with no event_id, or a different one from the browser, both are counted.
CRM-only events, such as SubmitApplication sent on a status change, have no browser twin, so there is nothing to deduplicate. Still send a stable event_id: it stops a retried send from being counted twice.
Freshness and events that never arrive
Meta also measures how quickly events arrive; its Dataset Quality API reports this as data freshness, with upload frequencies such as real_time and hourly. Slow freshness on CRM events usually means statuses are updated late or sent in batches. Meta's CRM implementation guide says calls should ideally be made in real time, with hourly or daily batches as a fallback and uploads at least once a day.
Some problems never show as a warning, because Meta rejects the event outright. Meta's server event documentation says that if any event_time in a request is more than 7 days old, the entire request returns an error and no events in it are processed. Meta's Conversion Leads documentation says an invalid lead_id gets the event rejected, and that an error anywhere in a batch discards the whole batch.
These failures only show up in your sending tool's logs or as a gap in Events Manager. If event counts look low, check the API responses, not only the Diagnostics tab.
- Any event older than 7 days: whole request rejected
- Invalid lead_id: event rejected
- Error in a batch: whole batch discarded (batches can hold up to 1,000 events)
- Conversion Leads event dated before the lead was created: may be discarded
Pixel setup issues and missing parameters
Meta's Ads Data Advisor documentation lists common Pixel setup errors: duplicate Pixel code on a single page, Pixel code placed on pages that do not need it, iframes or tag managers blocked by browser settings or privacy tools, base code outside the head section, and more than one conversion event per page without a user action triggering it.
Separately, check that every Purchase event carries value and currency. Meta's standard event reference lists both as required on Purchase. Send value as a plain number and currency as INR.
Pixel issues and CRM issues are different jobs, often owned by different people. Pixel placement, duplicate base code and tag manager problems belong to whoever manages your website. Missing lead IDs, placeholder phones and late status updates belong to whoever manages your CRM and sales process. Splitting the list this way stops a week of back-and-forth about whose problem a warning is.
How to work through the list
Start with anything marked Error, then warnings on the events your campaigns optimise for, then everything else. A warning on an event no campaign uses can wait.
For each one, ask whether it applies to how the event is sent. IP and fbc warnings on CRM events are often expected; the same warnings on website Lead events usually mean a real gap. Fix one issue, wait a few days for new data, and check again. Qualimize, for example, shows every Conversions API send and its result in Settings, which makes it easier to tell a rejected event from one that simply was not sent.
Keep a short log of what you changed and when. Diagnostics are based on recent data, so a fix made today may take several days to clear a warning, and without a log it is easy to make a second change before the first has shown its effect.
Example: a Hyderabad dental clinic sees a Phone placeholder warning on its website Lead event. The cause is a form plugin that fills 0000000000 when the phone field is left blank. The fix is to send no phone at all for those leads. The clinic notes the date, checks again a week later, and only then moves to the next item on the list.
Comparison tables
Events Manager issues from Meta's documentation, and what to do
| Issue (Meta's wording) | What it means | Applies to CRM events? | Fix |
|---|---|---|---|
| Server sending mismatched IP addresses | Server IPs do not match the Pixel's | Rarely | Send the customer's browser IP, not your server's |
| Update your IPv4 IP addresses to IPv6 IP addresses | Server sends IPv4; Meta recommends IPv6 | Rarely | Capture the visitor's IPv6 address where they have one |
| Empty IP / Relay IP | No customer IP, or a privacy relay IP | Expected for CRM events | Send real client IP on website events |
| FBC coverage | Too few events carry fbc | Low for Instant Form leads (lead ID used) | Capture fbclid on website forms |
| Email placeholder / Phone placeholder | Many events share one fake value | Yes | Send nothing instead of a placeholder |
| Deduplication rate too low | Browser and server copies not matched | Only if also sent from the browser | Matching event_id and event name on both |
Event statuses in Events Manager
| Status | Meta's meaning (paraphrased) | Urgency |
|---|---|---|
| Active | Event is being sent correctly | None |
| Inactive | Event is not currently sending data | Check the CRM first: may be no conversions |
| Warning | Issues that may affect performance | Review weekly |
| Error | Critical configuration issue that requires action | Fix first |
| Auto-detected | Detected from website activity without extra code | Review whether you want it |
FAQ
What does the Warning status mean in Meta Events Manager?
Meta says Warning means there are one or more issues with your event signal that may affect performance. The event is still arriving. Open it to see which issue is flagged, and fix the ones on events your campaigns optimise for first.
What does 'Server sending mismatched IP addresses' mean?
Meta says your server is sending client IP addresses that do not match those from the Meta Pixel. Usually the server is sending its own IP instead of the visitor's. Send the client_ip_address captured from the visitor's browser request.
Why does Events Manager say my events are not deduplicated?
Meta only deduplicates a browser and server event when the event_id and event name match, within 48 hours. Check that both sources send the same event_id for the same action and the same event name, with the same capitalisation.
Why are my Conversions API events missing from Events Manager with no warning?
Meta rejects some events outright: any request containing an event older than 7 days, events with an invalid lead_id, and whole batches with an error in them. Rejected events never appear, so check the API responses in your sending tool.
Should I worry about IP and fbc warnings on CRM events?
Usually not. A status change made by a sales rep has no customer browser behind it, so there is no customer IP or click cookie to send. For Instant Form leads, the Meta lead ID does the matching. These warnings matter more for website events.
Where does Qualimize fit?
Qualimize sends CRM stage events server-side with the Meta lead ID, hashed email, phone and name, fbc and fbp when it has them, and a stable event ID, and retries failed sends automatically. Every send and its result is visible in Settings, so you can check whether an event left Qualimize before digging into Events Manager. It does not fix website Pixel issues; those are on your website setup.
Key takeaways
- Error means fix now; Warning means an issue that may affect performance; Inactive on a CRM event may just mean no conversions.
- IP and fbc warnings mostly concern website events, not CRM stage events.
- Placeholder emails and phones hurt matching; send nothing instead.
- Deduplication needs matching event_id and event name within 48 hours.
- Some failures never show as warnings: stale events, invalid lead IDs and bad batches are rejected outright.