38% of Your Ad Budget May Fund Ads That Don't Build Pipeline

In 43% of head-to-head A/B tests, the ad with the higher CTR produced fewer or more expensive SQLs than the ad it beat. This statistic comes from GrowthSpree's report, "The Paid Ads Pipeline Disconnect," which analyzed 1,412 ad variants tied to closed-won revenue across 96 B2B SaaS accounts and $14.2 million in spend. The punchline: CTR's correlation to revenue pipeline is negligible, while cost per SQL's correlation is r = 0.71.

If you've been reporting CTR as a leading indicator of pipeline health, this is a problem worth quantifying.

The Budget Misallocation Is Worse Than You Think

GrowthSpree's data indicates that CTR optimization pushes budget toward the wrong ads. Before closed-loop correction, the report estimates that 38% of ad spend flowed into the bottom two pipeline quartiles—ads that appeared efficient on CTR and CPL but generated almost no pipeline. Nearly two-thirds of high-CTR ads were classified as "clickbait traps": they attracted clicks but produced little downstream revenue.

Conversely, 56% of the best pipeline-driving ads had relatively low CTR. Under click-based optimization, those ads are often the first to be paused.

Ishan Manchanda, co-founder of GrowthSpree, stated, "Optimizing on CTR does not merely mismeasure. It actively moves budget toward high-CTR, low-pipeline ads and away from the low-CTR ads that quietly produce buyers." This is not just a measurement gap; it's a budget allocation failure with a compounding effect.

Channel-Level Correlations Make the Case Sharper

The report broke out CTR-to-pipeline correlation by channel, revealing weak correlations: Google Search at 0.18, Performance Max at 0.07, LinkedIn sponsored content at 0.04, and LinkedIn boosted posts at -0.02, indicating that higher CTR correlated with less pipeline.

This matters for how you structure reporting. If your LinkedIn campaign deck emphasizes CTR, you're presenting a metric with almost zero predictive value for what your exec team cares about. Worse, you might be making optimization decisions that degrade pipeline quality.

CTR still has a role as a diagnostic for message-market fit and creative fatigue. A significant drop in CTR across a segment signals issues with targeting or creative relevance. However, treating it as a proxy for revenue impact? The data says no.

Cost Per SQL as the Anchor Metric

The r = 0.71 correlation between cost per SQL and pipeline is the strongest predictor GrowthSpree found. When the team re-scored ad performance around pipeline-positive indicators and reallocated budget accordingly, average cost per SQL improved by about 44%—with no additional spend required.

This efficiency gain can withstand boardroom scrutiny. No new budget request or channel is needed—just a different optimization target.

The catch: measuring cost per SQL requires closed-loop reporting from ad platform to CRM. You need agreed-upon stage definitions across marketing and sales (what counts as an SQL, what disqualifies one) and the instrumentation to tie ad variants to those stages. Many teams lack this setup. The funnel benchmarks explain why this matters: visitor-to-lead conversion in B2B SaaS is around 1.1–2.5%, MQL-to-SQL conversion averages roughly 13%, and SQL-to-opportunity ranges from 30–59%. Every leak compounds. Improving CTR without fixing these stage conversions inflates activity metrics without moving pipeline.

What This Changes Operationally

If you change only one thing, change your optimization target. Stop optimizing campaigns to CTR or CPL as the primary metric. Optimize to cost per SQL, and if your attribution infrastructure can't support that yet, use MQL-to-SQL conversion rate as an interim proxy.

The hypothesis is falsifiable: if you shift budget from top-CTR ads to top-pipeline ads (measured by cost per SQL), pipeline volume per dollar will improve because you're funding ads that produce buyers. The trade-off: volume metrics (clicks, impressions, even MQLs) will likely drop. This drop is expected and correct.

Guardrails: monitor total SQL volume and cost per SQL weekly. If cost per SQL degrades by more than 20% for two consecutive weeks, revisit the reallocation. A secondary metric to watch is MQL-to-SQL conversion rate by channel.

Creative refresh cadence matters too. Industry guidance suggests testing new creative every 3–6 weeks to prevent CTR decay, but GrowthSpree's data indicates the more important question is whether your new creative drives SQLs, not just clicks. Test creative against pipeline metrics, not engagement metrics.

GrowthSpree's 44% cost-per-SQL improvement came from reallocation, not invention. The ads that built pipeline were already running; they were just starved of budget because they didn't win the CTR contest. Somewhere in your account, a low-CTR ad is quietly producing buyers. The question is whether your reporting setup lets you find it before you pause it.