You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Introduction to the Power Platform ISV Studio app usage analytics| Microsoft Docs
3
-
description: Measure app's performance and get insights.
2
+
title: Introduction to Microsoft Power Platform ISV Studio app usage analytics| Microsoft Docs
3
+
description: Measure an app's performance and get insights.
4
4
services: ''
5
5
suite: powerapps
6
6
documentationcenter: na
@@ -23,41 +23,38 @@ search.app:
23
23
---
24
24
25
25
# App usage analytics
26
-
26
+
<!--note from editor: Please note the edit to the title. We still need to use "Microsoft" in front of "Power Platform," and there are other articles in this ISV Studio doc set that don't do so. -->
ISVs need datalike 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.
31
+
As an ISV<!--note from editor: Suggested. We should talk directly to the reader by using "you."-->, you need data—like active users or the number of times the solution has been installed—to measure the success of your application. You can use<!--note from editor: Via Writing Style Guide, we don't want to say that our software "allows" or "enables," we should "focus on what the customer needs to do." --> app usage analytics to get visibility into monthly, daily, and weekly usage data.
32
32
33
33
> [!NOTE]
34
-
> A tenant or customer needs to update their apps for an ISV to start seeing the usage data.
34
+
> A tenant or customer needs to update their apps for you to start seeing usage data.
35
35
36
-
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.
36
+
With the app usage feature, you can filter 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.
37
37
38
38
> [!NOTE]
39
-
> An app must be deployed via [AppSource](https://appsource.microsoft.com) in order to see this data.
39
+
> An app must be deployed via [AppSource](https://appsource.microsoft.com) in order for you to see this data.
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 extended the form by adding a widget to it. Every time the form is used, ISV1 gets the usage credit. Whenever the widget is used, ISV2 gets the usage credit. If a user visited the form only to access the widget, ISV1 also gets the usage credit.
44
45
45
-
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.
46
+
For a component that isn't shared, only the publisher who created it gets the usage credit.
46
47
47
-
For components that are not shared, only the publisher who created gets the usage credit.
48
-
49
48
## View the app usage dashboard
50
-
51
-
To view the app usage data:
52
-
49
+
<!--note from editor: Please double-check this procedure. I wasn't sure how steps 2 and 3 related to each other. -->
53
50
1. Sign in to [ISV studio](https://aka.ms/ISVStudio/).
54
-
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.
55
-
1.Scroll-down to the page to view all the apps. Select the app and select the **Usage** tab.
51
+
1. On the **Home** page, view the list of published apps. If necessary, scroll down to view the app for which you want to view usage details.
52
+
1. Select the app, and then select the **Usage** tab.<!--note from editor: I don't see a Usage tab in any of the screenshots for ISV Studio, but will it be obvious to the reader?-->
56
53
57
54
> [!div class="mx-imgBorder"]
58
55
> ![List of top apps](media/isv-top-apps.png"List of top apps")
59
56
60
-
1.You can also see the app usage details by directly selecting the app usage icon from the list of apps as shown in the screenshot:
57
+
<!--note from editor: I turned this into an indented paragraph because it's not a step, it's an alternative to the previous step. By the way, do you think this icon would be helpful in other articles? If so, we could make an inline graphic out of it.-->You can also go directly to the app usage details by selecting the app usage icon from an app in the list, as shown in the following image.
-**Monthly active users**: Tracks the information about the number of unique users who used the app within the last month.
70
-
-**Daily active users**: Tracks the information about the number of daily unique users who used the app within the last 24 hours.
71
-
-**Weekly active users**: Tracks the information about the number of daily unique users who used the app within the last 7 hours.
72
-
-**Usage over time**: Tracks the information about the number of monthly, weekly, and daily active users over time.
73
-
-**Monthly active users by component type**: Tracks the information about the number of monthly active users filtered by component type.
74
-
-**Monthly active users by component name**: Tracks the information about the number of monthly active users filtered by component name.
75
-
76
-
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.
66
+
-**Monthly active users**: Tracks the number of unique users who used the app within the last month.
67
+
-**Daily active users**: Tracks the number of daily unique users who used the app within the last 24 hours.
68
+
-**Weekly active users**: Tracks the number of daily unique users who used the app within the last seven hours.
69
+
-**Usage over time**: Tracks the number of monthly, weekly, and daily active users over time.
70
+
-**Monthly active users by component type**: Tracks the number of monthly active users, filtered by component type.
71
+
-**Monthly active users by component name**: Tracks the number of monthly active users, filtered by component name.
77
72
78
73
### Filtering the usage dashboard
79
74
80
-
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.
75
+
You can filter the usage dashboard by using the available filters. To see the metrics rolled up to the solution level, select all the components of the solution in the filter. Similarly, you can roll up all solution metrics to the package level, and roll up all package metrics to the app level.<!--note from editor: Edit okay? It seemed that the previous paragraph just restated what was in this section, so I combined them. -->
0 commit comments