|
| 1 | +--- |
| 2 | +title: Introduction to the Power Platform ISV Studio app usage analytics| Microsoft Docs |
| 3 | +description: Measure app's performance and get insights. |
| 4 | +services: '' |
| 5 | +suite: powerapps |
| 6 | +documentationcenter: na |
| 7 | +author: "nkrb" # GitHub ID |
| 8 | +manager: kvivek |
| 9 | +editor: '' |
| 10 | +tags: '' |
| 11 | +ms.service: powerapps |
| 12 | +ms.devlang: na |
| 13 | +ms.topic: article |
| 14 | +ms.reviewer: nabuthuk |
| 15 | +ms.workload: na |
| 16 | +ms.date: 10/02/2020 |
| 17 | +ms.author: nabuthuk |
| 18 | +search.audienceType: |
| 19 | + - developer |
| 20 | +search.app: |
| 21 | + - PowerApps |
| 22 | + - D365CE |
| 23 | +--- |
| 24 | + |
| 25 | +# ISV app usage analytics |
| 26 | + |
| 27 | +[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)] |
| 28 | + |
| 29 | +ISVs need data like active users, number of times the solution installed or other means of data to measure the success of their application. App usage analytics feature allows ISVs to monitor the usage of their apps by giving them the visibility into monthly, daily, and weekly usage data of their apps. |
| 30 | + |
| 31 | +> [!NOTE] |
| 32 | +> A tenant or customer needs to update their apps for an ISV to start seeing the usage data. |
| 33 | +
|
| 34 | +App usage feature allows ISVs to filter the usage data by **Component Type**, **Data Date**, **Package Name**, and **Solution Name**. An app can have multiple packages and an individual package can have multiple solutions. Each solution can have multiple components. App usage is measured based on how many times the components of the application are used in a month, week, or day. |
| 35 | + |
| 36 | +> [!NOTE] |
| 37 | +> An app must be deployed via [AppSource](https://appsource.microsoft.com) in order to see this data. |
| 38 | +
|
| 39 | +> [!div class="mx-imgBorder"] |
| 40 | +>  |
| 41 | +
|
| 42 | + |
| 43 | +Some of the components of a solution can have shared ownership by multiple ISVs. For shared components, only the publisher who created the component gets the usage credit. For example, ISV1 created a form and ISV2 extends the form by adding a widget to it. Every time the form is used, ISV1 gets the usage credit and ISV2 gets the usage credit whenever the widget is used. If a user visited the form only to access the widget, ISV1 also gets the usage credit. |
| 44 | + |
| 45 | +For components that are not shared, only the publisher who created gets the usage credit. |
| 46 | + |
| 47 | +## View the app usage dashboard |
| 48 | + |
| 49 | +To view the app usage data: |
| 50 | + |
| 51 | +1. Sign in to [ISV studio](https://aka.ms/ISVStudio/). |
| 52 | +1. On the **Home** page, you can see a list of published applications. Select the desired application for which you want to see the usage details. |
| 53 | +1. Scroll-down to the page to view all the apps. Select the app and select the **Usage** tab. |
| 54 | + |
| 55 | + > [!div class="mx-imgBorder"] |
| 56 | + >  |
| 57 | +
|
| 58 | +1. You can also see the app usage details by directly selecting the app usage icon from the list of apps as shown screenshot: |
| 59 | + |
| 60 | + > [!div class="mx-imgBorder"] |
| 61 | + >  |
| 62 | +
|
| 63 | +## Overview of the usage dashboard |
| 64 | + |
| 65 | +The usage dashboard shows the following metrics: |
| 66 | + |
| 67 | +- **Monthly active users**: Tracks the information about the number of unique users who used the app within the last month. |
| 68 | +- **Daily active users**: Tracks the information about the number of daily unique users who used the app within the last 24 hours. |
| 69 | +- **Weekly active users**: Tracks the information about the number of daily unique users who used the app within the last 7 hours. |
| 70 | +- **Usage over time**: Tracks the information about the number of monthly, weekly, and daily active users over time. |
| 71 | +- **Monthly active users by component type**: Tracks the information about the number of monthly active users filtered by component type. |
| 72 | +- **Monthly active users by component name**: Tracks the information about the number of monthly active users filtered by component name. |
| 73 | + |
| 74 | +If ISV is looking at the metrics at a solution level, all the components are rolled up to the solution level. Similarly, all the solution metrics are rolled up to package and all package metrics are rolled up to an app. |
| 75 | + |
| 76 | +### Filtering the usage dashboard |
| 77 | + |
| 78 | +ISVs can filter the usage dashboard using the filters available. For example, an ISV can filter to see the metrics at app, package, solution, and component level. If ISVs want to see the metrics at solution level, ISVs can select all the components of the solution in the filter. |
| 79 | + |
| 80 | +### See also |
| 81 | + |
| 82 | +[Home page](isv-app-management-homepage.md) |
| 83 | +[App page](isv-app-management-apppage.md)<br/> |
| 84 | +[Tenant page](isv-app-management-tenantpage.md)<br/> |
| 85 | +[AppSource checker](isv-app-management-appsource-checker.md)<br/> |
| 86 | +[Connector Certification](isv-app-management-certification.md) |
0 commit comments