In many cases, we may want to authenticate and control access to published GMetri content. There are a couple of ways to achieve this.
- Embed the experience on your App/Website/etc. and keep the access to this page authenticated.
- You can enable a text field at the beginning of the experience, asking users to input their unique identifier (Example. Employee ID for internal training) so you can reference that back to the analytics, if required.
- This method will incur no additional charges from GMetri. (Analytics charges, of course, are extra, and optional.)
- You can create as many GMetri view-only accounts for an experience as required. Example: A GMetri view-only account can be provided to each trainee for a VR training module.
- In this case, the authentication prompt will require credentials that have to be defined by the user during the first login.
- This is a chargeable feature, and the pricing depends on the number of view-only accounts created.
The GMetri platforms can store the following data points for any viewer of the immersive experiences:
- What the user looks at / interacts with - including coordinates of the user(s)
- When: The amount of time spent on the whole experience, per scene or looking at a single element
- How the user interacts with his/her surroundings - including what buttons were clicked/ what actions were performed on which element(s)/scene(s), and tracking user score in quizzes.
The above-captured metrics can be combined in various ways to get may insights through Custom Dashboard. These insights may include:
- User Performace/Leaderboard - by combining the total score of the user with the time spent by the user in the experience, one can estimate how well the user may perform in a real-world scenario.
- Creating domain-specific dashboards focusing on a few aspects of the training to gain further insights. Eg: measuring how one handles corrective situations in client interactions, or measuring how well versed a user is with technical processes, compliance, safety, soft-skills, etc.
- Dashboard to focus on user time spent, to create a feedback loop to detect and fix problems in the immersive environment itself - for example, if a user doesn't spend enough time at a particular section vs. other sections, it could have something to do with the design of the scene or the storyboarding. This information can then feed into the correction of the scene/storyboard itself, and to and any improvements may be measured over time.
Oculus recently announced that they are enabling casting options for the Go.
This came as great news to creators globally so you are not disconnected from the users when wearing the headset.
Here's how you can set this up:
There are a few legacy methods that you can still fall back on, you can find them here.