Skip to content

Event Match Quality

Understand Event Match Quality, the Meta score from 1 to 10 that rates how much customer data your Conversion API events include. Learn why EMQ measures parameter completeness and formatting rather than data accuracy, and how to check your score in Meta Events Manager.

This page explains what the Event Match Quality score measures, what it does not measure, and how to check it. Two things to keep in mind throughout: EMQ rates how complete and well formatted your event data is, not whether it is accurate, and real customer data matters more than a perfect score.

Event Match Quality (EMQ) is Facebook’s scoring system measuring how well your conversion events match actual Facebook users. Scores range from 1 to 10, with higher scores indicating better attribution potential. EMQ applies to events sent through the Conversion API and Conversion API for CRM. See Meta Pixel vs CAPI vs CAPI for CRM to understand how each tracking method contributes identifiers that affect your score.

Key Points:

  • EMQ depends on customer data parameters (email, phone, IP address)
  • Higher scores help Meta attribute conversions faster and to more of the right users
  • Scores appear in Meta Events Manager for each conversion event

How Facebook Calculates Event Match Quality

Section titled “How Facebook Calculates Event Match Quality”

Facebook determines your EMQ score using two main factors:

What it measures: Whether you send customer information like email, phone, IP address

Impact: More parameters typically yield higher scores

Common parameters: email, phone, IP address, external ID, click ID (fbc)

What it measures: Whether data follows proper formatting rules

Impact: Correct formatting improves scores but doesn’t verify accuracy

Examples: Phone numbers in international format (+1-555-123-4567), valid email structure

Important: Facebook accepts fake@fake.com or 555-555-5555 if properly formatted

What EMQ checks:

  • Format correctness (is email properly formatted?)
  • Parameter presence (are required fields sent?)
  • Technical compliance (does data meet formatting standards?)

What EMQ doesn’t check:

  • Data accuracy (does email belong to the actual customer?)
  • Real user matching (fake but well-formatted data scores 10/10)
  • Attribution effectiveness (high scores don’t guarantee good attribution)

Store A: EMQ Score 9.2/10

  • Sends all parameters in perfect format
  • Phone: +1-555-555-5555 (fake but formatted correctly)
  • Email: test@test.com (fake but valid format)
  • IP: Real address but unrelated to actual user
  • Result: Perfect score, poor attribution

Store B: EMQ Score 8.1/10

  • Missing some parameters
  • Phone: Real customer phones in correct format
  • Email: Actual customer emails
  • IP: Real user IPs
  • Result: Lower score, excellent attribution

8.5-10.0: Strong Parameter Presence

  • Most parameters are being sent in the correct format
  • Your integration is passing complete customer data

7.0-8.4: Good Foundation

  • Core parameters present, with some formatting or parameter gaps left to close

5.0-6.9: Parameter Gaps

  • Key customer information parameters are missing or badly formatted

Below 5.0: Limited Data

  • Major parameter gaps; check whether your conversion source is collecting and syncing customer data at all

For realistic EMQ score ranges by event type, see the benchmark table in EMQ parameters.

  1. Go to Meta Events Manager
  2. Click on “Datasets” in the left sidebar
  3. Select your dataset (Meta Pixel) from the list
  4. Click on individual events to see their EMQ scores
  5. Review the “Event Quality” tab for detailed insights

For businesses managing multiple datasets or requiring programmatic access, Facebook provides the Dataset Quality API. This requires technical implementation and appropriate permissions.

AnyTrack offers a free EMQ checker at match.anytrack.io that analyzes your Event Match Quality and benchmarks it against similar businesses.

Before treating an EMQ score as a problem, check whether it fits one of these patterns:

  • High score but poor attribution. Placeholder data (test@example.com, default phone numbers) or server IPs sent instead of customer IPs keep the score high while breaking real matching. Accuracy beats completeness.
  • Low scores on top-of-funnel events. PageView, ViewContent, and AddToCart fire before the visitor shares any personal information, so lower scores there are normal and expected.
  • Purchase or Lead events below 6.0, or a sudden drop. Check that your conversion source integration is active and syncing customer data, especially after a platform or integration change.
  • Fluctuating or conflicting scores. Duplicate events from multiple tools sending to the same dataset can distort both the score and attribution.

For the full breakdown of which situations to ignore and which to investigate, see When to Investigate Your EMQ Score. AnyTrack extracts customer data from your conversion source, formats and hashes it to Meta’s requirements, and sends it with each event, as documented in the Facebook Conversion API guide.