VUE
Sign inGet started

Analytics

Every metric explained, and why the visitor count works the way it does.

The VUE teamLast updated

Every metric

MetricWhat it counts
ImpressionsThe embed was on a page somebody looked at. Not the same as a view of the 3D — with click to load on, most impressions never become one.
Viewer readyThe 3D actually loaded and was displayed. This is your view count.
InteractionsSomebody touched it — spun, zoomed or changed something. The single best measure of whether the embed is doing its job.
Type changesA different type or option was selected, recorded with which control and which value. Commercially the most useful number here.
Material inspectionsA visitor looked at a material’s detail.
AR launchesAugmented reality actually opened on the visitor’s device.
AR QR shownA desktop visitor asked for AR and got the QR code. Demand for AR from people who could not use it.
Call-to-action clicksA link out of the viewer was followed.
DownloadsA file was downloaded from the viewer.
ErrorsThe viewer failed for somebody. A number that is not zero is worth a ticket.
Screenshot to addThe analytics dashboard for a model, with the metric cards and the daily chart.

How visitors are counted

VUE sets no cookie and stores nothing on a visitor’s device. A visitor is identified by a salted hash of coarse signals — a truncated IP address, a reduced browser identifier and the domain the embed is on — and the salt is regenerated every day and never kept.

Three consequences, which you should know before reading the numbers:

  • “Visitors” means unique per day. The same person on Tuesday and Wednesday counts twice. There is no way to tell that it was the same person, by design.
  • There is no cross-site view. The same person seeing your embed on two different domains is two visitors, because the domain is part of the hash.
  • There is no funnel across sessions. You can see what happened within a session; you cannot follow anybody between them.

This is a deliberate trade. It costs precision and it buys a viewer that needs no cookie banner and adds nothing to your own privacy obligations. A page carrying a VUE embed does not have to mention us in its cookie notice, because there is nothing to consent to.

Which numbers are worth acting on

  • Interactions ÷ viewer ready is the health of the embed. Low means people are not realising it is interactive — try turning off show controls only on hover, or turning on the slow rotation on load.
  • Viewer ready ÷ impressions only matters with click to load on, where it tells you how many people chose to open it.
  • Which type values get selected is the number to take to a product meeting. It is a direct record of the sizes and finishes people ask for, from real specifiers, at no cost to them.
  • Combinations that were refused. When a visitor picks a combination the catalogue does not make, VUE moves them to the nearest one that exists and records that it had to. That is a list of products people wanted and you do not sell.
  • AR QR shown tells you AR demand from desktop. If it is high, the AR button is worth promoting on the page itself.

Where to find them

Analytics in the main navigation covers everything in the organisation. Each model has its own analytics tab, and each embed is counted separately — which is the reason to make one embed per product page rather than reusing one across several.

Daily totals are what the charts read, so figures for today firm up as the day goes on.

What we hold and for how long is in the privacy policy.