How to Improve Meta Event Match Quality for Ecommerce

Meta's Event Match Quality score reflects how useful the eligible customer information on a server event is for matching that event to a Meta account. Improve it by sending permitted identifiers consistently, not by collecting every field available.

Audit the event before adding data

For each purchase, lead, and checkout event, record:

• the first-party source of truth
• the browser and server event IDs used for deduplication
• which customer-information fields are available
• the consent state and purpose for each field
• the formatting and hashing applied before delivery
• the Events Manager response and diagnostics

Start with the event that matters most to campaign optimization. Fixing one stable purchase event is more useful than expanding a broken schema across the funnel.

Use eligible matching parameters correctly

Meta accepts customer-information parameters such as email, phone, external ID, client IP address, user agent, browser ID, and click ID. Availability and preprocessing rules differ by field. Follow Meta's current documentation and send a field only when your policy allows it.

Common data-quality fixes include:

• normalize email casing and surrounding whitespace before hashing
• normalize phone numbers to the format Meta specifies
• capture fbp and fbc values without inventing them
• keep a stable external ID across eligible events
• pass the same event_id from browser and server when both send the event
• reject placeholder, blank, or malformed values before delivery

Hashing protects the representation in transit. It does not create consent or make an otherwise prohibited field acceptable.

Separate matching from deduplication

Event Match Quality and deduplication solve different problems. Matching helps Meta associate an event with an account. Deduplication helps Meta treat browser and server copies as one conversion. Test both:

1. Trigger a single test purchase.
2. Confirm that browser and server events use the same event name and event ID.
3. Check that Meta received both copies and deduplicated them.
4. Review parameter warnings in Events Manager.
5. Reconcile source purchases with accepted server events.

Measure the change

Use a baseline period long enough to cover normal weekday and campaign variation. Track:

• Event Match Quality by event type
• source events versus accepted server events
• duplicate and rejected events
• missing or invalid matching parameters
• delivery latency
• campaign results, with other material changes noted

Do not attribute a revenue or ROAS change to match quality alone without a controlled test. Creative, bids, audiences, seasonality, and offer changes can move the same numbers.

Read Meta's current Event Match Quality guidance, then map the approved fields in Hardal. For the wider delivery setup, see Meta Conversions API Gateway and Hardal for marketers.