Client operations and reporting guide

Client Reporting for Lead Gen: When ROAS Is Unsupported (And What to Show Instead)

July 5, 2026

If your agency runs lead generation campaigns without reliable downstream revenue attribution, a report that leads with ROAS is presenting a number the available data cannot support.

ROAS needs revenue attribution: the workflow must connect ad spend with attributable revenue. Ecommerce platforms often expose that relationship directly. Lead-generation businesses may need CRM, call, or offline sales data before the calculation is meaningful. When that link is missing, omit ROAS rather than showing a dash, zero, or estimate as if it were measured.

The dashes problem

Most reporting templates are built for ecommerce and reused for everything else. The result is a report where half the columns don’t apply: ROAS shows “—”, revenue shows $0, and the client is left wondering whether the campaign is broken or the report is.

A column of dashes isn’t neutral. To a client, it reads as something is wrong — either with the campaign or with the agency’s attention to detail. If a metric doesn’t apply to the client’s business model, it shouldn’t be in their report at all. (We learned this one directly: ClientSignal now shows an ROI column only for verticals that actually have revenue data, because a lead-gen report with an all-dash ROI column looked broken — even though the underlying data was correct.)

The metrics lead-gen clients actually care about

Strip the ecommerce columns and a lead-gen report gets simpler and more honest:

Leads. How many people raised their hand this week — form fills, calls, booked consults. This is the headline number.

Cost per lead (CPL). What each hand-raise cost. This is the number that should trend in your narrative: is it improving, holding, or drifting — and why?

Lead quality. The uncomfortable one. Fifty leads at $30 each is a terrible week if forty of them were tire-kickers. If you’re not reporting some signal of quality — qualified rate, booked appointments, whatever the client’s funnel calls it — your CPL number is only half a story.

Cost per qualified lead. When you can get it, this is the real metric. It’s the lead-gen equivalent of ROAS: the closest thing to “what does a real opportunity cost us?”

Close the loop with the client

Lead quality data lives on the client’s side — their CRM, their front desk, their sales team. Which means great lead-gen reporting requires something ecommerce reporting doesn’t: asking.

Build a lightweight loop into your reporting cadence: “Of the 32 leads we sent this month, how many turned into consults?” Some clients will answer because the question connects platform metrics with their sales process. When they do, the next report can distinguish generated leads from downstream outcomes.

One template does not fit all verticals

The broader lesson: reporting templates should follow the client’s business model, not the tool’s defaults. An ecommerce client should see ROAS and revenue. A law firm should see leads, CPL, and consults — and never a revenue column with a dash in it.

If your reporting tool can’t adapt its metrics to the vertical, you’ll spend your credibility explaining dashes. Explaining what CPL means in plain English — that’s a good use of a report. Explaining why the report shows metrics that don’t apply — that’s not.

ClientSignal writes plain-English weekly reports that match the client’s business — CPL and lead volume for lead gen, ROAS and revenue for ecommerce. Start free — 2 clients included →