A weekly acquisition-economics scorecard needs five things per channel: spend, leads, qualified leads, the conversion rate between every stage, and a trailing view of CAC even though CAC itself won't move weekly. The point isn't to generate a new number. It's to stop CPL, CPQL and CAC living in three separate reports, reviewed by three separate teams, on three separate timelines, where no one is ever looking at all of them at once when a budget decision actually gets made.
This is the fourth piece in our acquisition-economics series. If you're new to it: How to Reduce Cost Per Lead Without Sacrificing Lead Quality is the fix-it playbook, CPL vs CPQL vs CAC is the framework for which metric owns which decision, and Why Is My Cost Per Lead So High? is the diagnostic checklist for a specific spike. This piece is the operating rhythm that ties all three together on an ongoing basis, rather than only when something looks wrong.
Why weekly, and why not just pick one metric
Each metric in the stack resolves on a different timeline, and that mismatch is exactly why teams default to reporting only the fastest one. CPL is available same-day, inside the ad platform. CPQL needs a qualification tag and usually resolves within a week or two. CAC needs a closed-won deal, which for most B2B sales cycles takes a month or more to show up cleanly.
If you wait for CAC before reviewing anything, you're making decisions on data that's already a quarter old. If you only review CPL, you're making decisions with two-thirds of the picture missing. That timing gap is exactly why teams tend to default to the fastest number even when it cannot answer the commercial question on its own.
The scorecard's job is to hold all three in view at once, at the cadence each one can actually support:
- CPL reviewed weekly, sometimes daily at the campaign level.
- CPQL reviewed weekly once qualification data is flowing reliably from the CRM.
- CAC reviewed monthly or quarterly, but kept visible on the weekly scorecard as a trailing, directional number rather than absent entirely — even a three-week-old CAC figure is more useful sitting next to this week's CPL than no CAC figure at all.
The CRM feedback loop that makes this possible
None of this works without lead status flowing back from the CRM to wherever the scorecard lives. Without that loop, "the scorecard" is just CPL with better formatting.
The setup, in order:
1. Consistent UTM parameters on every campaign. Source, medium, campaign and content fields need to be structured the same way across every channel, every time, or the CRM can't attribute a lead back to the spend that generated it. This sounds basic and is the single most common reason a scorecard build stalls — inconsistent historical UTM tagging means months of otherwise-usable data can't be attributed cleanly.
2. A lead source field in the CRM that's actually populated at creation. Not inferred later, not backfilled by whoever notices it's missing — captured automatically at the point the lead enters the CRM, tied to the UTM data from step one.
3. A qualification stage that's defined once and applied consistently. MQL and SQL need firm, written criteria that sales and marketing have both agreed to, or the CPQL number becomes a matter of opinion rather than a metric anyone trusts. This is worth a short written definition document on its own, separate from the scorecard itself.
4. Closed-loop reporting back to the ad platforms. Google's offline conversion imports and Meta's Conversions API let you feed qualified-lead and closed-won events back into the platform that generated the original click. Without this, the algorithm only ever learns what a "good" outcome looks like from raw lead volume, and will keep optimising toward exactly the low-quality volume you're trying to reduce.
5. A weekly pull, not a live dashboard. Live dashboards feel more sophisticated but tend to get checked constantly and acted on prematurely, especially on CPQL, which needs a full week of data to mean anything. A scheduled weekly pull, reviewed at a set time, is a better discipline than a number that's always technically "live" but rarely stable enough to act on mid-week.
The template
A minimum-viable version, per channel, per week:
| Channel | Spend | Leads | CPL | Qualified Leads | CPQL | SQL Rate | Opportunities | Trailing CAC | WoW CPL Change | Flag |
|---|
The last two columns are what make it a scorecard rather than a report. Week-over-week CPL change catches sudden spikes worth diagnosing (see the diagnostic guide once one shows up). The flag column is where the decision rules from the next section actually get applied, so the scorecard tells you what to look at rather than just what happened.
Decision rules: what the numbers should trigger
A scorecard without decision rules attached to it is just a spreadsheet people glance at. Two rules do most of the work:
If SQL rate sits below roughly 10%, flag the channel regardless of how low its CPL is. A cheap lead that almost never becomes a sales-qualified opportunity is a targeting problem wearing a low-CPL disguise, and CPL alone will never surface it.
If CPQL is competitive but trailing CAC still won't clear roughly a 3:1 ratio against customer lifetime value, flag it as a commercial problem, not a media problem. No amount of campaign optimisation fixes a channel where qualified leads simply don't convert to revenue at a sustainable cost — that's a pricing, sales-cycle or churn conversation, and sending it back to the media team wastes a review cycle.
Everything that doesn't trip either rule needs no action beyond noting the trend. Most weeks, for most channels, that should be the outcome — the scorecard is there to catch the exceptions, not to generate a decision every week for every channel.
Common pitfalls when building this
Cohort mismatch. Comparing this week's CPL against a CAC figure calculated from leads generated two months ago treats them as the same cohort when they're not. Label the time period each number actually reflects, not just the week the report was pulled.
Treating CPQL as fixed once defined. Qualification criteria drift as the business changes — a criteria set that made sense at seed stage often doesn't hold at scale. Revisit the MQL/SQL definitions on a quarterly cadence, not never.
Building it before the CRM data is trustworthy. A scorecard built on inconsistent historical UTM tagging or a lead source field that's only half-populated will produce numbers that look precise and are quietly wrong. Fix the CRM feedback loop first, even if that delays the scorecard by a few weeks. A scorecard everyone secretly distrusts is worse than no scorecard.
Where Zenko fits
The scorecard makes a structural problem visible that's easy to miss when you're only looking at CPL: a channel generating cheap leads that never clear the SQL-rate threshold is a channel where the traffic was never really qualified in the first place, no matter how it's targeted.
This is the layer Zenko's reward-based engagement model is built to improve, because the qualifying signal is baked into the action itself rather than inferred afterwards from a form fill. A completed learning module, a verified real-world action, an engagement that was honestly earned rather than extracted with a discount, all carry a stronger intent signal than a lookalike audience clicking an ad. On the scorecard, that tends to show up as a channel with a smaller CPL-to-CPQL gap than the account average, which is the specific thing the SQL-rate flag above is designed to catch.
FAQ
How often should the scorecard actually be reviewed? Weekly for CPL and CPQL once CRM data is flowing reliably. CAC should sit on the same weekly view as a trailing, directional figure, but the underlying number itself realistically only moves meaningfully on a monthly or quarterly basis, since it depends on sales cycles resolving.
What's the minimum CRM setup needed before building this? Consistent UTM tagging across every campaign, a lead source field populated at creation, and a written, agreed definition of what counts as an MQL and an SQL. Without those three, the scorecard will produce numbers that look precise but aren't trustworthy.
Should CAC be excluded from the weekly scorecard since it moves so slowly? No. Excluding it entirely means weekly decisions get made without any commercial-reality check at all. Include it as a trailing figure, clearly labelled with the period it reflects, so it's visible without pretending it's a live weekly number.
What should trigger a channel review versus just noting the trend? An SQL rate below roughly 10% regardless of CPL, or a trailing CAC that won't clear roughly a 3:1 ratio against lifetime value despite a competitive CPQL. Most channels, most weeks, should trip neither rule — if everything is flagged every week, the thresholds need recalibrating, not the channels.
This is the fourth piece in our acquisition-economics series. Catch up on the CPL playbook, the CPL vs CPQL vs CAC framework, or the high-CPL diagnostic guide if you missed them.