One Analytics Stack.
Every XR Title Your Studio Ships.
This page is written for the head of engineering, XR studio director or platform lead who owns analytics across a portfolio of immersive products — not a single app. The problem is comparability across titles; the answer is a shared stack.
- •One event schema across every title in the portfolio
- •Signals stay comparable across Unity, Unreal and WebXR
- •Shared cohort tags — segment across apps, not just inside one
- •Central role-based access for engineering, UX and leadership
- •One SLA, one privacy posture, one procurement conversation
The problem a platform solves that a per-app tool cannot
A single XR title can be measured with almost anything. A portfolio of titles cannot. The moment you have two apps — a Unity training simulator and a WebXR product demo, or a Meta Quest game and a visionOS companion — the interesting questions become cross-title: is the accessibility guardrail we shipped in App A also violated in App B? Is the comfort regression in the new locomotion mode isolated to one title or systemic across the studio?
Answering those questions requires more than a shared login. It requires a shared event schema so 'hesitation at waypoint' means the same thing in App A and App B, a shared cohort model so 'returning user on Quest 3' is one definition instead of five, and a shared access model so a leadership dashboard is not a screenshot of a screenshot.
Everything else on this site is either a per-app view (/xr-application-analytics), a per-feature deep dive (/xr-heatmaps, /replay-xr-sessions) or a per-role workflow (/analyze-xr-behavior). This page is the argument for the platform underneath them.
"Two XR titles with different schemas is two products. Two XR titles with the same schema is a portfolio."
What the platform makes possible that per-app tools cannot
Cross-title capabilities
Portfolio-wide guardrail enforcement
Define comfort, accessibility and stability guardrails once at the org level. Any title that breaches a guardrail in any release surfaces in the same review queue — no per-app dashboard hunt.
Cross-title cohort analysis
A 'returning Quest 3 user' can be tracked across two of your titles. Portfolio retention becomes a real number instead of two disconnected ones.
Shared benchmarks across engines
Because the schema is shared across Unity, Unreal and WebXR builds, a hesitation rate in your Unity simulator is directly comparable to the same signal in your WebXR demo — no unit conversion, no caveats in the footnote.
One access model, one audit log
Role-based access, SSO, and a single audit trail across every title. Procurement, legal and IT review one contract, not one per app.
The per-app measurement surface (heatmaps, replay, comfort views) lives inside each title's workspace. This page is about what only exists above them.
What travels with the platform
- •A canonical event schema every title inherits
- •A canonical cohort model that spans titles and engines
- •Guardrail definitions applied at the org level, not per app
- •Shared privacy defaults — no per-title compliance drift
Comfort and safety at portfolio scale
A single title can absorb a comfort regression quietly. A portfolio cannot — a locomotion pattern that ships across three titles amplifies the same discomfort three times. The platform surfaces recurring comfort patterns across apps so studios can fix a shared library once instead of debugging three symptoms.
Accessibility as an org-level guardrail
Inclusive XR is easier to enforce at the platform than at the app. Reachable-volume and missed-affordance guardrails defined once at the org level apply to every title; a new app that breaches them is flagged before its first public release, not after a support ticket.
Who reads this dashboard
Head of Engineering / Platform Lead
Owns the shared SDK, schema and rollout policy. Uses the platform view to prove the studio's engineering guardrails are actually holding across every title.
XR Studio Director
Reads a single leadership view across the portfolio — comfort, stability, accessibility, engagement — instead of stitching per-app screenshots the night before a board update.
Central UX / Research
Runs cross-title studies that would be impossible from inside a single app workspace. Hypotheses about locomotion, tutorial length or hand-tracking generalise across the portfolio.
Why teams pick a platform over a per-app tool
Comparability is a feature
A shared schema is what makes cross-title numbers trustworthy. It cannot be retrofitted; it has to be the default from day one.
One procurement, one privacy posture
Legal and IT review the platform once. New titles inherit the same DPA, the same access model, the same privacy defaults — no per-app renegotiation.
Central rollout of new capture
A new comfort marker or accessibility guardrail lands in every title in the next SDK bump, not in a coordinated multi-team release.
Predictable economics across titles
Portfolio pricing sits at the studio level, not per title or per seat, so adding the next XR app to the stack does not trigger a new procurement cycle.
The SDK the platform standardises on
The same SDK that ships inside each title also enforces the platform's schema and guardrails. Studios pinning every title to the same SDK release band get the strongest cross-title comparability; teams staggering SDK upgrades still get comparable core signals thanks to schema versioning.
- •One SDK release band, all titles
- •Signed capture policies distributed centrally
- •Schema versioning so older builds stay comparable
Privacy defaults as an org policy
The platform enforces the same privacy defaults across every title — no raw audio, no biometric IDs, no video capture — so a new app cannot ship with looser defaults than the rest of the portfolio.