Collection setup
Separate Testimonial Forms per Product
One form is simple to send and easy to maintain, until a customer of your accounting add-on answers questions written for your core product. A form per product asks better questions, until you have nine of them and nobody remembers which link is current. Decide the structure once, before the links spread through your emails and QR codes.
- Five questions about what you sell and to whom
- One form, a form per product, or split by brand
- Setup steps for the structure you land on
Decision helper
How should your collection forms be split?
Answer for your whole catalogue as it is today, not as it might be in two years.
Answers are scored in your browser and are not saved.
The problem, solved
What goes wrong with form structure, and the StoryProof fix for each
- Problem 1
One form, and now everything is jumbled
Testimonials for three products arrive through one link, and building a product page means reading every one to find the relevant few.
How StoryProof solves it
Tag each testimonial by product as you approve it, then choose exactly which ones go into each product page’s widget.
- Problem 2
Generic questions get generic answers
A form that has to suit every product cannot ask about the problem any one of them solves.
How StoryProof solves it
From Pro, multi-step forms ask several questions in one sitting, so a product’s form can walk through its own before and after.
- Problem 3
Two brands keep sharing one library
Separate businesses under one owner end up with testimonials, team members and widgets mixed together.
How StoryProof solves it
Give each brand its own space. The number of brand spaces and seats per space depends on your plan.
- Problem 4
Our markets speak different languages
A product sold in two countries might seem to need two forms, one per language, doubling the upkeep.
How StoryProof solves it
Collection forms are available in several languages on every plan, so language alone is not a reason to split forms.
- Problem 5
Each product needs its own printed code
Packaging, receipts and event stands for different products need to point at the right form.
How StoryProof solves it
Each collection link can be shared by hand or printed as a QR code, so every product’s form can go on its own insert.
The three structures compared
In StoryProof
Set up the structure you chose
- 1
Write the questions per product, or once
For one form, keep questions general. For several, write the two or three that only that product’s customers can answer.
- 2
Agree tags before the first answer arrives
Even with a form per product, add a product tag on approval. It keeps the library usable if forms are merged later.
- 3
Hand out each link where that product is used
Use the product’s link in its delivery email, and print its QR code on that product’s packaging or receipt.
- 4
Fill each product page from its own set
Build a widget per product page and choose the testimonials tagged for it.
What happens next: Review the structure when you launch or retire a product. Retiring a form is easier than renaming one that is printed on packaging.
Before you start
Before you split anything
What this does not cover, and what to check on your side. Better to know now than after launch.
- 01
Form counts differ by plan
How many collection forms you can run depends on your plan. Check the pricing page before planning one per product.
- 02
Old links keep circulating
A link printed on packaging or saved in an email template stays in use for years. Keep old forms working until those copies are gone.
- 03
Spaces are for separate brands
A brand space is a container for one brand and its seats. Use one only for a business that really stands apart, not for a product line.
- 04
More forms is not more testimonials
Splitting forms improves the questions, not the response rate. The ask and its timing still decide how many customers reply.
FAQ
Questions people ask
Short answers to what usually comes up next.
Can I use one testimonial form for several products?
Yes. Keep the questions general and tag each testimonial by product when you approve it, so product pages can still show only their own.
When does a separate form per product make sense?
When each product solves a different problem and you want to ask about that problem directly, or when each is sent at a different point, such as after a specific purchase.
Do I need a separate form for each language?
Not usually. Forms come in several languages, so one product form can serve customers in more than one market.
What about services rather than products?
The same logic applies. A bookkeeping client and a payroll client describe different outcomes, so separate forms help if both are significant parts of the business.
Can I merge forms later?
You can stop using one and send its customers another, but testimonials already collected stay as they are. Product tags make that switch painless.
Still have a question? Ask the StoryProof team or book a demo.
Get the structure right on day one
Set up your collection forms, tag what arrives and give every product page its own testimonials.
Last updated 2026-11-05.