You have tags. Now they need rules.
Tag Naming Conventions for Testimonials
A tag scheme says which families of tags you keep. A naming convention says how each tag is spelled, so that three people tagging on three different days produce one tag, not "Enterprise", "enterprise-customers" and "ent". Fill in your families and the builder writes a one page convention, a rename map for the tags you already have, and a short note teammates send before creating a new tag.
- One prefix style for every family
- A rename map for tags already in use
- A request note before any new tag
Convention builder
Write your tag naming convention
Type your families as you want them to read, comma separated. Pick a prefix style; the documents below follow it everywhere.
- Naming convention (one page)
Pin this where the team tags. Every rule should be checkable by eye.
FORMAT Every tag is family: value, for example audience: [mid market] Families allowed: [product, audience, objection, format, use] SPELLING 1. Lower case only. 2. Spaces between words in the value, no hyphens or underscores. 3. Singular nouns: "agency", not "agencies". 4. Full words, no internal abbreviations unless the whole team says them aloud. 5. The customer’s word for a thing, not your product team’s. CONTACT TAGS Tags on contacts start with "contact: " so they never look like testimonial tags. TEMPORARY TAGS Campaign or one off tags start with "temp: " and the month, and are removed at the review. NEW TAGS Ask [Priya] first. Reviewed [first Monday of each quarter].
- Rename map for existing tags
Fill one row per current tag before you change anything. Rules and widgets may refer to the old names.
CURRENT TAG > CONVENTION TAG > ACTION [Enterprise, enterprise-customers, ent] For each current tag write: - the convention name it becomes - merge (several old tags become one), rename (one becomes one) or retire (no longer needed) - any automation, widget or saved filter that uses it Change the automations first, then retag the testimonials, then remove the old tag.
- New tag request note
A three line message to {owner}. If it cannot be written, the tag is not needed yet.
Subject: New tag request
Hi [Priya], Proposed tag: (family and value, following the convention) Why: (the search or placement it will make possible) Closest existing tag and why it does not fit: It would apply to these testimonials today:
- Quarterly tag review
Run [first Monday of each quarter], led by [Priya]. 1. Sort the tag list alphabetically. Near duplicates sit next to each other. 2. Any tag that breaks the convention goes on the rename map. 3. Any "temp" tag older than its month is removed. 4. Any tag used on fewer than three testimonials is questioned: merge it or keep it on purpose. 5. Allowed families checked: [product, audience, objection, format, use]. A new family needs a reason written down.
The documents are built in your browser from what you type. Nothing is saved or sent.
The problem, solved
Why tag names drift, and the StoryProof side of the fix
- Problem 1
Filtering finds only half of them
A filter on one spelling skips every testimonial tagged with another, so the team concludes there is no proof for a segment that has plenty.
How StoryProof solves it
Every testimonial lands in one library where you filter by tag. One spelling per idea makes that filter complete.
- Problem 2
Renaming broke an automation
A rule that labels or features testimonials refers to a tag by name, so tidying the list can quietly change what the rule does.
How StoryProof solves it
From Pro, automations can add or remove labels on testimonials. List each rule on the rename map and update it before retagging.
- Problem 3
Contact tags look like testimonial tags
A "vip" tag on a contact and a "vip" tag on a testimonial mean different things, and someone filters on the wrong one.
How StoryProof solves it
Automations can also add and remove contact tags. A fixed prefix for contact tags keeps the two lists apart at a glance.
- Problem 4
Every new teammate adds tags
Someone new tags in their own words for a month before anyone notices.
How StoryProof solves it
Roles on every plan give each teammate only the parts of the workspace they need, and the convention tells them which tags already exist.
- Problem 5
Tags are added long after approval
Tagging a batch weeks later is when shortcuts and new spellings creep in.
How StoryProof solves it
Every submission waits in the approval queue, and tags are on every plan, so tag at the moment you approve, with the convention beside you.
Choosing a prefix style
Either works. What matters is that one is chosen and nothing else is allowed.
In StoryProof
Move your library onto the convention
Step 1 of 4
Publish the convention first
Share the one page convention before touching any tag, so nobody creates a new variant during the clean up.
Step 2 of 4
Update automations that use tags
For each rule on the rename map, change the label it adds or tests to the convention name.
Step 3 of 4
Retag, then remove
Filter by each old tag, add the convention tag to every result, and only then drop the old one.
Step 4 of 4
Tag new work at approval
From now on, every testimonial gets its convention tags when it is approved.
Before you start
What StoryProof will not enforce
No format check on tag names
StoryProof does not reject a tag that breaks your convention. The rules live in your document and your review.
No bulk rename is claimed
This page does not claim a one click rename or merge of tags. The migration is retag by filter, then remove the old tag.
Check automations by hand
Whether a rule follows a renamed tag is not something this page claims. Update every rule on the rename map before retagging.
Widgets need checking too
If you used a tag filter to choose a widget’s testimonials, rerun that filter with the new name and confirm the widget still holds what it should.
FAQ
Questions people ask
Short answers to what usually comes up next.
Do we need a naming convention if we only have a few tags?
Below about twenty tags and one person tagging, a short list on a sticky note is enough. The convention earns its keep once a second person starts tagging.
Should tag names be singular or plural?
Pick one and write it down. Singular is easier to keep consistent, because it matches how you describe one testimonial: this is an agency testimonial.
How do we stop people creating new tags?
You do not need to stop them, only slow them down. A three line request to the tag owner catches duplicates early, because writing why a tag is needed reveals the existing one that fits.
What is the difference between this and a tag scheme?
The scheme decides which families you keep, such as product, audience and objection. The convention decides how every tag in those families is spelled and who can add one.
Still have a question? Ask the StoryProof team or book a demo.
Give your tags one spelling each
Write the convention, migrate with the rename map, and tag every new testimonial as you approve it.
Last updated 2026-11-20.