Seven SAAS marketing key metrics and where the data comes from

What to take away

Start with the decision

A metric earns its place only if someone would act differently when it moves. If nothing changes at 8 per cent or 18 per cent, the number is decoration.

Write the decision next to the metric before you build the report. That single habit removes half the rows from most marketing dashboards.

Requests that arrive from outside the team face the same test. If a number would not change a budget line or a brief, it can wait.

The wider discipline is set out in the SAAS marketing: measurement and reporting guide 2027, which covers how reporting fits alongside finance cycles.

The seven metrics

1. Qualified pipeline

Count opportunities that sales accepts against your agreed definition, not every form fill. State the definition in the report itself.

2. Customer acquisition cost

Total sales and marketing spend divided by new customers in the same period. Label the period, because mixing quarters flatters the number.

3. CAC payback

Months of gross margin needed to recover acquisition cost. For example, a team paying £400 a month to acquire a customer on £100 monthly gross margin has a four-month payback.

4. Net revenue retention

Revenue from existing accounts this year against the same accounts last year. It shows whether growth survives without new logos.

5. Activation rate

The share of new accounts reaching the first value moment, defined in the product, not in marketing.

6. Organic sessions

Sessions from search and other unpaid channels, reported with the landing pages that earned them.

7. Channel value

What each channel contributes after accounting for the full journey, not just the last click. Google's guidance on getting the full value from your web and app channels explains why last-click attribution understates upper-funnel work.

Where the data comes from

Website metrics usually start in your analytics platform. The GA4 documentation for websites covers how events and sessions are collected, which matters when two teams quote different session counts.

CRM data supplies pipeline, CAC and retention. Finance supplies spend. Product analytics supplies activation.

Set the reporting window before you pull anything. A rolling 90-day view and a calendar quarter will disagree, and neither is wrong until someone assumes the other.

When a number crosses a boundary between systems, name the system of record. Ambiguity is where reporting arguments start.

Keep a short note of which system owns each field. A later change to CRM configuration should not silently rewrite history.

Regulatory and advertising evidence can also inform claims you make about results. The ASA and CAP research pages show the kind of evidence the regulator draws on when assessing advertising claims.

Numbered sequence to build the report

Teams that skip step three tend to repeat the same arguments monthly. The SAAS marketing measurement mistakes in England piece collects the common versions of that failure.

Definitions and drift

Definitions change when products change. A trial that becomes a freemium tier breaks every historical conversion rate overnight.

Keep a versioned definitions page. When a definition changes, restate the prior period rather than hiding the break.

A definitions page only works if it is dated and linked from the report itself.

Common questions

How many metrics should a board pack contain?

Fewer than most teams assume. Seven is workable if each one maps to a decision, and three to five is common for smaller software firms.

Should marketing report revenue or pipeline?

Both, but separately. Pipeline is a marketing commitment; revenue depends on sales capacity and timing outside marketing's control.

How often should definitions be reviewed?

At least once a quarter, and immediately after any pricing, packaging or trial change.

What if finance and marketing disagree on a number?

Reconcile to the system of record, then publish the difference. A visible gap is easier to manage than a quiet one.