There is a number buried three clicks deep in Meta's Events Manager. It looks like a school grade, scored out of ten. Most advertisers have never opened the page it lives on.
It is worth more to your return on ad spend than the last four creative tests combined.
It is called Event Match Quality, and if yours is below 7 you are paying a tax on every single conversion you buy.
Here is what it actually measures, why it got dramatically more important in the last year, and how to fix it in an afternoon.
What the score is really telling you
When someone buys from you, your website tells Meta a conversion happened. Meta then has to work out which of the billions of people it knows about that conversion belongs to.
It does that by matching the customer information you send, email, phone, name, location, browser identifiers, against its own records. Event Match Quality is a score for how confidently it can make that match.
A high score means Meta knows exactly who converted, which ad they saw, and what those people have in common. A low score means it received a conversion notification and could not confidently attach it to a human.
Now consider what that does to an optimisation system. It learns by studying the people who converted and finding more like them. Bad matching means it is learning from a blurred, partial and sometimes wrong sample.
Your creative decides who stops scrolling. Your match quality decides whether the machine ever learns why. One of those is being ignored in most accounts.
Why this got urgent
Two changes turned a technical nicety into a primary lever.
First, browser level tracking kept getting more restricted. Cookies expire faster, identifiers get stripped, and a growing share of conversions never make it back through the browser at all. What used to be automatic now has to be sent deliberately from your server.
Second, ranking systems became far more dependent on prediction. Modern delivery is essentially a forecasting engine deciding who is likely to convert before showing an ad. Forecasting engines are only as good as the training data, and your conversion signal is the training data.
So the platforms got better at using signal at exactly the moment signal got harder to collect. Accounts that solved the collection problem pulled ahead. Accounts that did not concluded the platform had stopped working.
The fix, in order of impact
One. Run the Conversions API alongside the pixel. Not instead of. Both. The pixel reports from the browser, the API reports from your server, and Meta deduplicates them. Server side reporting survives everything that breaks browser tracking, which is most things.
On mainstream platforms this is a native integration or an app install rather than a development project. Check before you scope anything.
Two. Send more customer parameters. Every additional field improves matchability. Email and phone are the heavy hitters. First name, last name, city, state, postcode and country all add. Hashed, obviously, which the integration handles for you.
The single biggest wins usually come from sending information you already have. If a customer buys with an email address and your integration is only sending browser identifiers, you are withholding the one field that would have matched them.
Three. Fix deduplication. If the same conversion arrives twice with different identifiers, you get inflated numbers and degraded matching. Confirm your event IDs are consistent across both channels.
Four. Clean the data at the source. Phone numbers stored in five different formats, email fields with spaces, test orders that never got excluded. Rubbish in, low score out.
What good looks like
Aim for above 7 on your primary conversion event. Above 8 is strong. Anything below 6 means the system is largely guessing.
Check the score per event, not just overall. It is common to see a healthy score on page views and a poor one on purchases, which is precisely backwards, because the purchase event is the one that trains delivery.
And check it after every website change. Match quality quietly degrades when a form gets rebuilt, a checkout gets updated or a plugin gets replaced. Diarise a monthly look.
The uncomfortable comparison
Think about where your last ten hours of marketing effort went. Probably creative. Maybe audience testing. Possibly a debate about a headline.
Now consider that an account with poor match quality is running every one of those tests on corrupted data. The winner you crowned might have won because its conversions happened to be more matchable, not because it was a better ad.
That is the real cost. Not just weaker delivery, but a testing programme producing conclusions you cannot trust, which then guide the next quarter of decisions.
The privacy question, answered plainly
Owners often hesitate here, and the hesitation deserves a straight answer.
Customer information sent through the Conversions API is hashed before it leaves your systems. The platform matches hashes against hashes and never receives readable email addresses or phone numbers from you.
You still have obligations. Tell people in your privacy policy what you share and why, honour opt outs properly, and do not send data for people who asked you not to.
Do it properly and you get the performance without the exposure. Skipping it entirely does not make you more compliant, it just makes your advertising more expensive.
Do this today
Open Events Manager. Find your primary conversion event. Read the score.
If it is under 7, that number is the highest leverage thing in your marketing this month. Not the creative. Not the budget. Not the new platform someone suggested.
Fix it and the same ads, the same budget and the same offer will start performing better, because for the first time the system will actually know who is buying from you.
It is the least glamorous work in advertising and it is very close to free money.