BI Pixie provides a rich set of metrics to analyze your BI audience. This table includes the main metrics that are available in the Power BI App of BI Pixie. You can find these metrics throughout the report pages (Some of the metrics appear in more than one page) and in measures.
The metrics are grouped by the following categories:
- Activities
- User Engagement Metrics
- Report Metrics
- Page Metrics
- User Satisfaction Metrics
- Design Impact Metrics
- Performance Metrics
Activities
The activities below are used by BI Pixie to define active and passive usage in Power BI reports. For example, users that view reports without any active interactions are classified as passive users.
| Activity | Description | Activity classification |
|---|---|---|
| Page Views* | The number of times users view a report page. This type of activity is considered as a passive event. Without additional activities that are tracked below, BI Pixie will classify users, reports and report sessions as passive. | Passive use of reports (Pixie Event type = Page) |
| Visual Interactions (Interactions in visuals) | The number of activities where users click on visuals that lead to interactions with other visuals and to recalculations of measures in your reports. | Active use of reports (Pixie Event type = Sense) |
| Slicer Clicks | The number of clicks in slicers that were automatically detected in the reports. Slicers include built-in or custom Slicer visual that are placed inside the report pages. | Active use of reports (Pixie Event type = Slicer) |
| Filter Clicks | The number of filter clicks (or other slicing events) that are tracked when users apply filters on columns that are explicitly tracked by BI Pixie Instrumentation after you preconfigured BI Pixie to track these columns. | Active use of reports (Pixie Event type = Filter) |
| Bookmark Clicks | The number of times users click on bookmarks. BI Pixie collects also the bookmark names. | Active use of reports (Pixie Event type = Bookmark) |
| Link Clicks | The number of times users click on dynamic or static hyperlinks in the report pages. Hyperlinks are tracked in Table values and web actions in columns with conditional formatting, buttons, shapes and images (Matrix hyperlinks are supported as well). BI Pixie collects the URLs and the visual type and name from where the hyperlinks were clicked. | Active use of reports (Pixie Event type = Link) |
| Tooltip Opens | The number of times users hover on visuals elements that open report page tooltips. BI Pixie collects the name of the tooltip report pages and the selected column and value that were used to load the tooltip with specific details. | Active use of reports (Pixie Event type = Tooltip) |
| Drillthroughs | The number of times users perform drill through from selected visual elements to new report pages with details. BI Pixie collects the name of the drillthrough page and the selected column and value that were used to filter that page. | Active use of reports (Pixie Event type = Drillthru) |
User Engagement Metrics
| Metric | Description |
|---|---|
| Users | The count of unique users that are tracked. Throughout the report, other metrics may refer to this metric as active users. Users can be classified as passive or engaged. |
| Passive Users | The count of unique passive users. Passive users open reports and can even navigate through multiple pages of the reports, but they don't perform any activity. When users have no activity that is classified as active (as described in the Activities table above), they are counted as passive users by this measure. |
| Engaged Users | The count of unique engaged users. Engaged users view report pages but they engage further through tracked events as described in the Activities table above (Active Users = Engaged Users + Passive Users) |
| New Users | The count of unique users that are tracked for the first time in a given time period |
| Last-Time Users | The count of unique users that are tracked for the last time in a given time period |
| % Passive Users | The percentage of Passive Users relative to Users |
| Cumulative Users | The cumulative count of Users over time |
| Cumulative Lost Users | The cumulative count of Last-time users over time until the previous period. |
| % User Attrition | The percentage of Cumulative lost users relative to Cumulative users |
| DAU | Daily Active Users (including passive users who view report pages but don't interact with them, and including engaged users who interact with reports) |
| MAU | Monthly Active Users (including passive users who view report pages but don't interact with them, and engaged users who interact with reports) |
| WAU | Weekly Active Users (including passive users who view report pages but don't interact with them, and engaged users who interact with reports) |
| DAU/MAU | Daily active users divided by monthly active users. This ratio is an industry standard KPI to measure user stickiness. A ratio of 0.5 means that 50% of your monthly users are active on a daily basis. |
| DAU Excluding Passive | Daily Active Users (excluding passive users who view report pages but don't interact with them) |
| WAU Excluding Passive | Weekly Active Users (excluding passive users who view report pages but don't interact with them) |
| MAU Excluding Passive | Monthly Active Users (excluding passive users who view report pages but don't interact with them) |
| DAU/MAU Excluding Passive | Daily users who are active and engaged divided by monthly users who are active and engaged. Passive users are excluded from this metric. |
Report metrics
| Metric | Description |
|---|---|
| Tracked Reports | The number of reports that you instrumented using BI Pixie Instrumentation. Tracked reports = Opened Reports + Unused Reports. |
| Opened Reports | The number of reports that you instrumented using BI Pixie that have tracked activity (passive and active). Opened Reports = Interactive Reports + Passive reports. |
| Interactive Reports | The number of reports that you instrumented using BI Pixie that have tracked activities beyond page views. |
| Unused Reports | The number of reports that you instrumented using BI Pixie that have no tracked activity |
| Passive Reports | The number of reports that you instrumented using BI Pixie that have only page views but no other activity |
| % Passive Reports | The percentage of Passive Reports relative to Tracked Reports |
| % Unused Reports | The percentage of Unused Reports relative to Tracked Reports |
| Report Sessions* | The count of report sessions. A report session is a set of activities that are detected from the same user in a single report in a given time frame. BI Pixie aggregates events into a single session – as long as the user is not idle for a duration of 2 minutes. If a user is idle for more than 2 minutes, when they return to the report, BI Pixie tracks the new activity as a new session. You can change the 2 minutes timeout in Session timeout (min) parameter of the Semantic Model. |
| Passive Sessions* | The count of report sessions that include only page views (or navigation through pages). |
| Interactive Sessions* | The count of report sessions that includes interactions within pages (And not navigations through pages). |
| Avg Interactions* | The average number of interactions per report session (excluding page views or page navigations). |
| % Interactive Sessions* | The percentage of Interactive Sessions relative to Report Sessions |
| Avg Session Duration (Sec)* | The average duration of report sessions in seconds |
| Page Clicks | The count of times users opened report pages within report sessions. |
| Report Interactions | The count of times users interacted with reports through any of the activities in the table excluding page views or page navigation. |
*Note: In BI Pixie Power BI app, when you see this metric in a visual that aggregates data by page and not by report, a corresponding page-level metric is used for the calculation.
Page Metrics
Page metrics includes page-level measurements that are aggregated by pages and page sessions. Page sessions of the same page name coming from two different reports will be counted as two separate sessions. A page session is a subset of a report session. BI Pixie breaks down report sessions into one or more page sessions.
| Metric | Description |
|---|---|
| Tracked Pages | The number of pages that you instrumented using BI Pixie Instrumentation. Tracked Pages = Opened Pages + Unused Pages. |
| Opened Pages | The number of pages that you instrumented using BI Pixie that have tracked activity (passive and active). Opened Pages = Interactive Pages + Passive Pages. |
| Interactive Pages | The number of pages that you instrumented using BI Pixie that have tracked activities beyond page views. |
| Unused Pages | The number of pages that you instrumented using BI Pixie that have no tracked activity |
| Passive Pages | The number of pages that you instrumented using BI Pixie that have only page views but no other activity |
| % Passive Pages | The percentage of Passive pages relative to Tracked Pages |
| % Unused Pages | The percentage of Unused pages relative to Tracked Pages |
| Page Sessions* | The count of page sessions. A page session is a subset of a report session. BI Pixie breaks down report sessions into page sessions when the user navigates between pages. |
| Passive Page Sessions* | The count of page sessions that include only page views. |
| Interactive Page Sessions* | The count of page sessions that includes interactions. |
| Avg Interactions* | The average number of interactions per page session (excluding page opens). |
| % Interactive Sessions* | The percentage of Interactive Sessions relative to Page Sessions |
| Avg Session Duration (Sec)* | The average duration of page sessions in seconds |
| Page Interactions | The count of times users interacted in the given page session through any of the activities in the Activities table above and beyond page views or page clicks. |
User Satisfaction Metrics
With BI Pixie you can collect user feedback from your BI audience, and analyze user satisfaction. To start collecting user feedback BI Pixie can instrument your target reports and add a feedback control (learn how to set up feedback collection here).
| Metric | Description |
|---|---|
| Feedback Clicks | The number of clicks in the Feedback control. |
| Positive Clicks | The number of clicks in the positive button of the Feedback control. |
| Negative Clicks | The number of clicks in the negative button of the Feedback control. |
| Satisfied Users | The number of users whose last click was positive in the selected reports |
| Dissatisfied Users | The number of users whose last click was negative in the selected reports |
| CSAT (Last Response) | The count of positive responses (last response per user and report) divided by all last feedback responses in the specified time period. |
| CSAT (Multiple Responses) | The count of all positive responses, including multiple responses per user, divided by all feedback responses in the specified time period. |
| Average Satisfaction | A number between -1 (negative) and 1 (positive) that is the average of all non-neutral feedback clicks. 0 means that the number of negative clicks equals to the number of positive clicks. |
| Respondents | The count of users who provided feedback, including neutral feedback. |
| % Feedback Responses | The percentage of feedback providers relative to all report consumers. |
Design Impact Metrics
You can analyze the effectiveness of your report design using three new scores that assess report complexity, usability and passivity.
Complexity score
An estimate of the report's complexity at the data visualization level as was detected during the instrumentation by BI Pixie. Higher score means that the reports may have excessive number of visuals or objects that are expensive to maintain.
Usability score
An estimate of the report's usability which is based on the detection of controls such as bookmarks, slicers, tooltips and drill-throughs. As the score gets higher, you are likely to get more user-friendly reports.
Passivity score
An estimate for the dominance of table and matrix visuals that lead to passive consumption. A higher score means that the report leads to passivity and is more likely to serve as a data export tool.
| Metric | Description |
|---|---|
| # of Visuals | The number of visuals found during the last BI Pixie instrumentation. |
| Visuals per Page | The average number of visuals (Best used at the report or project/workspace level). |
| # of Bookmarks | The number of bookmarks found during the last BI Pixie instrumentation at the report level. |
| # of Slicers | The number of slicers found during the last BI Pixie instrumentation at the page level. |
| # of Table Visuals | The number of Table and Matrix visuals found during the last BI Pixie instrumentation at the page level. |
| # of Columns in Table Visuals | The number of columns used in Table and Matrix visuals as found during the last BI Pixie instrumentation. |
| # of Objects | The number of buttons, images and shapes found during the last BI Pixie instrumentation. |
| # of Tooltip Pages | The number of Tooltip pages found during the last BI Pixie instrumentation. |
| # of Drillthru Pages | The number of Drillthrough pages found during the last BI Pixie instrumentation. |
| Complexity Score | An estimate of the report's complexity. Higher score means excessive visuals or objects. |
| Usability Score | An estimate of the report's usability based on controls detection. |
| Passivity Score | An estimate for the dominance of table and matrix visuals. |
Performance Metrics
Measuring the effectiveness of your Power BI reports cannot be complete without taking into account performance data. You can extend BI Pixie capabilities by connecting to Azure Log Analytics.
| Metric | Description |
|---|---|
| Duration | Total duration of the execution in seconds. Provided as aggregations of 'durationMs' metric from Power BI in Azure Log Analytics. Aggregations: Sum, Average, P50, P75, P95. |
| Total CPU Time | Total CPU time of the request in seconds. Provided as aggregations of 'totalCpuTimeMs' metric. Aggregations: Sum, Average, P50, P75, P95. |
| Query Processing CPU Time | Total CPU time spent by tasks on Analysis Services query thread pool thread. Aggregations of 'queryProcessingCpuTimeMs'. |
| Vertipaq Job CPU Time | Total CPU time spent by Vertipaq engine in seconds. Aggregations of 'vertipaqJobCpuTimeMs'. |
| Execution Delay | Total time spent waiting for Analysis Services engine thread pool thread availability. Aggregations of 'executionDelayMs'. |
| Query Result Rows | Total number of rows returned as a result of the DAX query. Aggregations of 'queryResultRows'. |
| Performance Log Count | The number of load events per visual and other dimensions. Used as the weight in weighted average calculations. |
When SUM is applied as the function of the metrics above a Sum function in DAX is used to summarize multiple aggregations.
When AVG, P50, P75 or P95 functions are used for one of the metrics above, a weighted average is applied to aggregate multiple aggregations of the metric. The count of visual load events is used as the weight.