What an Event Match Quality score of 5.4 is actually telling your ad account

If your Meta campaigns are generating leads but the cost keeps climbing and the quality keeps dropping, there's a specific number worth looking at inside Events Manager. It's called Event Match Quality, and a score of 5.4 out of 10 is not a passing grade. It's a signal that Meta's algorithm is flying partially blind on your behalf, and you're paying for it in every auction.

What Event Match Quality actually measures

Every time someone submits a lead form or lands on a thank-you page, Meta fires a conversion event. That event gets matched against Meta's user database to figure out who converted. The stronger the match, the more data Meta has to optimize the campaign toward people who actually convert.

Event Match Quality (EMQ) scores that match attempt. It's scored 0 to 10. A score of 5.4 means roughly half the conversion signals Meta receives can't be confidently matched to a real Facebook or Instagram profile. The algorithm knows a lead came in. It doesn't know much about who that person actually is.

When Meta can't match a conversion event cleanly, it loses the ability to find more people like that person. The lookalike modeling degrades. The cost-per-lead climbs over time. And the leads that do come in start skewing toward whoever Meta can still reach easily, which isn't necessarily the person who'd actually book your service.

Why 5.4 is specifically a problem for local service businesses

A national e-commerce brand running hundreds of transactions per day can survive a mediocre EMQ score. Volume compensates for imprecision. A roofing company running $2,000 per month in ad spend cannot absorb that same inefficiency. Every conversion event carries more weight when you're generating 30 to 80 leads per month rather than 3,000.

Low EMQ means the algorithm is learning slower. Learning slower means it takes longer to exit the learning phase. While a campaign is in the learning phase, Meta deliberately limits delivery and holds back optimization. For a local service business, that can mean two to three weeks of elevated cost-per-lead on a campaign that could have stabilized in the first week with better signal.

There's also an attribution problem. If Meta can't match conversions reliably, the results visible in Ads Manager undercount real conversions. That means whoever is reviewing the account sees a worse return than what's actually happening and makes decisions accordingly, usually pulling budget or changing targeting when the real fix is upstream in the data pipeline.

The Conversions API gap most agencies leave open

Meta has two ways to receive conversion data: the browser-based Pixel, and the Conversions API (CAPI), which sends conversion data directly from the server rather than relying on the user's browser.

Browser-based Pixel alone is the default setup most agencies leave in place. The problem is that browsers increasingly block third-party tracking. Safari blocks it by default. Firefox blocks it. Ad blockers block it. iOS privacy changes reduced signal reliability further. The result: a significant portion of real conversions never reach Meta at all, and the ones that do arrive with incomplete customer information, which tanks the match rate.

CAPI was built to solve this. It sends a server-side event with richer customer data, including email, phone number, name, and other identifiers that improve the match. When CAPI runs alongside the Pixel (a configuration Meta calls "redundancy"), the match rate improves materially. EMQ scores of 7.5 to 8.5 are achievable for lead generation campaigns. Below 7 on a CAPI-enabled account is a configuration problem. Below 6 without CAPI is just the Pixel doing what the Pixel does now.

GoHighLevel (GHL) is the CRM most home service agencies use to receive and route leads. GHL has a native CAPI integration, but it requires configuration: you have to connect the GHL funnel or landing page to the Meta Conversions API through GHL's workflow settings, map the right event parameters, and ensure the access token and Pixel ID are correctly linked. It is not automatic on a new account. Most agencies that set up GHL for a client connect the Pixel and stop there. The CAPI layer gets skipped, not because it's hard, but because it requires an extra setup step that never made it into the standard onboarding checklist.

The downstream effect: campaigns that run for months on an incomplete data pipeline, generating leads the agency can see in GHL but Meta can only partially attribute, degrading the algorithm's ability to optimize, and producing rising costs that get blamed on "the market" or "the niche."

What to actually look for and what to ask

If you're evaluating whether to run Meta ads again after a bad experience, EMQ is one concrete, verifiable number you can ask about before committing to anything.

Here's where to find it: inside Meta Business Suite, go to Events Manager, select your Pixel, and look at the Event Match Quality column for your lead event. If an agency is managing your account, you can request read access to your own Events Manager. You own the account. You're entitled to see it.

Ask specifically: Is CAPI connected through GHL, or are you running Pixel only? If they can't answer that clearly, or if they say "we have the Pixel installed" without mentioning CAPI, the data pipeline is probably incomplete.

A well-configured setup for a GHL-based lead gen campaign should show an EMQ score above 7, deduplication enabled (so the same conversion doesn't get counted from both browser and server), and the correct event tied to lead submission rather than a page view or session start.

The Safe Step campaign ASN ran, which produced 247 leads at $11 per lead on $2,800 in total spend, ran with proper CAPI configuration through GHL. That cost-per-lead is not achievable at that volume on a misconfigured account where Meta is working from partial data. The signal quality is part of the result, not separate from it.

What this means if you're deciding whether to try again

If your last agency's campaigns started reasonably and then deteriorated, tracking configuration is one of the first places to investigate. A rising cost-per-lead on a campaign that launched fine is often a learning-phase or match-quality problem, not a targeting problem or a creative problem. Changing audiences or refreshing ads won't fix a broken data pipeline.

Before starting any new campaign, confirm that CAPI is being configured alongside the Pixel, that the GHL integration is set up at the workflow level rather than just the page level, and that someone can show you the EMQ score after the first week of live data. Those aren't advanced requests. They're the baseline of a properly built account. If you'd like to see how ASN sets this up before you commit to anything, the contact page is the right starting point.