Insights · guide

How to track where people leave your VR experience

Drafted with Insight · edited by The WE ARE VR team

development

Most VR teams collect opinions and forget to record behaviour.

I wrote this because memory becomes unreliable during a busy Jozi activation. A small event log gives your team something concrete to review afterwards.

What's the problem?

A participant removes the headset halfway through your experience. The facilitator asks what happened, and the answer is usually vague: "I was finished" or "It felt strange".

By closing time, the team remembers several exits but cannot place them. Did people leave during onboarding, after movement began, or while waiting for a scene to load?

A completion rate alone will not answer that. If 30 people start and 18 finish, you know there is a drop-off. You still do not know where to work.

Teams sometimes respond by tracking everything: gaze direction, controller movement, button presses and frame rates. That creates a large pile of data before anyone has agreed on a useful question. (Spreadsheets also have feelings, mostly resentment.)

Start with three records: start, completion and exit point.

What's the solution?

Add a small event log to the experience. An event is simply a recorded action with a time and location.

Each log entry needs four fields:

  • A random session ID, such as JHB-042
  • The event, such as start, complete or exit
  • The current scene or chapter
  • A timestamp

Do not use the participant's name, email address or phone number. A random session ID lets you follow one run without collecting personal information.

Your log might look like this:

10:14:05, JHB-042, start, onboarding

10:16:31, JHB-042, enter, taxi-rank-scene

10:17:02, JHB-042, exit, taxi-rank-scene

For a small pilot, write these entries to a CSV file. CSV means comma-separated values, a plain text format that opens in Google Sheets or Excel. You do not need a full analytics platform yet.

Add one logging call when each scene starts. Add another when the experience completes. If the application closes early, record the last active scene as the exit point.

Facilitators can add an exit reason after the session. Keep the choices short: participant stopped, discomfort, technical fault, facilitator stopped, or unknown. A printed tally sheet beside the laptop can handle this during a small activation.

Imagine 40 people try a VR piece in Braamfontein. Twelve leave during the same scene. Eight of those exits happen within 30 seconds of artificial movement beginning.

That pattern gives the team a useful place to investigate. You could shorten the movement, reduce its speed, offer teleport controls, or warn participants before it starts. Test one change, then compare the next group.

The log does not explain every exit. It tells you which scene deserves attention first.

What's next?

  1. Name every scene or chapter in your experience. Use labels your whole team understands.
  2. Record start, complete and the last scene reached for ten test sessions this week.
  3. Open the CSV in Google Sheets, count exits by scene and inspect the busiest exit point together.

Share what your log reveals, or send us a question about measuring your next Jozi XR activation.

The WE ARE VR team