question

Some of these values are things which are captured automatically by our service. For example, there is an event for every player sign-in operation, so if you do a distinct Login... call on each session, that would provide you with the number of sessions per day (per user), and from that info you can determine the number of sessions per DAU. Depending on what events you're sending over the course of gameplay, total game time (and mean time per session) should also be easy to determine, since it's the time from sign-in to the last event before the next sign-in (if the only access point is the game itself - if there's a community web site as well, you'll need to account for that in the calculation).

We also provide an "origination" field (and event) for players, which is the info on which platform they used to create the account to start with - that would be the way to determine the players per platform.

The other items - Gender, Age, and Location - are not things that we track in PlayFab, though you can access them from some integrated partners. For example, Facebook gives you the ability to query for these things via their auth token. However, I would strongly urge caution in how you manage that data, since all three are considered "sensitive" in certain contexts.

So the data is there - the question then becomes how to best leverage it to get the graphs and analyses you want. There are a couple of options.

One is to use a PlayFab-integrated analytics partner to evaluate this info. One example of this is Appuri, who you can find in our Partner Marketplace. We also have Segment integration, and we'll have Omniata shortly.

Another would be to pipe the data to your own data store, where you could then apply any tools you prefer to the data (Tableau, etc.). Right now, you can enable this via our Segment integration, but we'll also provide a way to connect the event pipeline to your own endpoint soon.