Skip to content

Commit 92c99b9

Browse files
authored
Making changes as per editing suggestions
1 parent 07bc93c commit 92c99b9

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

powerapps-docs/developer/common-data-service/isv-app-usage-analytics.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -23,12 +23,11 @@ search.app:
2323
---
2424

2525
# App usage analytics
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. -->
2726
[!INCLUDE[cc-data-platform-banner](../../includes/cc-data-platform-banner.md)]
2827

2928
[!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
3029

31-
As an ISV<!--note from editor: Suggested. We should talk directly to the reader by using "you."-->, you need data&mdash;like active users or the number of times the solution has been installed&mdash;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.
30+
As an ISV, you need data&mdash;like active users or the number of times the solution has been installed&mdash;to measure the success of your application. You can use app usage analytics to get visibility into monthly, daily, and weekly usage data.
3231

3332
> [!NOTE]
3433
> A tenant or customer needs to update their apps for you to start seeing usage data.
@@ -46,15 +45,14 @@ Some of the components of a solution can have shared ownership by multiple ISVs.
4645
For a component that isn't shared, only the publisher who created it gets the usage credit.
4746

4847
## View the app usage dashboard
49-
<!--note from editor: Please double-check this procedure. I wasn't sure how steps 2 and 3 related to each other. -->
5048
1. Sign in to [ISV studio](https://aka.ms/ISVStudio/).
5149
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?-->
50+
1. Select the app, and then select the **Usage** tab.
5351

5452
> [!div class="mx-imgBorder"]
5553
> ![List of top apps](media/isv-top-apps.png "List of top apps")
5654
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.
55+
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.
5856

5957
> [!div class="mx-imgBorder"]
6058
> ![Usage icon](media/isv-select-app-to-see-details.png "Usage icon")
@@ -72,7 +70,7 @@ The usage dashboard shows the following metrics:
7270

7371
### Filtering the usage dashboard
7472

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. -->
73+
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.
7674

7775
### See also
7876

0 commit comments

Comments
 (0)