About Tracking

Ad Platform Tracking

Meta Pixel + CAPI TikTok CAPI LinkedIn CAPI Snapchat CAPI Pinterest CAPI Quora Pixel Bing + UET Tag

Google Ecosystem

Google Ads Tracking GA4 Setup & Audit Google Tag Manager

Advanced Solutions

Server-Side Tracking Looker Studio Offline Conversion
Case Studies Blog Free Checklist Book Free Audit →

Most advertisers install their Meta Pixel and then never look at the data behind it. Meta Events Manager is where all that data lives — and it is also where pixel problems hide. If your conversions are under-reporting, your Event Match Quality is low, or your campaigns are not performing as expected, Events Manager almost always tells you why.

This guide covers every section of Events Manager, what each tab tells you, how to use the Test Events tool to verify your setup, and how to interpret and fix the most common warnings and errors.

How to Access Meta Events Manager

Go to business.facebook.com and log in. In the left sidebar, click Events Manager under the Data Sources section. If you manage multiple pixels across different ad accounts, make sure the correct Business Manager is selected in the top left dropdown before navigating to Events Manager.

On the Events Manager home screen, you will see all pixels and offline event sets connected to your Business Manager. Click on your pixel to open the detail view with all its tabs.

The Overview Tab: Reading Your Pixel Health at a Glance

The Overview tab is your pixel’s dashboard. It shows every event your pixel has received in the selected time range, with key metrics for each:

ColumnWhat It ShowsWhat to Look For
Event nameThe standard event or custom event nameAll expected events are present
ReceivedTotal event count in the periodMatches your expected volume
BrowserEvents received via browser pixelHigh if pixel is installed correctly
ServerEvents received via Conversions APIShould match browser count if using CAPI
DeduplicatedEvents removed because both browser and server sent the same event_idShould be non-zero if running both pixel and CAPI
StatusActive, inactive, or warningAll key events should be Active

The most important metric to check first: compare your Purchase event count against your actual order count for the same period. If Events Manager shows 200 purchases but your order system shows 350, you have a gap — conversions are being missed. If it shows 600 purchases but you had 350 orders, you have duplicate events.

The Diagnostics Tab: Finding and Fixing Warnings

The Diagnostics tab shows active warnings and errors for your pixel. Each warning includes a severity level, a description of the issue, and recommendations for fixing it. Common diagnostics you will encounter:

“No activity in the last 24 hours”

This appears when your pixel has not fired any events recently. Causes include: a broken pixel installation after a site update, a theme change that removed the pixel code, or a GTM container that was accidentally paused. Check Meta Pixel Helper on your homepage to confirm the pixel is still firing.

“Redundant pixels detected”

Two or more pixels are firing on the same page. This inflates your event counts significantly. Identify which pixel IDs are firing using Pixel Helper and determine which one to keep. Remove the duplicate either from your website code, your GTM container, or your plugin settings.

“Missing parameters”

Your event is firing but not sending required or recommended parameters. For Purchase events, missing value and currency prevents revenue reporting and disables ROAS-based bidding. Click the diagnostic to see which parameters are missing and on which events.

“Low event match quality”

Your customer data (email, phone, name) is not matching Meta profiles effectively. This reduces the quality of your lookalike audiences and retargeting. See the Match Quality tab for the specific score and recommendations for improvement.

The Test Events Tool: Verifying Your Setup in Real Time

The Test Events tool is the most useful feature in Events Manager for diagnosing and verifying your pixel setup. It shows every event your pixel fires in real time — including full parameter details — as you navigate your own website.

How to use it:

  1. In Events Manager, click Test Events in the left sidebar
  2. Enter your website URL in the “Test Browser Events” section and click Open Website
  3. Your site opens in a new tab; Events Manager begins listening for incoming events
  4. Navigate through your site — add a product to cart, start checkout, complete a test purchase using a test payment
  5. Watch events appear in real time in the Events Manager panel

For each event that appears, click on it to expand the full parameter list. Verify:

The Test Events tool also shows server-side CAPI events in a separate panel, allowing you to verify that both browser and server events are arriving with matching event_ids.

The Match Quality Tab: Understanding Your EMQ Score

Event Match Quality (EMQ) measures how effectively Meta can match your pixel events to people in Meta’s system using the customer data you provide. The score ranges from 0 to 10.

Click on any event in the Overview tab and then click Match Quality to see its score and a breakdown of which customer parameters you are sending. Each parameter contributes to the score:

ParameterImpact on EMQHow to Send It
Email (em)HighSHA-256 hashed lowercase email
Phone (ph)HighSHA-256 hashed, E.164 format
First Name (fn)MediumSHA-256 hashed lowercase
Last Name (ln)MediumSHA-256 hashed lowercase
City (ct)MediumSHA-256 hashed lowercase
Postcode / ZIP (zp)MediumSHA-256 hashed
Country (country)LowISO 3166-1 alpha-2 country code
Gender (ge)LowSHA-256 hashed: “m” or “f”
Date of birth (db)LowSHA-256 hashed YYYYMMDD format

For ecommerce stores, collecting and sending email and phone with every Purchase event is the fastest way to improve Event Match Quality. Both parameters are available at checkout — your pixel or Conversions API should hash and pass them server-side to avoid any privacy issues with browser-side data handling.

The Aggregated Event Measurement Tab

This tab manages your 8-event configuration for iOS users. If your domain is not yet verified or you have not configured your event priority, you will see a prompt to complete setup here. Follow the steps in this tab to verify your domain and set your event priority order — this is critical for accurate iOS conversion reporting.

Changes to your AEM configuration take up to 72 hours to propagate. Avoid making changes during active campaigns to prevent disrupting the learning phase.

Reading the Event Detail View

Click on any event in the Overview tab to open its detail view. This shows:

The Parameters tab is particularly useful for spotting incomplete implementations. If your Purchase event sends value in only 80% of events, that means 20% of your purchases are not reporting any revenue — those 20% are invisible to Meta’s bidding algorithm.

Using Events Manager as Part of Your Routine

Events Manager should be part of your regular tracking audit routine. A monthly check takes 10 minutes and catches problems before they compound:

  1. Check the Diagnostics tab for any active warnings
  2. Compare Purchase event count to your actual order count for the last 30 days
  3. Check the Match Quality score on your Purchase event — aim for 7 or higher
  4. Verify the Deduplicated column shows non-zero activity if you are running CAPI
  5. Run a Test Events session after any site changes to confirm nothing broke

Related Articles

📋 Not sure where to start? Use our Free Tracking Audit Checklist to find out where your setup is losing data.

Book a free tracking audit → We’ll review your setup and tell you exactly what to fix.

Leave a Reply

Your email address will not be published. Required fields are marked *