Customer Matching
Customer matching is the practice of pairing each prospect with the most relevant offer, content path, or sales representative based on their attributes and needs.
Key takeaways
- Matching turns a segment label into a destination: offer, proof, page and record owner.
- Deterministic ordered rules keep routing auditable and make wrong matches traceable to one condition.
- Few well-differentiated destinations outperform many that differ only in wording.
- Every rule set needs a default branch so no prospect is left unrouted.
- Matching amplifies a differentiated offer; it cannot create differentiation that is absent.
In depth
Matching is a lookup: inputs on one side, destinations on the other, and a rule that connects them. The inputs are attributes you already hold or have just collected, such as segment, score band, declared goal, team size or current tooling. The destinations are concrete assets: a plan tier, a case study, a result page, an owner queue. The rule is deterministic, so identical inputs always resolve to the same destination and any mismatch traces back to a specific condition rather than a judgement call.
Match quality rises with the freshness and granularity of the inputs and falls as the rule set grows. A handful of broad rules covers most traffic and stays auditable, while dozens of narrow rules cover edge cases but overlap, conflict and quietly rot as offers change. The second lever is how many destinations exist at all. Two well-differentiated paths usually outperform six thinly differentiated ones, because each destination needs its own proof, its own call to action and someone accountable for keeping it current.
Teams normally implement matching as ordered rules with a default fallback, so nothing is left unrouted. In a quiz funnel the match resolves at the result moment: the score band selects the result page, the declared goal selects the proof and the call to action, and the same values write the CRM owner and tags in one pass. That single pass matters, because it keeps what the prospect sees and what the rep sees consistent, instead of routing the record one way and the page another.
Matching cannot fix an offer that does not exist. With one product, one price and one proof point, routing merely relabels the same destination, and the effort belongs in building differentiation instead. It also breaks when inputs are stale or deliberately understated: a buyer who shrinks their team size to avoid a sales call lands in self-serve and never sees the plan that fits. Rules keyed to who someone is age worse than rules keyed to what they said they need.
Example in practice
How to measure it
Compare outcomes by matched destination rather than in aggregate. For each branch, take the next action you wanted, such as a demo booked, a trial started or a reply received, and divide it by the number of prospects routed there. A branch with volume but no forward motion is either badly matched or pointing at a weak asset, and reviewing who landed in it tells you which of the two it is.
Also track how often the fallback branch fires and how often a rep manually reassigns a record. A large fallback share means the rules do not cover the traffic you actually receive. Frequent manual reassignment means the rule disagrees with human judgement, and the reason a rep gives when reassigning usually names the input your rule was missing.
Common mistakes
The most common error is routing on data the prospect never confirmed. An enrichment record says fifty employees, the rule serves an enterprise deck, and the founder of a five-person team reads a page written for someone else. Ask directly for the one or two attributes the routing actually depends on, and let that answer override the inferred value. Where a guess is unavoidable, keep the destination broad enough to survive being wrong.
The second error is letting rules accumulate without an owner. Offers get renamed, a case study is retired, a rep leaves the team, and the rule still points at all three. Nothing throws an error; prospects simply land on weaker destinations. Keep a list of rules alongside the assets they reference, review it whenever an offer changes, and log the matched destination on each record so you can see which branches fire.
Frequently asked questions
How is customer matching different from segmentation?
Segmentation groups prospects into audiences, while customer matching is the next step that routes each prospect to a specific offer, page, or rep. Matching is the operational action that makes segmentation pay off.
What data does reliable customer matching need?
It needs accurate, current attributes such as role, team size, goal, and use case, ideally self-reported rather than guessed. Stale data sends prospects down the wrong path and damages trust before the first conversation.
Can a quiz funnel match leads automatically at the end?
Yes, the score and answers can select a tier-specific result page, a tailored call to action, and a CRM owner in a single motion. This lets enterprise and small-business respondents leave the same quiz on entirely different paths.
What is the difference between segmentation and customer matching?
Segmentation groups prospects by shared attributes; matching decides what each group actually receives. Segmentation produces a label, while matching produces a destination such as a plan, a case study, a result page or a named owner. A team can segment carefully and still show everyone the same experience, which is where the value of that segmentation quietly disappears.
How many matching rules should I start with?
Start with as many rules as you have genuinely different destinations, which for most teams is two or three. Add a rule only when you can name the asset it points at and explain why that asset works better for that group. Rules without a distinct destination behind them add maintenance cost and change nothing about what the prospect actually sees.
Which data should matching rules run on?
Prefer attributes the prospect stated in the current session, because they are fresh and consented. Use enrichment for context that is stable and public, such as industry or headcount band. Avoid routing on behaviour alone, since a single page visit rarely identifies a need, and avoid attributes likely to change between the visit and the sales conversation.
Should matching assign a sales owner as well as content?
Yes, wherever ownership differs by segment. Routing the page and the owner from the same rule keeps the message and the rep aligned, so a prospect who saw an enterprise result page is called by someone who sells that. Splitting the two decisions across separate systems is how a self-serve lead ends up on an enterprise rep's call list.
How do I handle prospects who match more than one rule?
Order the rules and take the first match rather than letting several fire at once. Put the narrowest, highest-value condition first and the broadest last. Then record which rule matched on the record itself, because overlapping conditions are almost impossible to debug later if you know only the destination and not the branch that chose it.
How do I know when a match was wrong?
Watch for the signals that follow a mismatch: a prospect books the wrong meeting type, asks about a plan they were never shown, or converts through a path other than the one they were routed to. Reps also flag it directly. Collect those cases, group them by the rule that fired, and fix the condition rather than the individual record.