Meta Ads

Catalogue Match Rate

Also called Event to catalogue match

The share of your website events that Meta could successfully tie to an item in your catalogue.

Quick facts: Catalogue Match Rate

Category
Meta Ads
Also called
Event to catalogue match
Level
Intermediate
Affects
Dynamic retargeting, product reporting, bidding signals
Where to see it
Meta Events Manager, Meta Commerce Manager diagnostics, your exported feed
In this article4
  1. What catalogue match rate measures
  2. Why catalogue match rate matters
  3. Where catalogue match rate goes wrong
  4. How to act on it

What catalogue match rate measures

Every time your site fires a product event, Meta takes the item identifier inside it and looks for that exact string in your catalogue. Catalogue match rate is how often it finds one. Events Manager reports it per event type, so you can see that product views match well while purchases do not, which is far more diagnostic than a single headline number.

It is a string comparison, nothing cleverer. The identifier either exists in the catalogue or it does not; near enough does not count. A prefix on one side, a different letter case, a variant code sent while the catalogue is built at parent level — each of these produces an unmatched event even though a human reading the two codes would call them the same product.

Why catalogue match rate matters

It is the fastest way to tell whether your commerce setup is genuinely connected. Dynamic retargeting can only show the item somebody viewed if that view was matched, so a poor rate turns personalised advertising back into generic advertising while the reporting still looks busy.

It also quietly damages bidding. Unmatched purchase events give the system less to learn from about which products and which buyers are worth pursuing, so delivery drifts towards whatever it can measure. And it distorts product-level reporting, because the sales that failed to match simply do not appear against the item that earned them.

Where catalogue match rate goes wrong

The usual culprit is not the rate itself but the assumption that a modest one is normal. It is treated as a background number, when in a healthy setup the great majority of events should match and anything well short of that points to a fixable fault.

Chasing the wrong cause wastes the most time. People re-install the pixel, rebuild the campaign or blame the audience, when the fault is an identifier mismatch that a single comparison would have exposed. The other trap is a rate that looks fine overall because product views dominate the volume, hiding a purchase event that matches badly — and purchase is the event that matters most.

How to act on it

Read it per event, not in aggregate, and start with purchase. Open Events Manager, pick an unmatched example, and note the identifier it carried. Export your catalogue feed and search for that exact string. The difference you find — a prefix, a case change, a variant code — is your answer, and it is almost always fixed in the shop platform rather than in Meta.

Then check the catalogue side for rejected or out-of-stock items, since an event cannot match a row that is not eligible. Once the content identifiers agree, watch the rate for a few days rather than expecting an instant change, and re-check it after any theme, plugin or checkout update. Making this part of a monthly review is cheaper than discovering a broken feed after a season of spend on catalogue advertising.

Do and do not

Do

  • Read the rate per event and start with purchase
  • Compare one unmatched identifier against the exported feed
  • Recheck after theme, plugin or checkout changes

Do not

  • Accept a weak match rate as normal
  • Reinstall the pixel before comparing identifiers
  • Judge health from the aggregate number alone

Questions people ask about this

What is a good catalogue match rate?

Aim for the great majority of events matching, since there is no technical reason for a correctly configured shop to miss many. A small shortfall is normal, caused by discontinued items or products removed from the catalogue while old browsing data still arrives. A large shortfall is a configuration fault rather than a benchmark to accept, and it is usually a single identifier mismatch.

Why does my purchase event match worse than my product views?

Because they are often built by different parts of the shop. Product pages typically read the item straight from the template, while the order confirmation reads from a completed order object that may expose a different field, such as a line item reference rather than the stock code. Test a real order and compare the identifier it sends against your feed.

Does a low match rate affect my ad delivery or only reporting?

Both. Reporting loses product-level accuracy, and delivery loses the signals that dynamic retargeting depends on, so the system falls back to showing less relevant items. Bidding also learns from fewer matched purchases. Fixing the identifiers usually improves results without any change to budget, audience or creative.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.