> For the complete documentation index, see [llms.txt](https://docs.3q.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3q.video/user-guide-new-ui/analytics.md). # Analytics
The **Analytics** area provides insights into how media content is viewed and accessed across the account. It helps users analyze playback performance, audience behavior, technical environments, and usage patterns. Analytics can be evaluated across all projects or limited to specific project types and individual projects. This makes it possible to review account-wide performance as well as detailed project-level statistics. From the Analytics area, users can: * Analyze playback performance * Review impressions, playback starts, and individual users * Evaluate playback time and playback progress * Analyze usage of renditions, audio tracks, and subtitle usage * Review viewer environments such as country, device, browser, and operating system * Use filters to narrow down the analysis * Select different time ranges * Export analytics data, depending on permissions and configuration The Analytics area is available from the main navigation under **Analytics**. *** ### Analytics Overview The Analytics area is divided into two main sections: * **Performance** * **Environment** The **Performance** section focuses on playback-related metrics, such as impressions, playback starts, playback time, and user activity. The **Environment** section focuses on technical and audience environment data, such as countries, devices, browsers, operating systems, domains, screen sizes, and player integrations. At the top of the page, users can select the project scope, analysis type, and additional filters. *** ### Project Selection The project selector defines which projects are included in the analysis. Available options may include: * **All Projects** * **All On-Demand Projects** * **All Livestream Projects** * Individual on-demand projects * Individual livestream projects Use **All Projects** for an account-wide overview. Select a specific project when you want to analyze the performance or environment data of one content pool, livestream project, or project-specific workflow. The available projects depend on the user’s permissions. *** ### Time Range Selection Analytics can be viewed for different time ranges. Available time range options include: * **T** – Today * **1D** – One day * **1W** – One week * **1M** – One month * **3M** – Three months * **1Y** – One year * Custom date range The selected time range defines which analytics data is shown in the chart or overview. Use shorter time ranges for operational monitoring and longer time ranges for trend analysis or reporting. *** ### Performance Analytics The **Performance** tab provides playback-related analytics. Available performance views may include: * **Playback Starts** * **Average Playback Time** * **Total Playback Time** * **Playback Progress** * **Renditions** * **Audio Track Languages** * **Subtitle Languages** * **Playback Start Conditions** The selected view determines which metric is shown in the main chart. *** ### Playback Starts The **Playback Starts** view shows how often playback was started during the selected time range. The chart can display several related values, such as: * **Impressions** * **Playback Starts** * **Individual Users** These values help compare how often content was displayed, how often users started playback, and how many individual users interacted with the content. *** ### Average Playback Time The **Average Playback Time** view shows how long users watched content on average. This metric is useful for understanding whether viewers stay engaged after starting playback. Use this view to evaluate: * General viewer engagement * Differences between projects * Content performance over time * Effects of content length or publishing context *** ### Total Playback Time The **Total Playback Time** view shows the accumulated playback time for the selected scope and time range. This metric is useful for understanding the overall consumption of content. Use this view for reporting total watch time across projects, campaigns, events, or specific publication periods. *** ### Playback Progress The **Playback Progress** view shows how far viewers progressed through the content. This can help identify whether users watch most of the video or leave early. Playback progress is especially useful for: * Training videos * Long-form content * Webinars * Event recordings * Editorial videos * Internal communication content *** ### Renditions The **Renditions** view shows which video renditions were used during playback. This can help evaluate which quality levels are delivered to viewers and how adaptive streaming behaves across different environments. Use this view to understand whether viewers mainly watch lower, medium, or higher quality renditions. *** ### Audio Track Languages The **Audio Track Languages** view shows which audio track languages were used during playback. This is useful when content includes multiple audio languages or alternative audio tracks. Use this view to evaluate multilingual content usage and audience language preferences. *** ### Subtitle Languages The **Subtitle Languages** view shows which subtitle languages were used during playback. This helps analyze subtitle usage and can support decisions about localization, accessibility, and translation workflows. *** ### Playback Start Conditions The **Playback Start Conditions** view shows how playback was started. This may include information about whether playback was started manually, automatically, or under other playback conditions depending on the player configuration. This view can help analyze how player settings influence user behavior. *** ### Environment Analytics The **Environment** tab provides insights into the technical and geographic context of viewers. Available environment views may include: * **Device Type Overview** * **Country Overview** * **Geo Heatmap** * **Domain Overview** * **Player Overview** * **Operating Systems Overview** * **Browser Overview** * **Screen Sizes** * **Integration Overview** These views help understand where users are located, which devices and browsers they use, and how content is integrated. *** ### Geo Heatmap
The **Geo Heatmap** view displays viewer activity on a map. This view helps identify geographic usage patterns and regional audience concentrations. Users can zoom and navigate the map to inspect regions more closely. Use the Geo Heatmap to analyze: * Regional traffic distribution * Event reach * Country-specific usage * Audience concentration by location *** ### Country Overview The **Country Overview** shows viewer activity grouped by country. Users can click on a country to view additional regional details, where available. For example, selecting a country may show a breakdown by regions or federal states. This is useful for understanding where viewers are located and how usage differs between regions.
*** ### Device Type Overview The **Device Type Overview** shows which device types were used for playback. This can include desktop, mobile, tablet, or other device categories depending on the available data. Use this view to understand whether content is mainly consumed on desktop or mobile devices and to optimize player integration accordingly. *** ### Domain Overview The **Domain Overview** shows the domains where content was played. This is useful when videos or players are embedded on multiple websites, portals, or partner platforms. Use this view to analyze where playback happens and to verify whether content is being consumed through the expected domains. *** ### Player Overview The **Player Overview** shows analytics grouped by player configuration. This is useful when multiple player configurations are used for different websites, projects, brands, or use cases. Use this view to compare player performance and identify which player configurations are used most often. *** ### Operating Systems Overview The **Operating Systems Overview** shows which operating systems viewers used. This can help identify technical patterns and support compatibility analysis. Use this view when investigating playback behavior across desktop and mobile operating systems. *** ### Browser Overview The **Browser Overview** shows which browsers viewers used for playback. This is useful for technical analysis, quality assurance, and troubleshooting browser-specific playback behavior. *** ### Screen Sizes The **Screen Sizes** view shows the screen sizes used by viewers. This information can help optimize website layouts, player dimensions, responsive embeds, and mobile viewing experiences. *** ### Integration Overview The **Integration Overview** shows how the player or content was integrated. This can help distinguish between different integration methods or embedding contexts, depending on the available data. Use this view to analyze whether content is consumed through the intended player integration. *** ### Filters Analytics can be refined with filters. Available filters may include: * **Country** * **Player** * **Category** * **Type** * **Container Mode** * **Integration** * **Browser** * **Operating System** * **Device Type** Filters allow users to narrow down the analysis to specific audiences, playback environments, metadata structures, or technical setups. For example, users can analyze playback starts for one project, filtered by device type and country, within a selected time range. *** ### Interactive Details Some analytics views allow users to click on chart elements or details to inspect more information. For example, in the Country Overview, users can click a country to view a more detailed regional breakdown where data is available. This makes it possible to move from a high-level overview to more specific insights. *** ### Exporting Analytics Data Depending on user permissions and account configuration, analytics data can be exported. Use the export option when analytics data should be used for: * Internal reports * Customer reporting * Editorial evaluation * Performance reviews * External analysis * Long-term documentation The exported data reflects the selected scope, metric, filters, and time range. *** ### Typical Use Cases Analytics can be used for different workflows, for example: * Reviewing video performance after publication * Measuring livestream audience activity * Comparing project performance * Checking playback starts and user reach * Understanding where viewers are located * Reviewing device, browser, and operating system usage * Analyzing subtitle and audio track usage * Evaluating player and domain performance * Preparing reports for internal teams or customers * Identifying technical patterns in playback behavior *** ### Notes The available analytics views, filters, and export options may depend on account configuration, enabled modules, and user permissions. Analytics data is based on the selected project scope, time range, metric, and filters. For meaningful comparisons, make sure that the same time range and filter settings are used across reports. Some detailed views are only available when enough data exists for the selected scope and time range. --- # 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.3q.video/user-guide-new-ui/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.