Source labels
Auto Tag Testimonials by Source
Knowing whether a review came from your own form, an import or a campaign changes where you can use it. From Pro, one automation can branch on where each testimonial came from and add the matching label, so nobody has to remember to do it.
- A short, fixed list of source labels
- One branch per source, up to eight
- A catch-all branch for anything unexpected
The problem, solved
Where source labels go wrong in a team
Half our testimonials have no source label
Labelling by hand depends on whoever approves remembering, and the busiest week is when it gets skipped.
With StoryProof: From Pro, an automation that starts when a testimonial is received can add a label without anyone touching it.
We collect from more places than one rule covers
Forms, imports and campaigns each need their own label, and a single yes or no rule cannot tell them apart.
With StoryProof: A condition can hold up to eight named branches, so each source gets its own path and its own label action.
Everyone spells the labels differently
Google, google-review and G reviews end up as three labels, and every filter misses two of them.
With StoryProof: The automation writes the exact label you typed into the flow, every time. Agree the list once, then let the flow apply it.
We want to know which source is working
Without a reliable split by origin, the team argues from impressions about which channel brings in usable reviews.
With StoryProof: Analytics show where testimonials come from alongside their ratings and approval rate, and the labels let you pull each group out for a closer look.
Too many people can edit the flow
A well-meant change to one branch can quietly rename a label the whole library depends on.
With StoryProof: Roles let you keep editing rights with the person who owns the label list, and the logs show every run if something looks off.
Flip the switch to see how StoryProof handles each one.
Team checklist
Agree the labels, then build the branches
Work through it with whoever approves testimonials. The first group is a meeting, the second is ten minutes in the builder, the third is a habit.
Ticks stay in your browser. Nothing is saved or sent.
In StoryProof
Roll it out across the team
- You will need
- A StoryProof workspace on Pro or above
- An agreed list of source labels
- Edit access to automations for the label owner
- 1
Draft the flow on the canvas
Start a blank automation from the received trigger. Drafts save as you work and nothing runs until you publish.
- 2
Add the condition and its branches
Name each branch after its source, then give each one the label action for that source and the fallback its own label.
- 3
Tell the team what changed
Share the label list and ask approvers to stop adding source labels by hand, so you do not end up with duplicates.
- 4
Publish and watch the first week
Check the logs after the first arrivals from each source, then settle into the weekly unknown-label review.
What happens next: When a new form or campaign starts, add its branch before the first testimonial arrives.
Before you start
What automatic labels do not cover
Only new testimonials
The flow runs when a testimonial is received. Anything already in the library keeps whatever labels it has.
The source field is the product’s, not yours
This page does not list how StoryProof records origin. Build branches from what the condition step shows you in the builder.
Eight branches per condition
More sources than that means grouping some together or chaining a second condition on the fallback path.
Needs automations
Labelling by rule starts on Pro. Tags themselves are on every plan, applied by hand.
Logs are short-lived
Run history is kept for 30 days, so investigate an odd label soon after you notice it.
FAQ
Questions people ask
Short answers to what usually comes up next.
Should the label go on before or after approval?
Before. Starting from the received trigger means approvers see the source while they decide, and rejected testimonials are labelled too, which helps when you compare sources.
Can one testimonial get two source labels?
If your branches overlap it can. Write the rules so each testimonial matches one branch, and let the fallback catch the rest.
What about testimonials we import later?
Do not assume either way. After your next import, look in the logs for an enrolment from one of the imported reviews, and label them by hand if none appears.
Do source labels show on our website?
Labels are for organising in the workspace. What a widget shows is chosen separately.
Still have a question? Ask the StoryProof team or book a demo.
Label every testimonial on arrival
Collect testimonials in StoryProof and let one automation keep your source labels consistent.
Last updated 2026-11-18.