Tabellab

Event Match Rate: Matched Share by Event Type, Unmatched Events, the Weighted Overall Rate & Status Flags

Lesson 1 of 20Lab

All lessons
  1. Event Match Rate: Matched Share by Event Type, Unmatched Events, the Weighted Overall Rate & Status FlagsLabFree
  2. Match Keys: Identifier Coverage, Match Rate When Sent, Match Rate by Number of Identifiers & Average Identifiers per EventLab Locked
  3. Delivery Reliability: Acceptance Rate, Final Delivery Rate after Retries, Days below Target & Events Lost for GoodLab Locked
  4. Browser vs Server: Distinct Purchases, Browser-Only and Server-Only Groups, Source Coverage & the Overlap RuleLab Locked
  5. Event ID Deduplication: Records per ID and Name, Value Counted Once, Overstatement & Name MismatchesLab Locked
  6. Deduplication Window: Arrival Gap between Browser and Server, Status, Pairs Counted Twice & Fast PairsLab Locked
  7. Parameter Completeness: Completeness, Validity, Usable Rate, a Weighted Score & Parameters below TargetLab Locked
  8. Value Accuracy: Difference and Error % against Order Totals, Tolerance Checks, Net vs Absolute Error & a Scatter CheckLab Locked
  9. Delay Distribution: Delay Bands with COUNTIFS, Cumulative Share, Median, 90th Percentile & the Mean TrapLab Locked
  10. Late Events vs Attribution Window: Shares, Cumulative Share, Events and Value Beyond the WindowLab Locked
  11. Conversions Recovered by Server Events: Browser Capture, Capture with Server, Uplift in Points & Recovered ValueLab Locked
  12. Consent-Respecting Measurement: Consent Rate, Events Sent without Consent, Share within Consent & an Audit FlagLab Locked
  13. Attribution Impact: ROAS Before and After Server Events, Reported Change, Overall ROAS & Campaign RankLab Locked
  14. Match Quality by Segment: Match Rate, Shortfall vs Target, Rank, Weighted Device Rates & a Heat MapLab Locked
  15. Event Quality Score: Weighted Scores with SUMPRODUCT, Grades with IFS, Ranks & the Biggest Weighted LossLab Locked
  16. Is the Improvement Real? Two-Proportion z-Test for Match Rate: Pooled Rate, Standard Error, z, p-Value & Confidence IntervalLab Locked
  17. Monitoring: A Baseline Match Rate, Daily Lower Control Limits for a Proportion, Alerts & a Control ChartLab Locked
  18. What If? A Scenario Grid for CPA: Match Rate × Sending Coverage, Mixed References, Needed Match Rate & Target CellsLab Locked
  19. Reconciliation with the Order System: Weekly Ratio, Status Bands, Trend with SLOPE & a FORECAST.LINEAR Warning LightLab Locked
  20. Final Project: Server-Side Event Quality Scorecard with Four Rates, Recovery Uplift, a Weighted Score, Rank, Flags & a Combo ChartLab Locked

You are not signed in — the lab works, but your progress is not saved. Sign up

Lesson 1 of 20 is free. Unlock all 20 hands-on labs, the final exam and your certificate.

Buy course — $9.90
Loading the spreadsheet…

What is an event match rate, and why does it decide what your ads can learn?

If you run an online shop and send purchase information to an ad platform from your own server, you rely on one quiet assumption: that the platform can recognise the person behind each message. When it can, the event becomes a data point for reporting and bidding. When it cannot, the event arrives, is counted as received, and then does very little. The share of events that the platform manages to link to a person it knows is the event match rate.

Server-side conversion tracking (most ad platforms call it a conversions API) sends events from your server instead of from the visitor's browser. That avoids many browser problems, but it also removes the browser's built-in clues, so the quality of what you attach to each event matters more. A server event without a good identifier is like a letter without a street address: delivered to the post office, never to a door.

This lesson turns that idea into numbers you can calculate in a spreadsheet. The example is Corvane Outfitters, a fictional online shop for outdoor gear. All events, rates and numbers are invented for learning, and the thresholds are illustrative, not official values of any ad platform. You will work with the same eight event types as in the lab above, over one week.

The core concept: sent, matched and unmatched

Every server event passes through three stages. Your shop stores the order and builds a message. The message carries customer information parameters: a hashed email address, a hashed phone number, the advertising click ID if the visitor arrived from an ad, a first-party browser ID, the IP address and user agent. The platform compares them with what it already knows about its own users and either finds a match or does not.

From order to matched eventShop serverstores the orderServer event+ hashed email, phone,click ID, user agentAd platformtries to matchMatched57,950 events65.8% match rateUnmatched30,150 events88,100 events sent in the week.Only matched events can beattributed, used for biddingor built into audiences.
The path of a server event. In the example week Corvane Outfitters sent 88,100 events; the platform matched 57,950 and could not match 30,150. The overall match rate is 57,950 ÷ 88,100 = 65.8%.

Three words are easy to mix up, so fix them now. Sent is the number of events your server transmitted. Matched is the number the platform could link to a user. Unmatched is the difference. The match rate is matched divided by sent, and it is always between 0 % and 100 %. It describes the quality of the identifiers, not the number of sales.

A match rate is also not the same thing as attribution. A matched event can still be credited to no campaign, because the person never clicked or saw an ad within the attribution window. Matching is the first gate; attribution is the second. If the first gate is narrow, nothing downstream can be good.

Send only events from visitors whose consent allows marketing measurement, and hash identifiers the way the platform requires before they leave your server. A higher match rate is never a reason to collect more personal data than you need or to ignore a refusal. The course returns to consent in lesson 12.

A fully worked example: Corvane Outfitters in one week

Here are the eight event types of the lab with the number of events sent, the number matched, the match rate, the unmatched events and the status flag, which the lab defines as Good from 85 %, Watch from 65 % and Poor below that.

EventSentMatchedMatch rateUnmatchedStatus
ViewContent48,20028,90060.0%19,300Poor
Search9,1005,20057.1%3,900Poor
AddToCart12,4008,70070.2%3,700Watch
InitiateCheckout6,8005,30077.9%1,500Watch
AddPaymentInfo4,3003,60083.7%700Watch
Purchase3,1502,85090.5%300Good
Lead2,9002,30079.3%600Watch
CompleteRegistration1,2501,10088.0%150Good
All events88,10057,95065.8%30,150

The formulas behind the calculated columns, written for row 4 and copied down to row 11, are:

  • Match rate (D4): =C4/B4. Matched divided by sent. Format the column as a percentage.
  • Unmatched (E4): =B4-C4. The events the platform could not use.
  • Overall match rate (D12): =SUM(C4:C11)/SUM(B4:B11). Total matched divided by total sent, never the average of the eight rates.
  • Status (F4): =IFS(D4>=$B$14,"Good",D4>=$B$15,"Watch",TRUE,"Poor"). The thresholds live in B14 and B15 and are locked with dollar signs.

Match rate per event type, one weekGoodWatchPoorViewContent60.0%Search57.1%AddToCart70.2%InitiateCheckout77.9%AddPaymentInfo83.7%Purchase90.5%Lead79.3%CompleteRegistration88.0%Watch 65%Good 85%0%25%50%75%100%Matched events ÷ sent events (fictional data)
Match rate per event type in the example week. The dashed lines mark the Watch threshold (65 %) and the Good threshold (85 %). Only Purchase and CompleteRegistration are Good; ViewContent and Search are Poor.

Why the overall rate comes from sums, not from an average of rates

The overall match rate of the week is 57,950 ÷ 88,100 = 65.8%. If you instead average the eight rates in column D you get 75.8%. The two numbers differ by 10.1 percentage points, and the difference is not a rounding issue. ViewContent alone makes up 55% of all events and has a rate of only 60.0%, so it pulls the true overall rate down. The simple average gives the small Lead and CompleteRegistration events the same weight as ViewContent.

MethodCalculationResult
Weighted (correct)57,950 ÷ 88,10065.8%
Simple average of the eight ratesAVERAGE(D4:D11)75.8%

The general rule is the same for every rate in this course: add the numerators, add the denominators, then divide. Averaging ratios is only right when every denominator is equal.

Reading the status flags

The status column turns eight percentages into a to-do list. A flag is a prompt for a question, not a verdict. A Poor ViewContent rate is largely expected: most visitors at that stage are anonymous, so there is no email address to send. The same Poor rate on Purchase would be an alarm, because the buyer has just typed an email address into your checkout.

In the example week Purchase reaches 90.5% and CompleteRegistration 88.0%, both Good. AddToCart (70.2%), InitiateCheckout (77.9%), AddPaymentInfo (83.7%) and Lead (79.3%) are Watch. ViewContent (60.0%) and Search (57.1%) are Poor. The funnel pattern is typical: the closer an event is to the purchase, the more identifiers the shop holds, and the higher the rate.

Keep the thresholds in cells, not inside the formula. When your team decides that Good starts at 88 % for purchase-related events, you change one cell and every flag updates.

Step by step in Excel

  1. Enter the events in A4:A11, the sent counts in B4:B11 and the matched counts in C4:C11. Add the two thresholds in B14 (Good from) and B15 (Watch from) as percentages.
  2. Click D4 and type =C4/B4. Format D4:D11 as a percentage with one decimal (Ctrl + Shift + 5 applies a percentage format).
  3. Click E4 and type =B4-C4.
  4. Select D4:E11 and press Ctrl + D to copy the formulas from row 4 down to row 11 (or drag the fill handle).
  5. Click B12 and type =SUM(B4:B11); copy it right to C12. Then click D12 and type =SUM(C4:C11)/SUM(B4:B11).
  6. Click F4 and type =IFS(D4>=$B$14,"Good",D4>=$B$15,"Watch",TRUE,"Poor"). In Excel versions without IFS use =IF(D4>=$B$14,"Good",IF(D4>=$B$15,"Watch","Poor")). Copy it down to F11.
  7. Cross-check: the unmatched column must add up to the difference of the totals: =SUM(E4:E11) must equal =B12-C12.
  8. Select A3:A11 and D3:D11 (hold Ctrl for the second range), choose Insert › Bar chart and give the chart a title that says what it shows.

Common mistakes and how to spot them

  • Averaging the rates. =AVERAGE(D4:D11) gives every event type the same weight and understates the problem when a large event type has a low rate. Divide the totals instead.
  • Inverting the ratio. =B4/C4 produces numbers above 100 %. A match rate can never exceed 100 %; if it does, the numerator and denominator are swapped.
  • Dividing by all events instead of the event's own sent count. =C4/$B$12 gives the share of the week's matches, not the match rate of this event type.
  • Comparing sent counts that include test events. Test and debug events inflate the denominator or the numerator. Filter them out of the export before you calculate.
  • Unlocked thresholds. =IFS(D4>=B14,...) copied down turns into B15, B16 and so on. Lock them as $B$14 and $B$15.
  • Wrong order of IFS conditions. IFS stops at the first condition that is true. If the Watch test comes before the Good test, every event at or above 65 % is labelled Watch.

How to read the result

Read the table in three passes. First look at the overall rate: 65.8% means that about one event in three is of little use to the platform. Second, look at where the volume is. ViewContent and Search together send 65% of all events but account for 77% of the unmatched ones. Third, look at the events that matter most for money: Purchase has 300 unmatched events this week, each a sale that cannot be credited cleanly.

A good question to ask of every low rate is: which identifier was available at that moment and did we send it? For an anonymous ViewContent, the honest answer may be that none was available, and the right response is to leave that rate alone. For a logged-in customer adding to the cart, the email address is known and a low rate points to a missing field in your data layer.

What moves a match rate

  • More identifiers per event. Sending a hashed email and a hashed phone number matches more often than sending either alone. Lesson 2 measures this.
  • Capturing the click ID early. The advertising click ID is a strong key, but it must be stored in a first-party cookie or in the session on the landing page, and attached to the later event.
  • Collecting email earlier in the funnel. A newsletter signup or a login before checkout moves identifiers to the left of the funnel. This must happen with the visitor's knowledge and consent.
  • Correct hashing. Identifiers are normalised (trimmed, lower case) and then hashed. A single stray space gives a different hash and a guaranteed miss.
  • Clean delivery. Events that are rejected or arrive late (lessons 3, 9 and 10) never get the chance to match.

Quick reference: functions and shortcuts in this lesson

Function / shortcutWhat it does hereExample
DivisionMatch rate of an event type=C4/B4
SubtractionUnmatched events=B4-C4
SUMTotals of sent and matched=SUM(B4:B11)
IFSStatus with three levels=IFS(D4>=$B$14,"Good",D4>=$B$15,"Watch",TRUE,"Poor")
AVERAGEThe tempting but wrong overall rate=AVERAGE(D4:D11)
Ctrl + Shift + 5Percentage format
F4 (Mac: Cmd + T)Toggle absolute references$B$14

Real-world uses

  • Weekly data-quality report. Export sent and matched counts per event type from the platform's event diagnostics, paste them into the sheet and review the flags every Monday.
  • Release checks. Compare the match rate of the week before and after a change to the checkout or the data layer. A drop is the first sign that an identifier stopped flowing.
  • Vendor or setup comparison. If two server setups run in parallel, compare their match rates on the same event type before you switch one off.
  • Budget conversations. A match rate in plain numbers helps explain why a campaign cannot be optimised on purchases yet, and what fix would unlock it.

Limits of the match rate

The match rate measures the platform's ability to link an event to a user. It does not tell you whether the event is correct, whether it was counted twice, whether the value is right or whether it arrived in time. A shop can have a 95 % match rate and still report the wrong revenue. That is why this course continues with deduplication, parameter completeness, value accuracy and delays, and brings them together in a quality score.

Platform dashboards also show their own match quality indicators, calculated in their own way and changing with product updates. Treat them as one input and build your own rate from counts you can reproduce. The arithmetic in this course is durable; any specific score or label a platform shows today may not be.

What you will build in the rest of this course

Lesson 1 is free. Lessons 2 to 20 make up the paid course ($9.90 one-time). Each has its own live lab and builds on the idea that server events must be measured like any other product: for coverage, accuracy and timeliness.

  • Match Keys: Identifier Coverage, Match Rate When Sent, Match Rate by Number of Identifiers & Average Identifiers per Event. You measure how often each customer information parameter is present, how well it matches when sent, how the match rate grows with the number of identifiers and the weighted average identifiers per event.
  • Delivery Reliability: Acceptance Rate, Final Delivery Rate after Retries, Days below Target & Events Lost for Good. You separate accepted, rejected and failed server events, calculate the acceptance and final delivery rates, count the days below target, add up the events lost for good and chart the daily rate.
  • Browser vs Server: Distinct Purchases, Browser-Only and Server-Only Groups, Source Coverage & the Overlap Rule. You use the overlap rule to turn browser and server counts into distinct purchases, split them into browser-only and server-only groups, calculate each source's coverage and chart the groups by channel.
  • Event ID Deduplication: Records per ID and Name, Value Counted Once, Overstatement & Name Mismatches. You count the records behind each event ID and name, divide values by that count, calculate the value after deduplication and the overstatement and find the value that stays double counted because the event names differ.
  • Deduplication Window: Arrival Gap between Browser and Server, Status, Pairs Counted Twice & Fast Pairs. You turn browser and server arrival times into gaps in hours, label each pair as deduplicated or counted twice against the window, count the problem pairs, measure the share of fast pairs and highlight the late ones.
  • Parameter Completeness: Completeness, Validity, Usable Rate, a Weighted Score & Parameters below Target. You measure how complete and valid eight Purchase event parameters are, combine them into a weighted usable score, count the parameters below target and highlight them.
  • Value Accuracy: Difference and Error % against Order Totals, Tolerance Checks, Net vs Absolute Error & a Scatter Check. You compare event values with order totals, calculate difference and error percentage, classify each order against tolerance and review limits, contrast net and absolute error and plot sent against true values.
  • Delay Distribution: Delay Bands with COUNTIFS, Cumulative Share, Median, 90th Percentile & the Mean Trap. You count 20 server events into delay bands, build the cumulative share, calculate the median, 90th percentile and mean delay and chart the distribution.
  • Late Events vs Attribution Window: Shares, Cumulative Share, Events and Value Beyond the Window. You split delayed conversions into delay bands, build shares and a cumulative curve, count the events inside an attribution window, value the events that arrive too late and chart the curve.
  • Conversions Recovered by Server Events: Browser Capture, Capture with Server, Uplift in Points & Recovered Value. You compare browser capture with capture including server events per browser, measure the uplift in points, value the recovered conversions, calculate the overall capture and the share that comes from the most restrictive environments.
  • Consent-Respecting Measurement: Consent Rate, Events Sent without Consent, Share within Consent & an Audit Flag. You calculate the consent rate per market, find server events that were sent without consent, measure the share of events within consent, total the surplus and highlight the markets that need a fix.
  • Attribution Impact: ROAS Before and After Server Events, Reported Change, Overall ROAS & Campaign Rank. You compare ROAS before and after server events per campaign, quantify the reported change, calculate the overall ROAS from totals, rank a campaign and learn why reported gains are a measurement effect, not extra sales.
  • Match Quality by Segment: Match Rate, Shortfall vs Target, Rank, Weighted Device Rates & a Heat Map. You calculate the match rate of twelve market and device segments, translate it into a shortfall against a target, rank the segments, aggregate by device with SUMIFS and colour the rates.
  • Event Quality Score: Weighted Scores with SUMPRODUCT, Grades with IFS, Ranks & the Biggest Weighted Loss. You combine match rate, completeness, timeliness, delivery and duplicates into a weighted quality score per source, grade and rank the sources, find the biggest weighted loss with INDEX and MATCH and chart the scores.
  • Is the Improvement Real? Two-Proportion z-Test for Match Rate: Pooled Rate, Standard Error, z, p-Value & Confidence Interval. You test whether a higher match rate after a change is more than noise: pooled rate, standard error, z, p-value, a verdict against the significance level and the lower end of a confidence interval.
  • Monitoring: A Baseline Match Rate, Daily Lower Control Limits for a Proportion, Alerts & a Control Chart. You set a baseline from a calm period, calculate a daily control limit that depends on the events sent, flag the days below it, count the signals and chart the rate against its limit.
  • What If? A Scenario Grid for CPA: Match Rate × Sending Coverage, Mixed References, Needed Match Rate & Target Cells. You model attributed conversions from orders, coverage, match rate and credited share, fill a two-way grid of the CPA with mixed references, find the match rate needed for a target and highlight the scenarios that reach it.
  • Reconciliation with the Order System: Weekly Ratio, Status Bands, Trend with SLOPE & a FORECAST.LINEAR Warning Light. You reconcile platform conversions with consented orders week by week, classify each week, measure the trend, forecast the next week and chart the ratio.
  • Final Project: Server-Side Event Quality Scorecard with Four Rates, Recovery Uplift, a Weighted Score, Rank, Flags & a Combo Chart. You combine the course into a quarterly scorecard for six sources: match, duplicate, completeness and on-time rates, the recovery uplift, a weighted quality score with rank, a flag below target and a combo chart.

Summary

A server event helps only when the platform can match it. The match rate is =C4/B4 per event type, the overall rate is =SUM(C4:C11)/SUM(B4:B11) from the totals, and a status built with IFS and locked thresholds turns the table into priorities. At Corvane Outfitters 57,950 of 88,100 events were matched, 65.8% overall, while a simple average of the eight rates would have shown 75.8%. The Purchase rate of 90.5% is Good; the large anonymous events are Poor and need a different reading.

Now scroll up to the lab and build the sheet yourself. It takes about fifteen minutes, the Coach checks each step, and you will end up with a match-rate table you can apply to your own event export today.

Frequently asked questions

What is an event match rate in server-side conversion tracking?

The event match rate is the share of server events that the ad platform can link to a person it knows. It equals matched events divided by sent events. It depends on the customer information parameters you send with each event, such as a hashed email address, a hashed phone number or an advertising click ID.

How do I calculate the overall match rate in Excel?

Add up the matched events and the sent events of all event types, then divide: =SUM(C4:C11)/SUM(B4:B11). Do not average the individual rates with AVERAGE, because that gives small event types the same weight as large ones and usually gives a different, misleading result.

Why is the match rate of some events low even when the setup is correct?

Events early in the funnel, such as page views or searches, often come from anonymous visitors for whom the shop holds no email address or phone number. Their low match rate is expected. The same low rate on Purchase, where the buyer has just typed an email address, would point to a missing or wrongly formatted field.

Is a higher match rate always better?

A higher match rate means the platform can use more of your events, but it must be achieved with data you are allowed to send. Send events only for visitors whose consent allows marketing measurement, hash identifiers as the platform requires and never collect extra personal data only to push the number up.

What is a good match rate?

There is no universal value. Platforms show their own indicators, which change over time, and the thresholds in this lab (Good from 85 %, Watch from 65 %) are illustrative. Set your own targets per event type from your baseline, and watch the trend after every change to the checkout or the data layer.

Does a matched event mean the conversion is attributed to an ad?

No. Matching only means that the platform recognised the person. Attribution is a second step: the person must also have clicked or seen one of your ads within the attribution window. A matched event can therefore remain unattributed, and an unmatched event can never be attributed.

Keep going: Server-Side Conversion API Quality: Event Match Rates, Deduplication, Parameter Completeness, Delays, Recovered Conversions & Attribution Impact

This free lab is lesson 1 of 20. Unlock the other 19 hands-on labs, the final exam and your certificate for a one-time $9.90.

  1. Match Keys: Identifier Coverage, Match Rate When Sent, Match Rate by Number of Identifiers & Average Identifiers per Event
  2. Delivery Reliability: Acceptance Rate, Final Delivery Rate after Retries, Days below Target & Events Lost for Good
  3. Browser vs Server: Distinct Purchases, Browser-Only and Server-Only Groups, Source Coverage & the Overlap Rule
  4. Event ID Deduplication: Records per ID and Name, Value Counted Once, Overstatement & Name Mismatches
  5. Deduplication Window: Arrival Gap between Browser and Server, Status, Pairs Counted Twice & Fast Pairs
  6. Parameter Completeness: Completeness, Validity, Usable Rate, a Weighted Score & Parameters below Target
  7. Value Accuracy: Difference and Error % against Order Totals, Tolerance Checks, Net vs Absolute Error & a Scatter Check
  8. Delay Distribution: Delay Bands with COUNTIFS, Cumulative Share, Median, 90th Percentile & the Mean Trap
  9. Late Events vs Attribution Window: Shares, Cumulative Share, Events and Value Beyond the Window
  10. Conversions Recovered by Server Events: Browser Capture, Capture with Server, Uplift in Points & Recovered Value
  11. Consent-Respecting Measurement: Consent Rate, Events Sent without Consent, Share within Consent & an Audit Flag
  12. Attribution Impact: ROAS Before and After Server Events, Reported Change, Overall ROAS & Campaign Rank
  13. Match Quality by Segment: Match Rate, Shortfall vs Target, Rank, Weighted Device Rates & a Heat Map
  14. Event Quality Score: Weighted Scores with SUMPRODUCT, Grades with IFS, Ranks & the Biggest Weighted Loss
  15. Is the Improvement Real? Two-Proportion z-Test for Match Rate: Pooled Rate, Standard Error, z, p-Value & Confidence Interval
  16. Monitoring: A Baseline Match Rate, Daily Lower Control Limits for a Proportion, Alerts & a Control Chart
  17. What If? A Scenario Grid for CPA: Match Rate × Sending Coverage, Mixed References, Needed Match Rate & Target Cells
  18. Reconciliation with the Order System: Weekly Ratio, Status Bands, Trend with SLOPE & a FORECAST.LINEAR Warning Light
  19. Final Project: Server-Side Event Quality Scorecard with Four Rates, Recovery Uplift, a Weighted Score, Rank, Flags & a Combo Chart

Buy course — $9.90 See the full course