What are the features/benefits of Analytics (Beta)?
- Out of the box dashboards to support indies
- 360 view of key metrics across activity, retention and revenue
- Easy multi-dimensional filtering
- Data recency of 2 hours max
- Stateful Audience segmentation considering player’s previous activity
- Predefined list of Audiences
- Custom Audience builder
Improved Data Recency
- Data is refreshed at least every one hour when upgrading to the Analytics SDK
- Improved user interface
- Better data visualization
- Transparency around metric definitions
- Changing of game settings and configurations in your game in real-time, without having to update the code via Remote Config Campaigns
- Audience targeting for game settings and config changes based on their player’s previous activity
- The ability to understand the impact of your Campaigns through Analytics reporting data
What is Analytics (Beta)?
Unity Gaming Services is an end-to-end platform designed to help you build, operate, and scale your game. As part of Unity Gaming Services, Analytics (Beta) gives studios the tools to understand performance and player behaviors through predefined Dashboards, Data Explorer, and more.
How can I get started with Analytics (Beta)?
- Sign in to the Unity Services Dashboard.
- Click Join now in the top banner.
- Accept the terms of service and click Join now.
- Click View SDKs.
- Select the packages that you want to install and click Generate Code Snippet.
- Follow the instructions provided by the code snippet model.
- Refer to the SDK installation guide here.
How much does it cost?
Unity Gaming Services products are completely free to use while in beta. Click here to see the pricing for when the products leave beta. You won’t be required to provide credit card information until then.
What’s the commitment to be a part of the beta?
You’ll need to boot up a new Analytics SDK in your game. The time to instrument new events and set up the SDK will vary based on game complexity and developer experience. This will unlock the ability to create and analyze events that are custom to your game, and to make use of additional features using your game data.
What are the differences between Analytics (Legacy) and Analytics (Beta)?
- Data refresh time in Analytics (Beta) is approximately one hour (versus eight hours on legacy)
- Built with player engagement in mind:
- Audiences cover both stateful and stateless segmentation so you can segment by platform, location, and other basic dimensions, and also by the player’s activity, retention and monetization profile.
- Audiences look back on historical data captured prior to audience creation while legacy analytics considers data captured after the audience is created.
- Exploring your data in Analytics (Beta) is simpler with:
- Improved data visualization and overall usability when querying metrics and events (both standard and custom).
- Enhanced event schema validation to prevent hacked events from polluting the data set.
- Multi-dimensional filtering tailored to the project so you no longer need to create segments to cover basic use cases such as: how is my game performing in a specific country? Which is my best performing platform?
- Analytics (Beta) offers Event Browser to debug your game’s event feed as they come in.
Are there any differences between the way the data is structured in Analytics (Legacy) vs Analytics (Beta)?
If you’ve previously used Analytics (Legacy) on your project and it’s still enabled, you’ll find that your standard events have been partially backfilled using your existing Analytics integration. This allows you to get a sneak peek of how the new analytics product will look and feel on your real data. While this can give you good insight into how your game is performing, it's only scratching the surface in terms of what our new analytics platform can offer.
Analytics (Beta) uses the following events to calculate the dashboard KPIs & metrics:
- newPlayer (previously appInstall)
Dispatched when a new player installs the app on their device.
- gameStarted (previously appStart)
Dispatched at the start of a new session. A new session starts when the user first launches an app or reengages as a new session after more than 30 minutes of inactivity.
- gameEnded (previously appStop)
Dispatched when a player takes an action to exit the game or no session activity is detected.
- gameRunning (previously appRunning)
Dispatched periodically when the app is running to detect session activity.
- clientDevice (previously deviceinfo)
Dispatched the first time a user launches an app and whenever device information changes.
- transaction (no change)
Dispatched when a player makes an in-app purchase and tracks the purchase amount.
While we have made our best efforts to keep data consistent between Analytics (Legacy) and Analytics (Beta), we’ve taken the opportunity to address customer feedback so there may be some slight inconsistencies when directly comparing the two. There are a number of reasons for this:
- Analytics (Beta) processes event data every one/two hours compared to the current general audience offering which processes event data every eight hours.
- Stricter event structure has been introduced to ensure your data is consistent and flows in gameplay order.
- Event data is processed in raw form to give you the flexibility to query, filter, and group your game data in Data Explorer.
- Event data from Analytics (Legacy) is available from July onwards. Players who installed your game prior to that date will be treated as new players and result in a peak in retention metrics.
- Metrics are calculated differently in the beta offering. For example, session length is determined by calculating the time difference between events in a session compared to tracking the session length on the client’s device. Check out the KPI and metric explanations available in the dashboards and metric dropdown in data explorer.
Note: Custom events are only supported once the SDK is installed in your game.
Do Analytics and Player Engagement tools need to be used together?
Our products within Unity Gaming Services were built to be modular, so they can be used independently, but are generally more powerful when used together. For example, you can build Audiences within Analytics (Beta), then target them or run A/B tests within Player Engagement for your Remote Config campaigns.
Can I continue to use legacy Analytics?
While Analytics (Beta) is a replacement product for legacy Analytics, the legacy solution will continue to operate as normal during the beta period.