Measure a configurator journey by the decisions it helps buyers make.
Build a practical measurement plan around valid selections, useful briefs and sales handovers, then use the evidence to improve the experience.
Define one outcome that the sales team considers useful.
Define a useful outcome before counting activity
A configurator can attract plenty of clicks without giving your sales team a better starting point. Begin by describing a useful outcome for your business. It might be a buyer who selects a valid product, understands the estimate scope and submits a brief with the missing facts clearly identified. Write that outcome in terms your product and sales teams can recognize.
Then choose a few stages to measure: opening the product experience, making a meaningful selection, reviewing the summary and completing the intended handover. Define each event precisely. Loading the page is different from changing a product option; opening a form is different from sending an enquiry. Avoid treating every interaction as equal progress toward a sale.
Make the numbers describe the same journey
Use a consistent starting point and time period when calculating a rate. If you divide completed briefs by visitors who opened the configurator, label the result that way. Do not compare it directly with a rate calculated from all website visits. Decide how repeat sessions and returning buyers should be handled so that reopening a saved design does not become a misleading new start.
Separate the product families and the devices where those differences help explain behavior. A garden room enquiry may involve more planning questions than a pergola finish comparison. A phone visitor may explore now and continue on desktop later. Review sample sizes before drawing conclusions, and write down what the available data cannot tell you about a customer’s intent.
Connect event data to the quality of the brief
Ask the sales team to review a sample of incoming briefs against a short, consistent list: valid product choices, usable dimensions, clear estimate assumptions and an identifiable next question. Record whether the salesperson could continue the conversation or had to collect the same information again. This adds context that a completion counter cannot provide.
Observe a few customers completing a realistic task as well. If people repeatedly miss the mounting arrangement or misunderstand an exclusion, use that finding to improve the relevant step. A drop in activity at a question might signal confusion, a product mismatch or an intentional exit. Event counts can point to a place to investigate; they do not explain the reason by themselves.
Use the findings to change one decision at a time
Choose a specific issue and a change you can assess. For example, if buyers reach the summary without understanding whether installation is included, revise the wording beside the estimate and review new briefs for that misunderstanding. Record when the change went live, which products it affected and whether campaigns or traffic sources changed at the same time.
Plan data collection around your actual analytics and enquiry setup. Keep contact details and free-text customer notes out of general event labels; agree what information is needed, how long it is retained and who can review it. Sales Visualizer’s current demonstration saves drafts locally and does not send enquiries, so its activity cannot be reported as delivered leads or sales. A production measurement plan needs a working handover before those outcomes can be evaluated.
Worked example: a clearly defined completion rate
For a hypothetical review period, 120 sessions make a product selection and 30 reach a completed brief. Using those sessions as the denominator gives a 25% selection-to-brief rate. The figures are invented to explain the calculation, not a performance benchmark.
- Keep the definition and review period beside the rate.
- Review the 30 briefs for usable selections and unresolved questions.
- Confirm which briefs were actually delivered before counting received enquiries.
Your review list.
- Define one outcome that the sales team considers useful.
- Name each event and keep the denominator consistent.
- Review brief quality and observe where buyers misunderstand choices.
- Document one improvement and assess it against the same definitions.
See the next step
in Sales Visualizer.
Explore an illustrative experience, then review your own range and requirements with your team.
Review your product experience