DATALYR

Shopify Event Match Quality: how to improve it

What Meta's Event Match Quality score measures for Shopify purchases, which fields raise it (email, phone, fbc, fbp, IP, user agent) and how to check them.

By DATALYR · · 3 min read

Contents

What Event Match Quality measures

Event Match Quality is Meta's score, out of 10, for how well the customer information on a server event can match it to a Meta account. Higher match quality produces better results, because Meta can use only matched events for ad attribution and delivery optimisation.

On Shopify, the score depends on what reaches Meta with each purchase: hashed email and phone, the fbc click ID and fbp browser ID, IP address and user agent. Meta shows the score in Events Manager for website events.

The fields that move the score

Meta says sending additional customer information parameters may help increase Event Match Quality, and names email, IP address, name and phone among high-quality ones. client_user_agent is required for website events sent through the Conversions API.

fbc and fbp are sent unhashed. fbc has the form fb.1.creation_time.fbclid and can be built from the fbclid in the landing URL; fbp lives in the _fbp cookie. Meta advises refreshing these values regularly when you send them, rather than reusing a stale one.

  • em and ph: hashed email and phone. Usually the biggest gain on purchases.
  • fbc: the click ID. Ties the purchase to the ad click itself.
  • fbp: the browser ID. Helps when the buyer has no click ID.
  • client_user_agent: required for website events. client_ip_address: sent unhashed and helps matching.
  • external_id: your own stable customer or visitor ID, sent hashed.

Where Shopify stores lose match data

Purchases usually have email, since checkout collects it. Upper-funnel events often do not: a product view or add to cart from an anonymous visitor carries only browser IDs. Judge each event against what it could carry, not against the purchase.

The click ID is the field most often lost. It arrives in the landing URL, then has to survive to the purchase, sometimes days later and sometimes across the in-app browser and Safari. If only fbp reaches Meta, with no email or phone, match quality stays low.

Illustrative example. Of 200 purchases sent in a week, 190 carry a hashed email (95%), 120 carry a phone (60%) and 150 carry fbc. Of those 200, 160 came from visitors who clicked a Meta ad, so fbc coverage on ad visitors is 150 of 160, or 93.75%. The 10 ad visitors without fbc are where the click ID was lost between click and sale.

Coverage on 200 purchases (illustrative)

Email

190 of 200

95% of all purchases.

Phone

120 of 200

60%; ask for it at checkout if you can.

Click ID (fbc)

150 of 160

93.75% of purchases from Meta ad visitors.

Browser ID (fbp)

170 of 200

85%; absent when the buyer declined consent.

Arithmetic example. Measure click ID coverage over ad visitors only; organic buyers never had one.

Raise it without collecting more than needed

Start with what you already have. Most stores collect email and phone at checkout; make sure both are sent hashed with every purchase. Then fix the click ID path, so the fbclid captured at landing reaches the order.

Do not chase a higher score by sending fields you should not. Consent applies: an event from a visitor who declined marketing should carry no user-level identifiers. For health and wellness stores, keep sensitive details out of what you send.

  • Send hashed email and phone with every purchase.
  • Carry the fbclid from the landing page to the order, with its original arrival time.
  • Send IP address and user agent from the buyer's session, not from your server.
  • Keep one purchase sender per pixel so matched and unmatched duplicates don't mix.

How DATALYR fills the match fields

On Shopify, DATALYR's App Embed writes the visitor ID, the _fbc and _fbp cookies, and the raw fbclid with its arrival time into the cart, and Shopify carries them onto the order. When the Meta conversion is sent, DATALYR builds fbc from the moment the fbclid first arrived and adds hashed email, phone, name and location from the event and the stored profile, plus IP address and user agent.

The Health page in DATALYR has a Match quality tab for each ad platform and origin. It shows, per event type, how many delivered events carried an ad click ID, an email, a browser ID and device info. Click ID coverage is measured only over visitors who came from that platform's ads, so a gap there means the ID was lost between the click and the sale.

Related articles.

See what really drives revenue.

Real-time attribution, analytics and conversions for every channel, campaign and ad, ready for your team and your agents.

Get started