Measuring results
Everything that happens in your Gateway is measured and shown in ARShades Studio, under Analytics › Gateways. There is nothing to install and no tag to add: it is on from the first day.
The full walkthrough of the section — filters, charts, date ranges and the Excel export — is in Analytics for Gateways. What follows is what you can expect to find.
What you can see
| Area | What it tells you |
|---|---|
| Audience | Visitors, sessions, first-time visitors, average time per session, average engagement per visitor, sessions per visitor — with trends over time and ready-made periods. |
| Pages | Which pages were seen, how often, and how long visitors stayed on each. |
| Actions | How many times visitors started the experience, rotated a frame in 3D, took a photo, shared it, or tapped through to your shop or store locator. |
| Products | Which frames and which colour variants were looked at and tried on, and for how long. |
| Devices | The split between phone and desktop, and across operating systems and browsers. |
| Geography | Countries and cities, on a map and in a table. |
Reading it well
- Compare like with like. Use the ready-made periods, or the same number of days, when you compare two campaigns.
- Filter by Gateway. If you run more than one, you can look at one at a time or at all of them together.
- Follow the products, not just the traffic. Which frames get tried on the most is usually the most actionable number in the whole section, especially around a launch.
- Take it away. The section exports to Excel, with the parts you select.
Who sees what
Access follows the role you already have in Studio: Company Admins see every Gateway in the organisation, Team Admins those of their teams, and Members those in the subscriptions assigned to them.
The figures describe behaviour, not people: there is no login in a Gateway, and visitors are never identified by name. Precise location is only used when the visitor has explicitly agreed to share it; otherwise the country and city are approximate. The camera image used by the try-on is processed on the visitor's own device and is never sent to us.