Match Strength vs Clarity Score: Delivery vs Identity for Shopify

Clarity Score tells you whether your Shopify purchase Pulses reached the advertising Channel, Match Strength tells you whether Meta could match those arrivals to a real user. When Clarity Score is low, Meta never received the purchase. When Match Strength is low, Meta received the purchase but could not connect it to the person who bought. Both numbers appear on the Overview, both affect performance, and fixing the wrong one first wastes weeks. This article explains the difference, why merchants confuse the two, and the order to fix them, with the Shopify signal recovery guide as the pillar for diagnosis and the companion reads on Clarity Score for Shopify merchants and Match Strength on Meta Ads for deeper dives on each metric.

Meta still labels the identity side as Event Match Quality in Events Manager, but signal layer tools surface it as Match Strength to make the contrast with Clarity Score explicit. Delivery health and identity health fail for different reasons, recover through different actions, and show up differently in the Stream. Treating them as one number is the most common reason Shopify merchants misdiagnose why reported purchases and Shopify orders no longer line up.

The Quick Answer

Clarity Score measures delivery: the percentage of purchase Pulses your store created that a Channel confirmed receiving. Match Strength measures identity: of the Pulses that arrived, how many Meta could match to a Facebook or Instagram account. Fix Clarity Score first, because a Pulse that never arrives cannot be matched at all. Once delivery sits near one hundred percent for a full week, fix Match Strength by completing the identity fields inside each Pulse. The order matters because identity work on undelivered Pulses never reaches the platform.

What Clarity Score Measures

Clarity Score is the delivery health percentage for one Channel at a time. For every completed Shopify order, a signal layer creates one Pulse, the structured purchase record that carries order value, currency, product details, and customer identity fields. The Pulse is delivered to each connected Channel, in Hawklists the two live Channels are Meta CAPI and Google Ads. Each platform responds with a confirmation or an error. Clarity Score for that Channel over a window is delivered Pulses divided by total Pulses attempted.

Two facts matter for reading it correctly. First, Clarity Score measures arrival, not quality. A Pulse that arrives with thin identity still counts as delivered, because the delivery layer did its job even though the platform could not match it to a user. Second, Clarity Score is per Channel. A Meta CAPI Channel can read ninety eight percent while a Google Ads Channel reads seventy percent, because each destination has its own token, endpoint, and validation. One number for both hides where the failure sits.

Healthy Channels sit near one hundred percent, typically ninety five percent or higher in a stable week. A Channel below ninety percent is worth investigating, and below seventy percent means purchase data is actively being lost upstream and should be treated as an immediate priority. The number is the first line of any tracking health check, the point where a store stops asking whether purchase Pulses are being sent and starts asking whether they are arriving.

Julian Juenemann of MeasureSchool has documented that client side pixel loss for the average Shopify store runs forty to sixty percent, concentrated in iOS and Safari traffic where App Tracking Transparency and Intelligent Tracking Prevention block browser events. Those purchases only survive when the store sends them server side as a Pulse, and if the Pulse itself is then dropped by an unhealthy Channel, the purchase is lost twice, first by the browser restriction, then by the delivery failure.

What Match Strength Measures

Match Strength is Meta’s estimate of how confidently it can link the purchase data a Shopify store sent to a real user on its platform. Meta computes it from the identity parameters included in the event payload: email, phone, first and last name, city, state, ZIP, country, plus the browser ID and click ID captured by the pixel.

The score matters because Meta’s delivery algorithm needs to connect a conversion to a person to learn anything from it. A purchase that Meta cannot match to an account is a purchase Meta cannot learn from, even though the Pulse arrived and counts toward Clarity Score. The algorithm keeps optimizing toward the same audiences and creative combinations, because the unmatched sale does not tell it who converted or why.

Meta Business Engineering guidance is to send the maximum number of identifiers available for each event, because each additional identifier increases the probability that Meta can resolve the purchase to an account. Phone is the single highest impact field for most stores, because phone numbers are more stable than email addresses and more likely to be associated with a Facebook account. The browser ID and click ID give Meta two additional paths to the same person that do not depend on personal information matching at all.

Overall Match Strength for a store over a window is not a simple average. It reflects the distribution of identity completeness across all Pulses in that window. A store that sends one thousand purchase Pulses with only a hashed email on each one may show lower Match Strength than a store that sends five hundred Pulses with email, phone, and browser ID on each one, because the second set is matchable far more reliably. That is why two stores with the same Shopify order volume can report different cost per purchase even when both use server side delivery.

Match Strength vs Clarity Score: The Difference in One Table

Question	Clarity Score	Match Strength
What it measures	Did the Pulse reach the Channel?	Could Meta match the arrived Pulse to a user?
Unit	Per Channel percentage	Per event type percentage on Meta
Fails when	Token expired, endpoint changed, checkout stopped creating Pulses	Phone missing, hashing inconsistent, browser ID or click ID lost, checkout fired before identity collected
Shows up as	Lower delivered count in the Stream, gaps vs Shopify orders	Low matched rate in Events Manager despite high delivered count
Fix location	Channel connection and server capture	Checkout data collection and identity payload
What improves	Reported purchase volume	Attributed conversions and optimization learning

A Channel can show a Clarity Score of ninety eight percent and a Match Strength of sixty percent, which means nearly every Pulse is delivered but a large share arrives without enough identity to be useful. The inverse also occurs: a Clarity Score of eighty percent with a Match Strength of ninety percent means the store is losing some delivery but using the delivered data extremely well. Reading the pair as two axes is what keeps the diagnosis targeted.

Why the Confusion Costs Shopify Stores

Merchants confuse the two because both fall when tracking degrades and both live on the same Overview. The cost shows up in three places.

First, misallocated time. A team that sees cost per purchase rise, opens the Overview, sees sixty percent on both numbers, and decides to chase identity fixes will spend weeks adding phone fields and auditing hashing, while the actual cause is an expired Meta token that a five minute re authorization would have restored. The Stream confirms this: failed deliveries cluster around the affected Channel and time window, while identity fields inside successfully delivered Pulses look unchanged.

Second, hidden modeling. Meta reports a purchase whether it actually received your Shopify order or it inferred one, and blended reporting totals can look complete even when delivery is broken. Conversion modeling fills gaps with estimates where no Pulse arrived. A store with Clarity Score at sixty percent may still see reported purchases near Shopify orders because modeled conversions patched the gap, while the delivery system still lacks buyer level data to optimize. The companion article on conversion modeling versus actual signal details how to separate the two by reconciling confirmed Pulses in the Stream against Shopify orders and against reported purchases for the same window.

Third, weak attribution. Modeled or unmatched purchases carry little or no attribution to the ad, ad set, and creative that drove the click. When a large share of purchases is unmatched due to low Match Strength, budget flows to the campaigns whose conversions Meta could observe and attribute, while the campaigns that drove the unmatched sales look inefficient. Even a ten to fifteen percent mix of low Match Strength Pulses is enough to skew which ad sets the system prefers, and the preference compounds each week as the model trains on its own partial picture. Meta’s own analysis estimated that advertisers with iOS heavy audiences saw attributed return on ad spend decline by fifteen to twenty percent in the period after App Tracking Transparency enforcement began, and most of that decline was attribution related.

Safari adds scale to the problem. Statcounter’s 2025 data places Safari share near fifty five percent of United States mobile web traffic, and Statista’s 2025 Global Digital Advertising Report places desktop ad blocker use near forty two percent in North America and Western Europe. Stores that treat delivery and identity as one problem leave the largest traffic segments under recovered.

How to Diagnose Which Metric Fell

Diagnosis starts with the Overview and ends in the Stream, and the order prevents the usual wrong turn.

1. Check Clarity Score by Channel for the Last Seven Days

If one Channel dropped while the other held steady, the cause is Channel specific. If both Channels dropped together, the cause is upstream capture. A healthy Meta CAPI Channel near one hundred percent with a sharp drop in Match Strength on the same days points to an identity change rather than a delivery break.

2. Reconcile Shopify Orders to Confirmed Pulses

Export Shopify orders for the window and count confirmed Pulses to Meta in the Stream for the same time zone. If Shopify orders exceed confirmed Pulses by more than five percent, delivery is broken and modeling may be covering the gap in Ads Manager totals. If Shopify orders and confirmed Pulses align but reported purchases in Ads Manager still diverge, the remaining gap is identity, not delivery.

3. Segment Match Strength by Event Type

Check Match Strength on the purchase event specifically, not the blended account number. A store can show strong match quality on add to cart and weak match quality on purchase if a checkout app injects the purchase event before identity fields are populated. The segment that fell tells you which funnel stage lost data.

4. Read the Recent Stream Near a Known Order

Open the Stream around an order you can verify in Shopify. Confirm the Pulse exists, carries the correct order value, shows a confirmed delivery to Meta CAPI, and carries phone, browser ID, and click ID. A missing Pulse means capture stopped. A present Pulse with thin identity means delivery is healthy but matching is not.

How to Fix Clarity Score First

Fix delivery before touching identity, because identity improvements on undelivered Pulses never reach Meta.

Start with the Channel connection. Refresh the token, re authorize the platform, and confirm the endpoint still matches the current integration. Most connection failures recover in minutes once credentials are renewed, and Clarity Score returns to baseline in the next hourly roll up.

Next, confirm every order creates a Pulse at the server. If Shopify order volume exceeds attempted Pulses, the gap is in capture, not delivery. Open the Stream around a known order and confirm the Pulse exists. A missing Pulse often follows a theme update, a checkout extensibility migration, or a sales channel change that moved where order confirmation fires. The fix sits at the integration point, not in Channel settings.

Then verify the external event ID pipeline. Meta deduplicates browser and server events for the same order using a shared event ID. Without a stable ID the platform may drop or double count purchases, and the confirmed count reads lower than the truth. Generate one deterministic ID per order at confirmation, such as shopify_{order_id}_purchase, and reuse it in every browser and server event for that order, including retries.

Add a weekly check that compares Clarity Score against the prior week and against confirmed Pulse count. The complete Shopify conversion tracking guide places this delivery verification at the foundation for a reason. No bidding, audience, or creative work can compensate for a Channel that is not receiving the data.

How to Fix Match Strength After Delivery Is Healthy

Once Clarity Score holds above ninety five percent for a full week, turn to identity. The following steps address the causes that suppress Match Strength most often.

1. Collect Phone Numbers at Checkout

Enable phone collection if it is not already active, and pass the same field through to the purchase Pulse. This is the single highest impact change for most stores, because phone is the identifier Meta matches most reliably. Many Shopify themes collect phone for shipping but drop it before the payload is built, which discards the most valuable matching signal.

2. Standardize Hashing and Normalization

Send every personal identifier lowercased, trimmed, and hashed with SHA-256. Normalize phone numbers by stripping formatting characters and using E.164 style digits before hashing. If you use a signal layer, normalization is handled automatically. If you maintain a custom CAPI implementation, audit the hashing logic for every identifier type, because a single inconsistency breaks matching for every affected Pulse.

3. Verify the Browser ID Reaches the Server Event

Confirm that the Facebook browser ID is read on the first touchpoint and forwarded into the server event payload for every checkout completion. Theme updates and third party apps are the usual cause of a quiet drop here, so check page source or the pixel helper after every theme change.

4. Preserve the Click ID

The click ID appended to the URL when a user clicks an ad must be passed through to the purchase Pulse and not stripped during checkout redirects or thank you page handling. Some stores lose the click ID at the redirect step, which removes the direct link between the ad and the conversion.

5. Reconcile Match Strength at the Event Level

Watch the purchase event specifically rather than the account average. When purchase Match Strength lifts from the low sixties to the high eighties, cost per purchase often trends down over the following one to two weeks as the delivery model exits learning phase on the larger, stronger signal. The Shopify Meta ads optimization guide documents the same progression: clean delivery plus strong identity lets broad targeting and creative testing perform as intended.

How Hawklists Surfaces Both Metrics Together

Hawklists is a Shopify signal layer. Every order creates one Pulse in the Stream, every connected Channel reports delivery back, and the Overview presents a per Channel Clarity Score alongside a Match Strength reading for Meta in one place. The design separates the three concerns blended totals collapse into one number: did the purchase arrive, could it be matched, and can it be attributed to an ad.

The pulse stream is the source of truth for both. Clarity Score is delivered Pulses divided by total attempted per Channel over the window. Match Strength is the share of arrived Pulses Meta could match to a user account. The stable external event ID handles deduplication and attribution. The Hawk assistant reads the Stream and flags which concern moved on any given week, for example when phone stopped being included after a checkout change or when the browser ID went missing after a theme update. None of this exposes model internals. The benefit level description is that actual Pulses replace modeled estimates as confirmed, matched, attributable purchases, and the platform report converges toward Shopify truth rather than being patched around it.

What Hawklists does not do matters for accurate expectations here. It does not send Pulses to GA4, TikTok, Snapchat, Pinterest, or X through its Channels, which remain roadmap items. It does not claim recovery through device fingerprinting or CSV uploads that are not shipped. Pricing follows published tiers, with the Starter free tier covering roughly five hundred Pulses per month and Growth at twenty nine dollars per month for full Channel delivery, and multi store delivery in the Scale tier for agencies. The scope keeps the promise narrow and testable: restore delivery for Meta CAPI and Google Ads, and surface the delivery and identity numbers that prove the recovery held.

FAQ

What is the difference between Clarity Score and Match Strength on Shopify?

Clarity Score measures delivery, the percentage of purchase Pulses a Channel confirmed receiving. Match Strength measures identity, the percentage of arrived Pulses Meta could match to a Facebook or Instagram user. One is a plumbing number, the other is a data number. A store can be healthy on one and weak on the other, and the fix is different in each case.

Which should I fix first, Clarity Score or Match Strength?

Fix Clarity Score first. A Pulse that never reaches the Channel cannot be matched regardless of its identity fields. Once delivery sits near one hundred percent for a full week, fix Match Strength by completing the identity payload on each purchase Pulse.

What is a good Clarity Score?

Healthy Channels typically sit at ninety five percent or higher. Below ninety percent is worth investigating, below seventy percent means revenue data is being lost before optimization. The threshold is per Channel, so check Meta CAPI and Google Ads separately.

What is a good Match Strength?

Match Strength is reported per event type. Many stores see purchase event Match Strength in the sixty to seventy percent range before optimization and aim for eighty five to ninety percent or higher after adding phone, browser ID, and click ID to every Pulse. The lift depends on what the store currently collects at checkout.

Can a store have high Clarity Score and low Match Strength at the same time?

Yes, and it is common. High Clarity Score means delivery is working. Low Match Strength means the delivered Pulses carry thin identity. The opposite pairing is also possible. Reading them as two axes is what keeps diagnosis targeted instead of guessed.

Does low Match Strength affect Meta Ads cost?

Not directly on cost per click. What it affects is optimization and attribution. When a large share of purchases arrives without matchable identity, the ad that drove each sale never gets credit, learning phase lasts longer, and budget flows to the campaigns whose conversions were matchable rather than the campaigns that actually drove the sales.

How do I check whether my tracking problem is delivery or identity?

Check Clarity Score by Channel and Match Strength on the purchase event for the same seven day window. Then reconcile Shopify orders to confirmed Pulses in the Stream, and confirm the Pulse for a known order carries phone, browser ID, and click ID. The metric that moved points to the layer that broke.

Related Resources

• Shopify signal recovery guide: the pillar guide that separates delivery from identity and walks through full recovery
• Complete Shopify conversion tracking guide: the foundation guide that places delivery verification before any bidding work
• Clarity Score for Shopify merchants: the delivery health metric that verifies Pulses reach each Channel
• Match Strength on Meta Ads: the identity metric that controls whether delivered Pulses count for delivery
• What Meta CAPI is: how the server side Channel receives Shopify purchase Pulses
• Conversion modeling vs actual signal: how to tell confirmed Pulses from modeled estimates in blended reporting
• Shopify Meta ads optimization guide: how clean delivery plus strong identity improves cost per purchase over one to two weeks