We know that many developers distribute their apps via the Oculus store so we wanted to outline the main differences between the Oculus analytics dashboard and our own. This goal of this table is to provide clarity and transparency into how we calculate our metrics, as well as to clarify any data discrepancies when comparing data between the two platforms.
|What timezone do you display data in?||UTC||PST|
|How do you define a unique user?||Observer treats every computer (or standalone device) as a unique user.||Oculus tracks users by their Oculus ID|
|How do you define a session?||We define a session as the time between a user opening the application and then closing it||Unclear|
|When do you start tracking data?||We track data immediately upon session start||Oculus stops tracking sessions when they reach the 3-to-4 hour mark, they do not specify the exact time|
|When do you stop tracking a session?||Observer has added functionality for developers to set an automatic shutoff, however, we allow you to track any session length||Oculus only registers sessions once they’ve passed 60 seconds of play|
|Can I export data?||Yes, just request the events you want to export and we can send them over as a CSV or JSON file. Dashboard export coming soon!||Each graph lets you export that specific dataset|
The Oculus “Active” Users chart is the same graph that appears on your Observer “Overview” page. We’ve decided to graph Active Users and Sessions as two separate lines to eliminate the need for highlighting over every point of the graph as you do on the Oculus dashboard.
Oculus only shows average time per user per day rather than average session length. You’ll find both metrics on the sessions page of your Observer dashboard.
On the Oculus dashboard, they claim the following:
"Disclaimer: This data is an approximation within 5% and may be delayed 24 hours or more. Performance data does NOT include users with prototype Rifts, DK1, and DK2. Please refer to financial reports for official values."