> For the complete documentation index, see [llms.txt](https://docs.decentraland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decentraland.org/creator/scenes-sdk7/other/scene-analytics.md). # Scene Analytics As a creator, it's very valuable to track player visits and the way in which players interact with your scene. Instead of assuming, you can obtain real data and make informed decisions while iterating on your designs. The [Creator Hub](https://decentraland.org/create) includes an **Analytics** section with detailed metrics for every scene you publish or have permissions on. You don't need to add anything to your scene, this data is collected automatically for all published scenes. {% hint style="info" %} **📔 Note**: Analytics data is updated once a day. Only the owners and operators of a scene can view its data. {% endhint %} ## View your scene's analytics 1. Open the Creator Hub and sign in with your account. 2. Select the **Analytics** tab on the top navigation bar. You'll see a list of all the published scenes you own or operate, with headline metrics for each. 3. Click on a scene to open its detail page, with the full set of metrics organized into tabs. Data is tracked per scene. If a World contains multiple scenes, each scene appears as a separate entry in the list, with its own metrics. ## The scenes list The list shows one row per scene, with the following fields: * **Unique Visits**: Distinct users who visited your scene, counted once each. * **New Users**: Users who visited your scene for the first time. * **D7 Retention**: The percentage of new users who returned to your scene at least once over the 7 days after their first visit. * **Revenue**: MANA earned in your scene. * **Avg. Playtime**: Average time each user spends in your scene on a single visit. You can sort the list or search by name, and pin the scenes you care about most to the top. ## The detail page Click on any scene in the list to open its detail page. Next to the metrics you'll find a card with general information about the scene: its like rate, whether access is public or private, the World it's published in, who last published it, and when it was last updated. You can also copy the scene's URL, jump into the scene, or create an event for it directly from this page. Use the **Date Range** selector to compute the metrics over the last 7, 30, or 60 days, and the **Export Analytics** button to download the data as a .csv. The metrics are organized into four tabs. ### Overview A snapshot of your scene's growth, engagement, and user retention. * **Total Visits**: Every visit to your scene, including repeat visits by the same user. * **Unique Visits**: Distinct users who visited your scene, counted once each. * **New Users**: Users who visited your scene for the first time. * **Concurrent Users**: The highest number of users in your scene at the same time. * **Revenue**: MANA earned in your scene. * **Day 7 Retention**: The percentage of new users who returned to your scene at least once over the 7 days after their first visit. * **Avg. Playtime**: Average time each user spends in your scene on a single visit. * **AFK Time**: Average time users spend in your scene without interacting. * **Desktop / Mobile**: Users who visited your scene from a desktop or mobile client. ### Visits How many users visited your scene, and how many were new or returning visitors. * **Unique Visits in the Last 60 Days**: Unique visitors, broken down by platform (all platforms, desktop, and mobile). Users are deduplicated across platforms: someone who plays on both desktop and mobile is counted once in the all platforms total and once in each platform's total. * **Weekly Active Users**: Unique active users during each week. * **Weekly Users Flow**: How your weekly users split between: * **New Users**: Users who visited your scene for the first time. * **Returned Users**: Users who visited last week and came back this week. * **Reactivated Users**: Users who had stopped visiting and returned this week. ### Engagement How users engage with your scene once they're in it. * **Average Daily Playtime**: Average time each user spends in your scene on a single visit, with a week-by-week chart and the change against the previous week. * **Average Weekly Playtime**: Average time each user spends in your scene per week. * **Social Interactions**: Three social signals, shown both as weekly totals and as the share of that week's visitors who did each thing: * **Messages Sent**: Chat messages sent by visitors in your scene. * **Emotes Played**: Emotes played by visitors in your scene. * **New Friendships**: Friend requests accepted between visitors in your scene. ### Retention The percentage of users who return after their first session. * **Platforms**: Your 60-day rolling average retention, compared across desktop and mobile. * **Day 7 Retention by Cohort Week**: The percentage of users who returned at least once over the 7 days after their first visit, grouped by the week they first jumped into your scene. The chart draws a 20% benchmark line as a healthy reference value. * **Weekly Churn Rate**: The percentage of active users from the previous week who did not return this week. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.decentraland.org/creator/scenes-sdk7/other/scene-analytics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.