Skip to main content

Measuring collection

Testimonial Program Metrics and KPIs

Counting testimonials tells you very little. A program with forty vague one-liners is doing worse than one with ten specific stories. These metrics measure the collection itself: who replies, how much of it you can use, and how long it waits. Score how well your team tracks each one.

  • Six collection metrics worth a monthly look
  • Score how well your team tracks each
  • A plain formula for every number
Use the free toolStart tracking collection (opens in a new tab)
Score: Program tracking
  • You know how many requests went out last monthYesPartlyNo
  • You can state last month’s response rateYesPartlyNo
  • You can say what share was usableYesPartlyNo
  • You know how long submissions waitYesPartlyNo

6 checks. Each one you miss comes with a fix.

Free tool, no sign-upTry it below

The problem, solved

Why testimonial reporting misleads, and how StoryProof gives you the inputs

  • All we report is the total

    A rising count can hide a falling reply rate: you are just sending more requests to get the same few answers.

  • Half the submissions are not usable

    Polite one-liners count the same as specific stories, so the number looks healthy while the homepage still lacks good proof.

  • Testimonials wait weeks for approval

    A testimonial sitting in a queue is not on a page doing any work, and the customer wonders why theirs never appeared.

  • Every testimonial comes from one segment

    Forty testimonials from small customers do nothing for an enterprise buyer looking for someone like them.

  • We cannot say who was asked

    Without a record of requests, a response rate is a guess.

Flip the switch to see how StoryProof handles each one.

Six metrics and how to work them out

Pick a fixed period, usually a month, and use the same one every time.

Formulas are suggestions. Agree your own definitions once, then keep them fixed so months compare.
MetricFormulaWhat it tells you
Response rateTestimonials received divided by requests sentWhether the ask, timing and audience work
Usable shareTestimonials you would place on a page divided by all receivedWhether your questions draw out specifics
Time to approvalDays from submission to approved or rejected, as a medianWhether the review step is a bottleneck
Segment coverageSegments with at least one recent usable testimonial divided by segments you sell toWhere buyers will not find someone like them
Format mixCount of video, audio and written testimonialsWhether you have the formats your pages need
FreshnessShare of published testimonials newer than your cut-off dateWhether the proof on your site is going stale

Scorecard

How well does your team track the program?

For each metric, answer yes if you could report it this week, partly if you could estimate it, no if you could not.

You know how many requests went out last month
You can state last month’s response rate
You can say what share was usable
You know how long submissions wait
You can list segments with no recent testimonial
You know how much published proof is old

Scored in your browser. Nothing is sent or saved.

In StoryProof

Collect the inputs in StoryProof

  • You will need
  • A StoryProof workspace
  • An agreed reporting period and segment list
  1. 1

    Send from a counted list

    Keep this month’s candidates in a smart list. The size of the list is your requests-sent number.

  2. 2

    Review on a fixed day

    Submissions wait in the queue until someone decides. A weekly slot keeps time to approval short and easy to track.

  3. 3

    Tag usable, segment and format at review

    Three tags per testimonial give you usable share, segment coverage and format mix without a separate spreadsheet.

  4. 4

    Open the dashboard for the monthly look

    The analytics dashboard comes with every plan. Pair it with your tag counts to fill the six metrics.

What happens next: Report two or three metrics, not six. Pick the ones tied to this quarter’s problem, such as usable share if answers are thin.

Before you start

What these numbers will not show

  • They measure collection, not sales

    A healthy program can still sit on pages nobody visits. Measure page impact separately with a test.

  • Usable is a judgement

    Agree what counts as usable, or each reviewer will tag differently and the share will swing.

  • Small numbers move a lot

    With ten requests a month, two extra replies change the response rate sharply. Look at a quarter, not a single month.

  • Tags only count what you tag

    If reviewers skip tagging, segment and format metrics are wrong without anyone noticing.

  • Do not set targets for customers

    A team chasing a response rate target may pressure customers. Use the numbers to improve the ask, not to push harder.

FAQ

Questions people ask

Short answers to what usually comes up next.

What is a good testimonial response rate?

There is no reliable public benchmark; it depends on audience, timing and how personal the ask is. Measure your own for a few months and work to raise it.

Which metric should we start with?

Requests sent, because every other rate depends on it. Then usable share, which tells you whether your questions work.

Should testimonial count be a KPI at all?

As context, yes. As the only target, no: it rewards volume over quality and says nothing about coverage or freshness.

How do these metrics relate to conversion?

They are upstream. Good collection metrics mean you have the right proof; whether that proof lifts sign-ups is a separate test on the page.

How often should we report them?

Monthly for the team, quarterly for leadership. Collection numbers are noisy week to week.

Still have a question? Ask the StoryProof team or book a demo.

Measure the program, not just the pile

Send from counted lists, tag at review and keep the inputs for every metric in one place.

Start tracking collection (opens in a new tab)

Last updated 2026-11-05.