Experience Analytics

Measurement built into the experience

Most of what we ship comes with a system behind it: a CMS an editor logs into, a dashboard that shows what people did, and an API that feeds the numbers into something you already run. We have built web systems since 1995 and immersive experiences for most of that time, so the reporting comes from the people who built the app, and it is specified at the start rather than added once the build has shipped. The projects it comes from are listed under related work.

What we build

A CMS with live analytics

Our GLME framework runs our location and marker apps. Content and locations are managed in the GLME CMS, and the same system reports live analytics for each location, so you can see which stops hold people and which they walk past.

Dashboards, roles and APIs

The reporting side is a web system of the kind we build for clients in its own right: custom dashboards, user roles and content workflows, with an API so the data can go into an LMS, a reporting tool or a CRM instead of sitting in a second place. Some of the systems we first deployed nearly a decade ago are still running and still being updated.

Automatic scoring for training

In our AI-driven training simulations the system scores the decisions, words and actions it saw and gives feedback straight away. Those scores go into the same reporting, so a facilitator does not have to sit in on every session to know how a learner did.

How a project runs

We start with the questions, because they decide the events. A visitor attraction usually wants to know which parts of a site people reach and where they give up. A learning team wants completion and competence. A marketing team wants to know whether a demo held anyone's attention. Once those are settled, the developers record the right events as they build.

The experience sends its events to a system we build for you. You log into the dashboard or CMS yourself, export from it, and pull the data into your own tools through the API. Where a scheduled export is more practical than an integration, we do that instead.

Data protection

Headsets and phones can capture head and hand position, gaze, room dimensions, location and device identifiers. We collect what the question needs and nothing else. We decide early what is anonymous and what is identified, keep data only as long as it is useful, and handle it under UK GDPR in the same way as the user data in our web work. Where you need identified records, such as training completions tied to a named employee, we design for that on purpose.

If you are still deciding what is worth measuring, our consulting and workshops sessions are where that conversation usually starts.