Skip to main content

​
Your analytics page

Open My Apps → your app → Edit → Analytics while signed in as the app’s owner or a team member. The earlier /app/<slug>/analytics route redirects to the Analytics section of the edit console. It shows aggregate usage for a time window (90 days by default): A usage chart shows the trend over the window.

​
Privacy built in

Analytics are aggregate and anonymized:
  • No individual users or raw payloads are ever shown.
  • Results are suppressed when the cohort is too small to stay anonymous, so very new apps may show no data at first.

​
Make your analytics useful

Analytics are built from what your app records through app-metrics. To get meaningful numbers:
  • Record meaningful events, for example session_complete or level_complete, not every frame.
  • Save scores with saveScore when a session produces a result. This drives Avg score.
  • Keep event types stable across releases so trends stay comparable.

​
What to watch

Your app page also shows plays, saves, votes, reviews, and comments.

​
Compare usage with sales

Open Edit → Commerce for product sales, subscription payments, and recent transactions. Use Edit → Analytics to understand usage. These panels answer different questions: paid access does not guarantee someone played, and trial or membership access does not imply a direct app payment. Usage analytics remain aggregate and subject to the minimum-cohort rule. Commerce transaction records are a separate operational view and may display shortened buyer wallet addresses. Product revenue estimates use current catalog prices; subscription revenue uses recorded payment amounts. Neither is a net wallet balance. See Revenue and payouts for interpretation and access to funds.