Multifamily marketing directors and regional marketing managers already track cost-per-lead and cost-per-lease. Neither is a new concept. The real question isn't which one matters more; it's whether either number can actually be trusted in the systems producing it.
Cost-per-lead and cost-per-lease each answer a different question, and both have a real job in multifamily marketing.
Cost-per-lead isn't the metric to abandon. It's the metric that tells you whether your funnel is staying full. Cost-per-lease is the metric that tells you whether that funnel is producing leases worth the spend.
Ownership cares more about cost-per-lease because it's the number closest to an actual business outcome: a signed lease. When it's time to decide whether to increase spend on one channel or cut another, cost-per-lease is the more decisive number. That's exactly why it matters so much that the number is correct. A budget decision built on the wrong cost-per-lease is worse than no decision at all.
This is where both numbers start to break down, and it's an attribution problem, not a tracking problem.
An ad platform captures a lead click, but that click isn't tied to the actual person anywhere the marketing team can see. A leasing agent logs that same person in the CRM under whatever source field they select, which may or may not match where the click actually came from. By the time that person signs a lease, the PMS often attributes the whole thing to the property website, since that's where the application was physically completed, even though the website had nothing to do with generating the lead. This pattern is common enough in multifamily reporting that it has a name: the property website myth, and it's a direct result of last-touch attribution, crediting whichever touchpoint happened right before conversion instead of the touchpoints that actually built it.
One prospect. Three systems. Three different, disconnected records of where they came from.
Cost-per-lease (by source) = Marketing spend for that source ÷ Signed leases attributed to that source
The math isn't the hard part, and multifamily marketing teams already know how to run it. The hard part is that the attribution data feeding that formula is often wrong before the calculation even starts. A team can run the math perfectly and still land on the wrong cost-per-lease because the "signed leases attributed to that source" input was never accurate to begin with.
Some marketing teams know their attribution is shaky and work around it. Others don't know and are making budget calls off numbers that look precise but aren't. Either way, the issue isn't effort or speed. It's a trust in the inputs.
That mistrust shows up most clearly when cost-per-lead and cost-per-lease disagree on the same channel. A channel might show a strong cost-per-lead in the ad platform while showing almost no signed leases in the PMS, not because the channel underperformed, but because the leases it actually produced got attributed elsewhere, often to the property website by default.
When the two numbers disagree, it's rarely because the channel changed. It's because the record of who came from where broke somewhere between the click and the signature.
The fix isn't choosing one metric over the other. It's making sure both numbers are built on attribution the marketing team can actually rely on, down to the source, instead of numbers they don't fully trust or are trying to reconcile by hand.
This is what Halo, Hyly.AI's data and decision intelligence platform, is built to solve.
Hyly.AI’s CrSTAL multi-touch attribution model traces a prospect's full journey, from the first click through to the signed lease, and distributes credit across every touchpoint that influenced the outcome instead of defaulting to whichever one came last.
Before accurate attribution, marketing teams weren’t working with slow numbers. They're working with wrong numbers, and every reconciliation attempt just produces a different wrong number, not the real one. After accurate attribution, cost-per-lead and cost-per-lease finally describe the same reality, because they're both built on the same reliable record of where every lease actually came from.
Hyly.AI’s Halo Spend Manager then takes that corrected picture and flags exactly where budget is being wasted, so reallocating spend is a decision made from real numbers instead of a guess.
Cost-per-lead still has its place. Cost-per-lease is still the number ownership cares about most. Neither one means much without attribution, but with Halo, both numbers can now be trusted.
See how Halo connects lead source to lease outcome → hyly.ai/schedule