Skip to content

Reading the dashboard

The analytics dashboard tracks how your published experiences perform. Data appears once visitors start opening your models. Until then a fresh workspace shows empty states instead of zeros.

Every number follows the period you pick (today, 7, 30 or 90 days, this or last month, or a custom range, all in UTC) and the project filter next to it. With a project selected the whole page narrows to that configurator. “All projects” reads the workspace.

A list card shows its first six rows. View Details at the bottom of the card opens the whole list in a wider window, with the columns the card has no room for.

Six figures, each with the value of the equal-length period before it, the change between them and a small line of its daily values:

  • Model opens: deduplicated opens, one per visitor, project and day. This is the figure your plan meters.
  • Sessions: distinct shopper sessions that opened a model, launched AR or configured.
  • Configured sessions: sessions that changed at least one option.
  • AR launches: native and in-page AR launches.
  • Added to cart and Orders once your storefront reports carts and orders (see Revenue tracking). Until then Enquiries and Time on model take their place.

Right under the row sits the visitor map, folded until you open it: every country that opened a model in the period, the sessions active right now, and a detail card for the country you pick on the map or in the list.

Shown once Shopify reports orders. Every order the store reports counts, whether a 3D session was behind it or not, so the comparison has an honest denominator:

  • Orders touched by 3D: the share of store orders attributed to a 3D session.
  • Average order with 3D against the average order without, and the lift between them.
  • Revenue per model open: verified revenue over model opens.

This strip is store-wide. The project filter does not narrow it.

  • Trends: one point per day for the metric you pick. Model opens, sessions, configured sessions and AR launches are always there, enquiries until your storefront reports carts and orders, carts and orders after that. The dashed line is the same day of the period before.
  • Devices: sessions by the device that opened the model.
  • Top countries: where the opens came from, as a share of the period. The visitor map under the headline row keeps the long tail and the live sessions.
  • Top products: the most opened products, each with the previous period and the change. Open the full list to search, sort and page through every product with its variants and SKUs.
  • Most configured projects: which configurators do the work: viewed and configured sessions, configure rate, picks, AR launches, carts and enquiries per project, with its products underneath. A project name is a shortcut for the project filter.

Views show that people came. Sessions show what they did:

  • Model opens, AR launches and total sessions: the three counts the other metrics are read against.
  • AR share of opens: how much of the attention becomes an in-room preview.
  • Time on model: the average time a shopper kept the model on screen after it rendered. Only visible time counts: a hidden tab pauses the clock. Sessions shorter than a second and longer than two hours are not counted.

Every model open records where the shopper came from:

  • Referring sites: the site the shopper was on before your page. Direct or QR is an open with no referrer: a typed link, a QR scan, a message.
  • Embedded on: which of your pages hosted the viewer.
  • Campaign sources: the utm_source on the link that brought the shopper. Add utm_source, utm_medium and utm_campaign to campaign links exactly as you would for any web analytics.

For an embed, the referrer and campaign are read from the page hosting it. For a direct viewer link or QR code, they are read from the viewer URL.

A launch is the last moment we can observe on native AR, and the dashboard says so plainly rather than inventing engagement numbers it cannot source.

  • AR launches and launch rate: how often a viewer becomes an in-room preview.
  • Launches by device: iOS (Quick Look), Android (Scene Viewer), other (desktop / WebXR).

iOS Quick Look and Android Scene Viewer are native operating-system apps. Once AR opens, your web page is no longer running, and neither Apple nor Google offers a callback to it. Photos, recordings, sharing and time spent inside native AR are therefore invisible to every web platform. Any tool reporting “AR engagement” is counting button taps.

WebXR is the exception. It keeps the session inside the page, so for WebXR launches the dashboard reports real session duration, completion, and in-session photos. These are labelled as WebXR-only and are never blended into the AR total.

The one thing native AR can report: the add to cart

Section titled “The one thing native AR can report: the add to cart”

A shopper in native AR is invisible to you. Adding to cart is the one action they can take that you can see, and it is a real conversion. The dashboard shows it as “Added to cart from AR”, and it counts toward the configurator funnel’s enquiries alongside the summary panel’s quote request button.

Enable it per project in WebAR settings → AR Add to Cart. The button text defaults to Add to cart. With the text left blank there is no button and the feature stays off.

The shopper’s tap reaches your page as a single togenar:ar-add-to-cart event on the embed, with the same event and payload on both platforms. Write one handler and wire it to your cart, as described in Add to cart.

Where the button appears
iOS (Quick Look) Inside the AR session
Android (Scene Viewer) The moment AR closes

The dashboard splits the taps by surface so you always know which one you are reading. The tap rate is over all native AR sessions, not iOS alone.

On iOS it is not free. The banner takes the slot Quick Look uses for its photo button, so turning it on means iOS shoppers can no longer screenshot or share the model from inside AR. You are trading organic reach for a measurable conversion. That is a merchandising decision, so the setting is off by default. (Android loses nothing because its button was never inside AR.)

iOS Safari only. Chrome, Firefox and Edge on iOS ignore rel="ar"’s banner, so no button is drawn there. AR still opens but cannot be measured.

This is the part a merchandiser acts on. It fills in for every published configurator, whether the shopper picks in the built-in panel or in one your page draws through the SDK’s select(). The na attribute switches analytics off for an embed.

  • Funnel: viewed → configured → added to cart → ordered once your storefront reports carts and orders, and viewed → configured → summary opened → enquired until then. Each stage shows its share of the step before. Stages are counted in distinct sessions, so a shopper who flips through nine fabrics counts once. Ordered is counted in orders. Enquired counts both ways of asking, the summary panel’s quote request button and the add to cart from AR, and splits them underneath. An AR tap from a session that never changed an option is reported in the AR section instead of the funnel.
  • Most-picked options: the share within each part of a project (“62% of everyone who chose a fabric chose linen”). This is what tells you which options to stock, promote, or retire. While all projects are shown, each row names its project. Over two weeks or more each row also draws its share week by week, so you see an option gaining or losing ground, not only its rank today.
  • Configure rate, cart rate (or enquiry rate) and options per session sit above the funnel.

The funnel says how many shoppers configured. This block says what they configured and what came of it. A session is placed on the full combination it ended on, with the options the shopper changed highlighted and the defaults dimmed.

  • Most chosen: the combinations most sessions ended on.
  • Most converted: the combinations that most often turned into an enquiry, a cart or an order.
  • Most abandoned: the combinations most sessions left without any of those.

Each row carries its sessions, how many converted and the rate, its enquiries, and its carts and orders once your storefront reports them. Enquiries are read from the quote requests themselves, so a lead counts even when the browser event behind it was lost. Carts and orders join the session through the same session id your page reports with Add to cart.

Parts sits next to it: for every part, the share of sessions that changed it from the default, and the share of abandoned sessions that touched it last. A part shoppers rarely change is a decision they are not making, and a part many abandoned sessions stopped on is where they stall.

This block is rebuilt once an hour from the raw events, so it trails the rest of the page by up to an hour. The footer says when it was last rebuilt.

Every action a shopper can take in the configurator, counted against the period before: option picks, summary opens, links shared, CSV exports, enquiries and the add to cart from AR, each with the sessions behind it. Under the table, when quote requests kept their session, the median time from a shopper’s first open to the enquiry.

The revenue attributed to the 3D experience, once your storefront reports it back. See Revenue tracking.

  • Verified revenue, orders and cart adds: from orders confirmed by the Shopify webhook. Orders your page reports with purchased() are listed separately as unverified. Counted for sessions that opened the model, not for your whole catalogue.
  • Revenue per session: the figure that answers whether the 3D paid for itself.
  • Revenue by channel: orders, units and revenue grouped by the campaign or referring site the shopper arrived from, counted from the orders your store’s webhook confirmed.

Amounts in different currencies are never added together. Each currency is totalled on its own. The block stays empty until your storefront reports its first cart or order.

Every number on this page is filtered to events a visitor produced. Your own work in the editor (uploading models, opening projects, previewing scenes) never counts as a session, a view, or a load.

Model reliability is measured on the shopper’s device and network, not on yours. A model that a visitor waited for and never got is recorded as a failed load (and is never billed as a view), so the success rate has a denominator that includes the failures.

  • Detailed analytics requires an active subscription: a lapsed workspace shows the gate message until renewal (Plans & billing).
  • Embeds can opt out per instance with the na attribute. Use it to keep internal dashboards and staging pages out of your production numbers (Attributes reference).