1. Home
  2. Meta Hub
  3. Tracking & Operations
  4. Troubleshooting the Meta Pixel and Conversions API in Events Manager: Test Events, Diagnostics and Common Errors
Tracking & Operations · 8 min read

Troubleshooting the Meta Pixel and Conversions API in Events Manager: Test Events, Diagnostics and Common Errors

By the Power Ads teamUpdated 2026-11-20Checked against 16 sources1,581 words

Purchases in Ads Manager don't match your store, a Diagnostics badge has turned red, or server events never arrive. Meta gives you four tools to find out why: the Test events tool, the Diagnostics tab, the Meta Ads Data Advisor extension (formerly the Meta Pixel Helper) and the event activity charts in Events Manager. This guide explains what each shows, the errors Meta documents with their fixes, and a debugging order. Each rule comes from Meta's Help Center or developer documentation.

The Test events tool: browser and server

Meta's Help Center says the Test events tool lets you verify that events are configured and received, detect unusual activity and see which web events were processed and which were deduplicated. To open it, go to Events Manager, click Data sources, select your pixel or dataset and click Test events. The same row of tabs holds Overview, Diagnostics, History, which lists changes to your pixel or Conversions API and who made them, and Settings.

For browser events, enter your website URL in the browser events section and click Open website, then use the site as a customer would. Meta notes that website activity is only recorded while the Test events page is open. Filters can show standard, custom or automatically logged events, with URLs, parameters and active errors.

For server events, the tool generates a test code. Meta's developer documentation says to send it as the test_event_code parameter in your Conversions API request to see the events appear in the Test events window. The Help Center says that if test events don't show up, check that your payload is structured correctly, using the Payload Helper tool. Test information stays in the tool for 24 hours or until you click Clear activity.

If nothing appears within one minute, Meta's web troubleshooting steps are to check your connection, disable ad blockers, refresh the site and interact again, or try another browser. Meta also says data can take 30 minutes or more to appear in analytics after you set up an event, so use Test events rather than waiting on the Overview chart.

The Diagnostics tab and the issue types Meta lists

Meta says the Diagnostics tab helps you find and resolve issues with web, app and offline events, and that each issue includes a description and steps to fix it. Critical issues have a red icon and cover high-priority changes, such as platform updates, privacy regulations and Meta Privacy Policy violations. Warnings have a yellow icon and are lower priority, for example a value parameter that may be set up incorrectly or a pixel that recently started sending events from new domains.

Issues sit in three tabs. Active holds issues detected in the last 24 hours that you haven't resolved or ignored. If you don't act on one within three days of first detection, it moves to Previously detected and Meta removes its fix instructions, so work through Active promptly. Ignored holds issues you've chosen to ignore. For web and app issues, Ignore and Mark as resolved apply to everyone in the business portfolio.

Power AdsUnlimited Meta agency ad accounts on our corporate cards, with 24/7 support on Telegram and WhatsApp, for teams spending roughly $100,000+/mo. 4% per top-up, no setup fee. Apply for access →

Common errors and Meta's documented fixes

Meta publishes a list of pixel errors and warnings that appear in Diagnostics. The ones advertisers meet most often, with Meta's fixes:

  • Missing or invalid currency: the currency code must be a standard three-letter ISO code, such as USD or GBP. Meta says code snippets must contain both a value and a currency parameter.
  • Missing or invalid price in value: the value must be a decimal number greater than or equal to zero, with no letters, special characters, currency symbols or commas.
  • Mismatches in currency or value: the pixel and Conversions API send different values for the same event. Meta warns that if the true value isn't in the event it keeps after deduplication, ROAS calculations can be inaccurate.
  • Event name mismatch: events are case-sensitive, so purchase is not Purchase.
  • Multiple events on an action: the pixel fires several events for one click or page load. Remove extra event snippets, and keep only the pixel base code, which includes PageView, in the site header.
  • Redundant purchase events: four or more purchase events for one purchase. Meta says this can over-report purchases and may hurt delivery of conversion and catalog sales ads; put purchase code only on the confirmation page or a specific inline action.
  • Duplicate events detected: an event is logged both in your code and as an automatic event. Meta points you to turning off automatic events; the event still comes through from your code.
  • New domain sending data: the pixel started sending from a domain it hadn't used before. Meta points you to the traffic permissions allow list or block list.
  • Event parameters blocked: parameters may contain information that goes against the Meta Business Tools Terms. Review and fix what you send, then request unblocking in Events Manager. If it keeps happening, Meta may restrict the pixel to a core setup, shown as Your data is restricted.

Duplicates, domains and low match quality

Duplicate counts often come from sending the same event through the pixel and the Conversions API without matching keys. Meta deduplicates when event_name matches and event_id is identical in both, or alternatively when event_name and either external_id or fbp match. Its troubleshooting steps: confirm the same event_id is used on both sides, check in Test events which events were received, deduplicated or dropped, and make sure event_name and event_id are formatted identically. Our deduplication guide covers the setup.

Domain problems come in two forms. Your pixel ID is public, so Meta says someone else can put it on their site, and partner integrations, iframes or redirects can make your own events show an unfamiliar domain; Meta recommends a traffic permissions allow list over a block list. Separately, a domain can be blocked for violating Meta's terms and policies, and events sent while it's blocked can't be used for advertising or measurement even after it's unblocked. Blocked domains show in Diagnostics, where pixel admins can request a review.

Meta's event match quality score covers website events sent through the Conversions API. Meta scores event match quality from 0 to 10, based on the customer information you send and the share of events matched to Meta accounts, using the last 48 hours of data. Email and click ID are the high-priority parameters. Check the Event matching tab in the event's server details, and see our event match quality guide for what to send.

Meta Ads Data Advisor (formerly Meta Pixel Helper) and the event charts

Meta's developer documentation says the Meta Pixel Helper now updates automatically to Meta Ads Data Advisor. It runs in Chrome or Edge, basic detection works while logged out, and your ad blocker must be off. A pixel shows Active, Warning or Inactive; events can also show Error, for critical issues such as blocked parameters or duplicate events. A pixel can be Active while its events carry warnings, so click into it. No badge on the icon means no pixel was found.

Data Advisor has blind spots. Meta says custom conversions, some advanced event types and some button-click events may not appear even though they're still sent, and points you to the Test events tool for in-depth troubleshooting. Our pixel events guide explains how those event types differ.

For trends, use the Overview tab: hover over the event activity chart for a breakdown, or select an event for its own chart. For website events sent through the Conversions API, View details opens tabs for event overview, coverage, matching, deduplication and data freshness. Meta suggests aiming for a 75% event coverage ratio and sending events as close to real time as possible.

A step-by-step debugging checklist

This order is practitioner advice, not a Meta procedure. Each step uses a tool or rule Meta documents.

  • Start with Diagnostics. Fix red critical issues first, and act on Active issues before they move to Previously detected and lose their instructions.
  • Check History for changes made around the date the problem began.
  • Load the page with Meta Ads Data Advisor, ad blocker off. Confirm one pixel, PageView on every page and each standard event only on the pages where it belongs.
  • Run a browser test in Test events, keeping the tab open, and complete a real path through to purchase or lead. Look for lowercase event names, missing value or currency, and more than one event per action.
  • Send a server test with test_event_code. If nothing arrives, check the payload with the Payload Helper, and keep event_time within 7 days: Meta returns an error for the whole request and processes no events if any event_time is older.
  • Review traffic permissions and blocked-domain notices, then check match quality, coverage and data freshness in the server event details.
  • With both sources running, check in Test events which events were deduplicated, and compare value and currency between the pixel and server copies.
  • Remove test_event_code from production and clear the test activity. If you're rebuilding the server side, start from our Conversions API setup guide.

Common mistakes to avoid

These come straight from Meta's documentation. Power Ads supplies Meta agency ad accounts and doesn't set up pixels or the Conversions API, so these checks stay with you.

  • Leaving test_event_code in production. Meta says the field should be used only for testing and must be removed from production payloads. Events sent with it are not dropped: they flow into Events Manager and are used for targeting and ads measurement.
  • Assuming Clear activity deletes test data. Meta says cleared activity still appears in Events Manager, Ads Reporting and Audience Creation results.
  • Putting event code in the site header template. Meta says the only Meta code that belongs in the header is the pixel base code, and to remove other event code from it.

Key takeaways

  • Diagnostics flags issues as red critical or yellow warnings; act on Active issues within three days or the fix instructions are removed.
  • Browser tests only record while the Test events page is open; server tests need the test_event_code parameter in the request.
  • Remove test_event_code before production. Meta says events sent with it are not dropped and are used for targeting and measurement.
  • Event names are case-sensitive, value needs a decimal number and currency a three-letter ISO code.
  • Meta Ads Data Advisor replaced the Pixel Helper but can miss custom conversions and some button clicks; confirm in Test events.

FAQ

Why don't my events show up in the Test events tool?

For browser events, activity is only recorded while the Test events page is open; if nothing appears within a minute, Meta suggests disabling ad blockers, refreshing or trying another browser. For server events, the request must include the tool's test_event_code, and Meta suggests checking the payload with the Payload Helper.

Do I need to remove test_event_code after testing?

Yes. Meta's developer documentation says the field is for testing only and must be removed from production payloads. Events sent with it are not dropped and are used for targeting and ads measurement.

What does Event name mismatch mean in Diagnostics?

Meta shows it when an event is similar to, but not identical to, a standard event. Events are case-sensitive, so purchase must be written Purchase. Use See affected URLs to find the pages and correct the event code.

Why is my pixel receiving events from a domain I don't own?

Meta says your pixel ID is public, so someone else can add it to their site, and partner integrations, iframes or redirects can also show an unfamiliar domain. A traffic permissions allow list limits events to approved domains.

Why do Events Manager and Ads Manager show different numbers?

Meta notes that event counts may differ between the data sources page in Events Manager, the custom conversions page and Ads Manager. A gap alone isn't an error; check Diagnostics and Test events before changing your setup.

Need agency ad accounts?Unlimited Meta agency accounts on our corporate cards, shared to your Business Manager through partner access. 4% per top-up, no setup fee, unused balance refunded within 24 hours (business days), free replacements, 24/7 on Telegram and WhatsApp.
@power_ads_hqGet the next one in Telegram.Meta policy shifts, spend-limit fixes and scaling notes from the Power Ads team. Join 3,000+ subscribers. Free, read-only, one tap to leave.Join channel

Sources

Power Ads background
By application only

We don't talk. We solve.

Unlimited Meta agency ad accounts on our corporate cards for teams spending roughly $100,000+ a month. 4% per top-up, no setup fee, 24/7 on Telegram and WhatsApp.

Telegram support · 24/7
TelegramWhatsAppApply