How much of what you collect is usable?
Track Your Testimonial Approval Rate
The share of submitted testimonials you approve is the quietest signal in your whole program. A falling rate means your requests, your forms or one source are producing material you cannot use. A rate near 100% can mean nobody is really reading. Score how your team tracks it today, then set up the monthly habit that turns the number into a decision.
- Six habits that make the number meaningful
- A score and the next fix to make
- Reasons recorded, not just counts
The problem, solved
What hides behind an approval rate nobody tracks
Analytics are included on every plan. The alert and auto-approval fixes need a plan with automations.
We do not know how many we approve
Teams remember the great testimonials and forget the pile they quietly left in the queue.
With StoryProof: StoryProof analytics show how many testimonials you collect and how often you approve them, on the dashboard every plan includes.
The rate fell and nobody knows why
A number without reasons cannot tell you whether to fix the form, the request or the audience.
With StoryProof: Tags are on every plan. Give each rejected or held testimonial a reason tag, such as off-topic, too short or needs consent, and count the tags monthly.
Our rate jumped after we automated
A sudden rise can be a rule approving things a person would have held back.
With StoryProof: From Pro, auto-approve takes 4 and 5 star testimonials that include text. Sample what it approved each month and check you would have approved them too.
Rejections happen and nobody hears about it
One moderator rejects a run of submissions from the same campaign, and the person running that campaign never learns.
With StoryProof: An automation can start when a testimonial is rejected and send an in-dashboard notification or email up to ten teammates.
Borderline ones get waved through
Under time pressure, unclear submissions are approved because rejecting feels harsh.
With StoryProof: Nothing goes public until approved, and an automation can flag a testimonial so borderline cases get a second look instead of a default yes.
One source drags the rate down
A workspace-wide average hides that one channel produces most of the unusable submissions.
With StoryProof: Analytics also show where testimonials come from. Read approvals next to sources, so you fix the channel rather than the whole program.
Flip the switch to see how StoryProof handles each one.
Approval rate scorecard
How well does your team track approvals?
Answer yes, partly or no for each habit as it is today. The score shows how much the number can tell you, and each gap comes with its fix.
Your answers stay in this browser tab. Nothing is saved or sent.
Reading a change in the rate
In StoryProof
The monthly approval review
- You will need
- A written definition of the rate
- A short list of reason tags
- Thirty minutes once a month
- 1
Clear the queue first
Approve or reject everything pending from the month, using a reason tag on each rejection.
- 2
Read the figures in analytics
Note how many testimonials came in, how often you approved them and where they came from, in your running log.
- 3
Count the reason tags
The most common rejection reason is your next fix: a prompt, a request, a source or a consent step.
- 4
Sample the automation
If auto-approve runs, read a handful of its approvals and confirm they meet your standard.
- 5
Make one change
Change one thing per month, so next month’s figure tells you whether it worked.
What happens next: Share the figure and the one change with whoever runs requests. They are the people who can move it.
Before you start
What the approval rate cannot tell you
No benchmark is given
This page publishes no typical approval rate. Compare yourself with your own past months.
Dashboard details are not listed
This page does not claim the dashboard shows the rate as a percentage or over a chosen date range. Note your own figures each month.
Higher is not always better
A very high rate can mean weak moderation as easily as great testimonials.
Alerts need automations
Rejection alerts and flagging are automation actions, available from Pro.
FAQ
Questions people ask
Short answers to what usually comes up next.
What is a good testimonial approval rate?
There is no published standard. A stable rate with known rejection reasons is healthier than a high rate nobody can explain.
Should imported reviews count toward the rate?
Keep them separate. You chose to import them, so they would push the rate up without telling you anything about your requests.
Do pending testimonials count as rejected?
No. Clear the queue before reading the figures, or count pending items separately, so a slow week does not look like a quality problem.
Will auto-approve make the rate meaningless?
Not if you sample its approvals monthly. The rule approves 4 and 5 star testimonials with text and leaves the rest for people, so the human decisions are still there to read.
Still have a question? Ask the StoryProof team or book a demo.
Know how much of what you collect is usable
Collect, approve and tag in one place, and read the figures every month.