Product configurator analytics
Understand the journey. Improve the next decision.
See where a configured product progresses, where a buyer needs help and what reaches your sales team. Build a measurement plan your product, sales and factory teams can use.
Discuss your workflowFrom product interest to a confirmed order
- Eligible journeys—
- Started journeys—
- Valid journeys—
- Request journeys—
- Qualified journeys—
- Won journeys—
Measure one journey, all the way through.
Use unique eligible configuration journeys from one defined cohort. Count each journey once at each reached stage, in order. These are linked journeys, not raw page views, event totals, leads or order quantities. The worksheet calculates only after all counts and the cohort definition are supplied.
Specify the product, market, journey-start period and outcome cutoff. Include only journeys eligible for the same ordered path; late outcomes belong to that original cohort.
Enter an unformatted whole count, including a measured zero. Leave unknown counts blank.
Journeys where the configurator is available and the agreed measurement conditions are met.
Eligible journeys with a first meaningful product-changing action.
Started journeys reaching a saved state that passes the agreed commercial rules.
Valid journeys with at least one accepted request, deduplicated after server success.
Request journeys meeting the sales criteria recorded in the CRM.
Qualified journeys linked to at least one confirmed won order by the outcome cutoff.
Worksheet values stay in this page’s memory until reset or navigation. A JSON download includes your cohort and notes. They are not copied into the enquiry form.
Agree the counting contract first.
One unit throughout
This worksheet counts unique configuration journeys at every stage. Multiple sessions, revisions, form attempts, leads or orders do not create extra journeys. Use a separate report if your process requires users, sessions or order quantities.
A closed, ordered cohort
Every counted later stage must have reached all earlier stages in order. Define the start cohort and outcome cutoff before comparing periods. A general consultation that skips configuration belongs in another path.
Identity and source ownership
Where collection is permitted, link the measurement journey to the configuration ID created at meaningful start, then to revisions and CRM or order records. A pseudonymous ID is not a substitute for a privacy review. Keep personal information outside analytics payloads.
Accepted actions, once
A button click is not a saved configuration, accepted lead or won order. Use the authoritative server or business-system outcome, document retries and duplicates, and reconcile collection gaps rather than silently filling them with zero.
Sales cycles and coverage
A won order may arrive after the journey-start period. Follow the original cohort to an agreed cutoff and report immature outcomes, consent gaps, missing joins and integration failures. Do not imply that the worksheet reads your live systems.
Platform semantics
GA4 funnel explorations count users under their configured sequence rules. This worksheet counts journeys. Build a governed reconciliation layer if one user can create several projects; do not compare the two totals as if they had the same unit.
An event contract that explains the action.
configurator_view
- Trigger
- The configurator becomes available to the visitor.
- Purpose
- Defines the eligible audience for start-rate and performance analysis.
- Controlled parameters
- product_family, market, language, channel, device_class
configuration_start
- Trigger
- The user makes the first product-changing action.
- Purpose
- Separates passive viewing from an intentional configuration session.
- Controlled parameters
- configuration_id, entry_point, product_family, user_role
configuration_change
- Trigger
- A dimension, component, material, finish or accessory changes.
- Purpose
- Shows which decisions are explored without treating every click as a conversion.
- Controlled parameters
- option_group, option_id, previous_value, selected_value, price_delta
configuration_error
- Trigger
- A rule, validation or system condition prevents the requested state.
- Purpose
- Distinguishes helpful constraint guidance from technical or catalogue failure.
- Controlled parameters
- error_type, rule_id, step_id, recoverable, product_family
configuration_valid
- Trigger
- The current saved state passes the agreed commercial validation rules.
- Purpose
- Creates a stable denominator for quote, cart and handoff rates.
- Controlled parameters
- configuration_id, revision, price_status, required_fields_complete
configuration_save
- Trigger
- The system confirms an explicit save or share of a configuration.
- Purpose
- Records a recoverable specification; a resume is a separate action.
- Controlled parameters
- configuration_id, save_method, authenticated, revision
generate_lead
- Trigger
- The server accepts a quote, consultation or information request.
- Purpose
- Use generate_lead when its recommended meaning fits; deduplicate the accepted request instead of counting button clicks.
- Controlled parameters
- configuration_id, lead_type, value, currency, product_family
quote_generated
- Trigger
- The accepted system produces a quote or proposal from the saved configuration.
- Purpose
- Measures operational output separately from a form submission.
- Controlled parameters
- configuration_id, quote_id, revision, price_status, document_language
purchase_or_won_order
- Trigger
- The ecommerce purchase completes or the CRM opportunity becomes won.
- Purpose
- An internal outcome label: map a completed ecommerce purchase to purchase and a CRM win to the agreed lead-lifecycle event. Do not send both as duplicate revenue.
- Controlled parameters
- configuration_id, transaction_id, value, currency, channel
configuration_resume
- Trigger
- A saved configuration is restored successfully.
- Purpose
- Preserves project identity across sessions; track revisions only when the specification changes.
- Controlled parameters
- configuration_id, revision, session_context, resume_method
Define the formula before the dashboard.
Start rate
Started journeys ÷ eligible journeys
Whether the page and first interaction invite the eligible audience to begin.
Valid-configuration rate
Valid journeys ÷ started journeys
Whether people can reach a commercially usable product state.
Quote-request rate
Request journeys ÷ valid journeys
Whether a completed product state advances into a commercial conversation.
Qualified-lead rate
Qualified journeys ÷ request journeys
Whether captured demand fits the sales criteria defined in the CRM.
Won-order rate
Won journeys ÷ qualified journeys
How qualified configurator opportunities progress through the wider sales process.
Configuration error rate
Started journeys with a defined error ÷ started journeys
Specify the error class and deduplicate each journey. Expected product constraints and technical failures need separate rates.
Median time to valid state
Median(first valid timestamp − first start timestamp)
Compute within each successful journey; agree treatment of paused time and resumed sessions, then segment by complexity and role.
Resume rate
Unique saved projects resumed ÷ unique saved projects
Use a separate saved-project cohort and follow-up window. This diagnostic has a different counting unit from the main journey funnel.
Build evidence in six steps.
Define the decision before the event
Start with the business question, responsible owner and action. If no team will change a product rule, interface, campaign or follow-up because of a metric, collecting more parameters will not create useful insight.
Create stable configuration identity
Assign a configuration ID when meaningful configuration begins. Preserve it across save, quote, CRM and order records so the same project can be reconciled without placing personal information in analytics parameters.
Write an event contract
For every event, document the trigger, required parameters, owner, allowed values, consent behavior and test case. Version the contract when semantics change instead of silently reusing an event name.
Validate in the working journey
Test standard, edge, invalid, saved, resumed, mobile and integration-failure scenarios. Confirm events fire once, in the correct order, with the same configuration ID and without sensitive payloads.
Join customer and operational outcomes
Website analytics can show behavior, while CRM and order systems hold qualification and revenue. Reconcile them through governed IDs and documented attribution windows rather than copying every business record into the browser layer.
Review a diagnostic scorecard
Use a small weekly or monthly scorecard with totals, rates, segments and data-quality notes. Investigate meaningful changes before assigning a cause or publishing an outcome claim.
Compare like-for-like journeys.
Product and complexity
Product family, base model, size band, option count, price band and whether the configuration is standard or edge-case.
Audience and channel
Anonymous customer, dealer, salesperson or administrator; website, campaign, showroom, sales call or embedded partner site.
Market and experience
Country, language, price list, currency, device class, browser, viewport, connection class and consent state.
Commercial outcome
Quote type, qualification result, sales stage, loss reason, won order and time between configuration, contact, quote and decision.
Six reasons to question a chart.
Different denominators on the same chart
A quote rate based on all page visitors cannot be compared with one based on valid configurations. Name the denominator beside every rate.
Events named after interface labels
Button text changes. Track the business action—such as configuration save—then store the controlled interface context separately.
Revenue without configuration identity
If quote or order data cannot be reconciled to an exact configuration and revision, the report cannot explain which configured state progressed.
All validation treated as failure
A rule preventing an impossible combination may be correct guidance. Separate expected constraint messages from broken data, rendering or integrations.
Averages hiding mixed journeys
A fast standard product and a complex engineered product should not share one interpretation. Segment before diagnosing performance.
Correlation presented as causation
A higher order rate after launch can have many causes. Preserve the baseline, document concurrent changes and use controlled tests where practical.
Test the data, not just the dashboard.
A new configuration creates one stable configuration ID and does not expose customer names, email addresses or free-text notes in analytics parameters.
Changing five options emits five interpretable change events without duplicating the start or view event.
An invalid option produces the agreed validation event and the user can recover without losing the current valid state.
A saved configuration resumes with the same configuration ID and a new session context.
A failed form attempt is not a lead. A server-accepted request is measured once after retries and reconciles to a matching CRM record.
The quote and order retain the configuration ID, revision and commercial status required for reconciliation.
Consent denied, withdrawn and granted states produce the documented collection behavior in each target market.
Dashboard totals reconcile to raw events and source-system records within the agreed tolerance and time window.
Custom software for manufacturers
Connect the configurator to the work behind it.
We specialise in complex products. Configurix builds custom configurators and business or factory software around your catalogue and workflow: lead qualification and CRM, appointments and calendars, pricing and quotes, materials and BOM, orders, jobs and invoicing. Analytics and integrations are scoped around the systems, permissions, product rules and commercial outcomes your team actually needs.
CRM and qualified leads
Capture the selected product, dimensions and options with each enquiry. Qualify by product fit, project requirements and commercial readiness, then assign the next action to the right salesperson.
New enquiry
Product configurator analytics
Product fitQualified
Product configurator analytics
RequirementsProposal
Product configurator analytics
Next actionCalendars and appointments
Let a configured project continue into a sales consultation, technical review, survey or installation appointment. Connect calendars, responsibilities and reminders to the same customer record.
- 09:00Project review
- 11:30Technical review
- 14:00Production planning
Bill of materials and factory data
Map product selections to component codes, quantities, materials and cut lengths. Build the sales or manufacturing BOM your team needs, with revisions and production review rules defined for your products.
| Component | Quantity |
|---|---|
| FRM-01Configured components | 1 |
| PNL-02Materials and quantities | 1 |
| KIT-03Agreed operations | 1 |
Mapped to your product codes
Live prices and branded quotes
Apply your own formulas, price lists, dealer margins and approval rules. Generate a quote containing the saved specification, product images, commercial terms and a clear customer approval step.
Quote revision
Orders, jobs and production
Carry accepted choices into order lines and assigned jobs. Keep product revisions, required approvals, documents and delivery tasks together so sales and the factory work from the same specification.
- Accepted quote01
- Configured order02
- Production job03
- Installation04
Invoicing and accounting
Connect accepted orders to deposits, invoice drafts, payment terms and your accounting workflow. Agree which system issues the invoice and how references and confirmed payment status return to the project.
Product configurator analytics
Built for your website. Connected to your systems.
Launch a branded configurator in your existing website or a custom sales portal. Connect CRM, ERP, PIM, ecommerce, calendars and accounting through available APIs, webhooks or agreed imports. We define the data, permissions and responsibilities for each connection with your team.
- 01Your website
- 02Configurator
- 03CRM & calendar
- 04ERP & accounting
Choose the workflows your implementation needs. We build and validate them against your products, documents and target systems.
Discuss your workflowProduct configurator analytics questions
Build a measurement plan around your products.
Tell us about your product range, sales process and current systems. We can scope a custom configurator and software workflow with the events, CRM links, operational outputs and acceptance tests you need.