Skip to content
rj. Rudi Jantos
Menu
← All field notes

From campaign reporting to pipeline: what to measure in B2B

Separate clicks, leads, qualified opportunities, and revenue so your B2B campaign report supports a useful decision.

By Rudi Jantos · Published September 15, 2026

  • measurement
  • pipeline
  • b2b

A campaign report is useful when it helps you decide what to do next. The simplest way to improve one is to stop treating clicks, form submissions, and sales opportunities as interchangeable outcomes.

This is a reporting framework, not a claim that every sale can be attributed precisely. Your definitions, consent choices, CRM processes, and sales cycle all affect what you can observe.

Start with four distinct questions

  1. Reach: Are the intended people arriving?
  2. Response: Are they taking the next step?
  3. Qualification: Does sales consider the enquiry relevant?
  4. Progression: Does the opportunity advance, close, or stall?

Each question describes a different part of the journey. A cheap form submission may be poor value if the person is outside your target market. An expensive enquiry may be worthwhile if it becomes a valuable customer. Neither conclusion follows from cost per lead alone.

Use a small shared scorecard

Metric Working definition Decision it supports
Spend Campaign cost within the stated period How much did the test cost?
Enquiries New, deduplicated requests Did the offer prompt a response?
Qualified opportunities Records accepted against agreed criteria Did the right buyers respond?
Cost per qualified opportunity Spend divided by qualified opportunities How efficiently did the campaign create sales conversations?
Closed revenue Revenue from won opportunities, using a stated accounting convention What commercial outcome is recorded?

State your definitions next to the report. If the denominator is zero, show “no qualified opportunities” rather than an apparently meaningful efficiency number.

Compare cohorts, not unrelated date ranges

A cohort is a group that entered the process in the same period. If an enquiry from March closes in June, comparing June revenue only with June advertising spend can hide the work that created the sale.

Keep two views: activity during the current reporting period, and the progress of enquiries created in each earlier period. The first helps run the team; the second helps assess how demand turns into business over time.

Do not call a recent cohort a failure simply because it has not had time to complete the normal sales cycle. Equally, do not keep an old opportunity open indefinitely without checking whether the buying process is still active.

An illustrative example

Campaign A costs €1,000 and creates 20 enquiries, of which two become qualified opportunities. Campaign B costs €1,000 and creates eight enquiries, of which four qualify.

A has the lower cost per enquiry: €50 compared with €125. B has the lower cost per qualified opportunity: €250 compared with €500.

Those numbers are hypothetical. They show why the definition of success changes a budget decision; they do not establish that B will generate more revenue. Opportunity value, win rate, and time to close still matter.

Explain discrepancies instead of hiding them

Ad platforms, website analytics, and the CRM can count different events over different windows. Document which system answers each question. For example, your CRM can record sales acceptance while a campaign platform records its own attributed conversions.

Keep missing or unknown sources visible. A report with an explicit “unknown” category is more honest than one that allocates every sale to a channel without evidence.

For naming consistency, use a shared campaign tagging standard. For a launch review, start with the tracking audit scorecard.

Finish with a decision

End the report with three short statements: what changed, what you believe explains it, and what you will test next. Distinguish an observation from an interpretation.

“Lead volume increased” is an observation. “The revised offer caused the increase” is an interpretation that may need a controlled test. Keeping that distinction visible makes your reporting more useful and your decisions easier to revisit.

Need help applying this to your stack?

If your team needs a practical audit and implementation plan, start here.

Related resources