Cost per opportunity by ad campaign: how to calculate cost per SQL, opportunity and pipeline dollar

Ad platforms optimize and report on the conversions they can see: form fills, lead gen form submits, calls. In B2B, most of those leads never become pipeline, and the share that does varies widely by campaign. A webinar campaign on LinkedIn can produce leads at a third of the cost of a high-intent search campaign and still produce fewer opportunities per dollar.

When budget moves on cost per lead, it flows toward the cheapest form fills. When it moves on cost per opportunity and pipeline per dollar, it flows toward the campaigns that sales actually works. That is the shift CFOs and CROs ask for, and it is the core of a pipeline-first paid media report.

A worked example with example inputs for one quarter. These are illustration numbers, not benchmarks: use your own CRM data.

On cost per opportunity, search looks best. On pipeline per dollar, the LinkedIn account-list campaign wins because its deals are larger. Neither metric alone justifies a budget move; together they tell you to protect both and look harder at the Microsoft campaign, which has the same cost per SQL as Google but loses half its SQLs before the opportunity stage. That is a qualification or targeting question to take to sales, not a reason to cut by default.

With small numbers like six SQLs, treat any single quarter as directional. We look at rolling two-quarter cohorts before moving more than 20% of a campaign’s budget on down-funnel cost alone.

There are two honest ways to line up spend and opportunities, and mixing them is the most common reporting mistake we see.

The period view divides this quarter’s spend by opportunities created this quarter, whichever campaign or month their leads came from. It is simple and works when the sales cycle from lead to opportunity is short, a few weeks.

The cohort view divides the spend of a month by the opportunities later created from the leads that month generated. It is fairer for long B2B cycles, but the latest cohorts are incomplete, so show them with a note such as "cohort still maturing" rather than as a bad month.

Pick one per report, label it, and keep it for at least two quarters. Changing method every review makes trends meaningless.

None of these metrics work unless the CRM can tell which ad campaign created or influenced each contact, and when each contact reached each stage. Here is what to put in place in HubSpot or Salesforce.

1. Capture the ad click ID (such as Google’s GCLID) and all UTM parameters into hidden form fields, and store them on the contact or lead. Keep the first values; do not let later visits overwrite them.
2. Make campaign names in UTMs match ad platform campaign names exactly, so spend can be joined to CRM records without a mapping table that someone has to maintain.
3. Use lifecycle stages with dates. HubSpot records "date entered" and "date exited" for each lifecycle stage; Opportunity means the contact or company is associated with a deal. In Salesforce, use lead and opportunity creation dates and stage history.
4. Associate contacts with deals. In HubSpot, the Opportunity lifecycle stage means the contact or company is associated with a deal, so deal associations are what make opportunities countable by campaign. In Salesforce, use contact roles or Campaign Influence, which can automatically associate influential campaigns to an opportunity within an influence time frame you set.
5. Agree with sales on what an SQL and an opportunity are, in writing, and on who sets each stage.
6. Send qualified stages back to the ad platforms. Google’s offline conversion imports use the GCLID (or enhanced conversions for leads) to measure what happens after the click, so bidding can learn from SQLs and opportunities instead of form fills.

For attribution, HubSpot’s deal create and revenue attribution reports require Marketing Hub Enterprise and can include ad click interactions from connected LinkedIn and Google ad accounts. You do not need multi-touch attribution to start: a first-campaign rule for cost per opportunity plus an influence view for programs is enough for most budget decisions.

• Dividing all paid media spend by all opportunities, including those from outbound, partners and organic.
• Letting the last form fill overwrite the original source, which hands credit to retargeting and brand search.
• Counting opportunities that sales created for existing customers, renewals or upsells in new-business cost.
• Comparing a campaign’s cost per opportunity this month with spend this month when its cycle is 90 days.
• Using platform-reported spend for some channels and invoiced spend for others in the same table.

Most teams compute cost per opportunity once a quarter in a slide. It is far more useful while the month is running, next to pace: an on-pace campaign with a rising cost per SQL is the one to fix this week.

Pacing Console puts it there. On Pro, CRM lifecycle stages by campaign come from HubSpot, Salesforce, Pipedrive, or any CRM by CSV or API, so cost per SQL and per opportunity sit next to spend and pace. On Enterprise, pipeline and revenue (deals) by campaign are added, so cost per pipeline dollar is visible for every campaign in the same view finance uses for the forecast. The first month is free, and you can try the live demo before connecting anything.