Did you find this helpful?

Dashboard Overview

Dashboard is the first page you see when accessing the title. It contains overview for the following items:

  1. Logins and Installs
  2. Purchases and their breakdown
  3. API Calls and Errors
  4. Event Stream

It is possible to change the overview period to increase/decrease using "Time period" panel in the top right corner.

Installs and logins statistics

Dashboard contains "Logins" panel (1). This panel shows the amount of logins executed at 3 points based on your selected time period. It also shows the percentage-based change between those 3 points. In the example above, we see that during last 24 hours, we had 4,575 logins which is 18.63% less than we had yesterday and 13.82% more than what we had a week ago. "Logins" panel also shows distribution of login events during the specified period as a chart. You can place the mouse over different peaks to check for additional information, such as time and the number of events.

Dashboard also contains "Installs" panel (2) which is, functionally, the same as "Logins" panel, and shows overview of Install events.


Dashboard offers an overview of purchases and revenue of your title. "Purchases" panel (1) shows the distribution of purchases over the specified period of time. "Purchase Breakdown" panel (2) shows purchases grouped by platform.  

API calls, Errors and PlayStream Events

Dashboard contains 2 important tools to analyze the impact on the system and it's behavior. Those are "API Requests" panel (1) and "API Errors" panel (2). "API Requests" panel shows the distribution of all API calls during the specified period of time. "API Errors" panel, on the other hand, shows the distribution of errors. You can place your mouse over certain points on the charts to see additional information about that time period.

In addition to API calls and errors, dashboard offers "PlayStream Debugger" panel, which displays all the incoming PlayStream events in real-time: 

You can click on event time stamp label (1) to see the event details in JSON format (2).

Did you find this helpful?