What Counts as a Qualified Lead Isn't Universal

I run a rule in my current work that sounds almost too simple to be worth stating: when I'm setting up how a campaign gets measured, there's exactly one thing I'm allowed to change from client to client. Everything else about the measurement structure stays the same. The one variable is the definition of what actually counts as a qualified result.

That constraint is deliberate, and it exists because of a mistake I watched happen too many times before I built it in: treating "qualified" as if it means the same thing everywhere.

For a lead-generation campaign, a qualified result might be someone who answered the phone or booked a demo, something you can pull straight from a CRM. For a SaaS trial, "qualified" has nothing to do with a phone call, it's whether someone actually activated, logged in more than once or twice, showed real intent to use the thing they signed up for. For an ecommerce campaign, it's simpler again: did they buy something within a sensible window after clicking.

Three completely different definitions, three completely different data sources. What stays fixed underneath all of it is the structure: how the numbers get pulled together, how cost gets measured against value. Change the definition of "qualified" in one place, and the whole thing works for the next client, without redesigning the measurement approach from scratch every time.

Before comparing performance across campaigns or clients, check that "success" means the same thing in both.

It usually doesn't, and that's often where a real disagreement about whether something is "working" actually lives. Two campaigns can post identical cost-per-result numbers and mean entirely different things, if one of them is counting phone calls and the other is counting completed purchases. Treated as if they're comparable, that's not a measurement problem, it's a definition problem wearing a measurement problem's clothes.

This isn't a technique I picked up recently and I'm not claiming it's unique to how I work. It's the same instinct that's shown up across every commercial environment I've worked in, applied to whatever the current problem happens to be. The details change, campaign structure, list quality, client scoping, but the underlying move doesn't: check what's actually being measured before trusting what the measurement says.

What's different about this one is that it's current. It's not a story from a decade ago. It's how I run measurement on my own work right now, which matters, because it's easy for a career story to sound like something that used to be true. This one is still true. Halo starts every engagement by asking the same underlying question, just aimed at a business rather than a single campaign: what are we actually measuring here, and is it the right thing?

What this looks like in practice, if you're the one trying to work out whether a number can be trusted:

• Before comparing two campaigns, two channels, or two time periods, check whether "success" is defined the same way in both. Don't assume it, check it.
• Ask what specific action counts as the qualifying event, and where that data actually comes from. A vague answer here usually means the number downstream is vaguer than it looks.
• Build your measurement structure so the definition of success is the one thing you change per situation, not something you rebuild every time. Consistency in structure, precision in definition.
• Treat "the numbers don't agree" as a prompt to check the definitions first, not the data quality first. Definitions are wrong far more often than data is broken.

None of this requires new tools or more dashboards. It requires being honest about what a number is actually counting before deciding what it's telling you.

This is a current-era example of a pattern that's shown up across a decade of different businesses. The fuller picture is on Insights. And it's part of why the Commercial Audit starts by finding the right constraint before recommending anything about it.