Web analytics tells you
- How many people opened the lineup page
- How long they stayed and where they came from
- Which page they left from
- That a form was submitted
Demand data
Every build a customer assembles is a vote — for a floorplan, a finish, a package, a price point. The configurator counts those votes, and once a quarter it tells you what next season should look like.
The floorplans and packages buyers keep assembling — ranked, months before the order book shows it.
Options nobody picks cost you inventory, supplier minimums and catalogue space. Now you can see them.
Demand splits by place. What Texas configures is not what Idaho configures, and the lot can follow that.
The step where builds are abandoned is usually a price jump or a missing option — both of them fixable this week.
Quarterly report
You do not have to log in, filter anything or learn a dashboard. Every quarter a short report lands in your inbox: what rose, what fell, what nobody chose, and where builds were abandoned — with a note from us on what we would change.
It is the part clients keep quoting back to us a year later. Nobody else can tell them what their own buyers wanted and did not order.
See a sample reportYours. We collect what buyers configure on your own places, use it to run your configurator, and never pool it with anyone else's. Nothing is sold on, and nothing leaves for another brand.
You almost certainly have web analytics already. It can tell you that four hundred people looked at a page — never which build they wanted.
Web analytics tells you
Demand data tells you
Both are useful. One is about traffic, the other about production — and only the second one changes what you build.
It starts counting from the day your configurator goes live — and the first report lands a quarter later.