Forum Discussion
User Report - only logging report opens not page views
Is this a bug of some kind? report views come though fine but no page views are ever recorded. It's been like this since I published a report there. The only thing I've done differently with this workspace is that was a pbip file and the workspace is part of a deployment pipline. Although I don't think that should have any effect on how the service logs uses...
I found the solution mtself on reddit, it's a limitation on the pbir report format. Hopefully MS fix this soon?
https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-report?tabs=desktop#pbir-considerations-and-limitations
9 Replies
Hi David_CMR,
Thank you for reaching out to the Microsoft Fabric Forum Community.
- Navigate to the Fabric Admin Portal (Power BI Service) → Tenant settings → Check for any settings related to usage metrics. Make sure that page views tracking is enabled for your workspace.
- Page views are only recorded when users interact with different pages. If users open the report but don't navigate between pages, the metric may not update. Try opening different pages in the report yourself to see if they register.
- If your workspace is part of a deployment pipeline, ensure that usage metrics are enabled in the target workspace where the report is published. Check the Development, Test, and Production workspaces separately to see if metrics are captured in one but not the others.
- Since this report was published as a PBIP file, ensure that all metadata related to tracking is included. Try publishing a standard PBIX version of the report in a test workspace to see if the issue persists.
- Occasionally, usage metrics may take some time to update. Please try refreshing the dataset manually from the Usage Metrics Report page.
Please refer to the links below for more details:
Usage Metrics Report does not show Page Views - Microsoft Fabric Community
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
- Navigate to the Fabric Admin Portal (Power BI Service) → Tenant settings → Check for any settings related to usage metrics. Make sure that page views tracking is enabled for your workspace.
Not a tenant, but I can check with the tenant.
- Page views are only recorded when users interact with different pages. If users open the report but don't navigate between pages, the metric may not update. Try opening different pages in the report yourself to see if they register.
Yeah, I'm 100% sure people, including me have navigated to and interacted with many/all of the pages in the report.
- If your workspace is part of a deployment pipeline, ensure that usage metrics are enabled in the target workspace where the report is published. Check the Development, Test, and Production workspaces separately to see if metrics are captured in one but not the others.
Is this something a Tenant needs to do?
- Since this report was published as a PBIP file, ensure that all metadata related to tracking is included. Try publishing a standard PBIX version of the report in a test workspace to see if the issue persists.
I'll try that.
- Occasionally, usage metrics may take some time to update. Please try refreshing the dataset manually from the Usage Metrics Report page.
Yeah, doubt it's a refresh issue as it logs report opens but not page views and this has been the case for 30+ days
Hi David_CMR,
Thank you for your detailed follow-up and for confirming the user interactions and workspace setup.
- Since you’re planning to test this—good decision. Please publish the same report as a standard .pbix file to a test workspace (not connected to a deployment pipeline). After publishing, interact with the report by navigating across pages and wait about 24 hours. If page views start registering here, it suggests the issue is likely related to the PBIP format or deployment pipeline setup.
- Since you aren't a tenant admin, I suggest asking someone with admin access to check the Power BI Admin Portal to ensure that Usage Metrics are enabled, especially the setting “Allow usage metrics for content creators” for your workspace or its security group. Also, make sure that activity logging policies aren't scoped in a way that might exclude tracking of page views. While report opens may still be captured, page views rely on more granular telemetry, which could be restricted at the tenant level.
- If your report is in a pipeline-connected workspace, review the deployment pipeline and workspace configuration. First, confirm the workspace is hosted in Premium capacity, as some telemetry features may behave differently in shared capacity. Ensure that usage metrics weren’t disabled or overwritten during deployment. It's also helpful to check whether page views are being tracked across Dev, Test, and Prod stages individually, as behavior can vary between them. As a troubleshooting step, try manually re-deploying the report outside of the pipeline to rule out any deployment-related metadata issues.
- Does the report use custom buttons, bookmarks, or navigation panes instead of the standard page tabs? These methods can sometimes affect how page views are tracked. In your PBIX test version, try navigating pages using the standard tabs to see if that makes a difference.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
- Navigate to the Fabric Admin Portal (Power BI Service) → Tenant settings → Check for any settings related to usage metrics. Make sure that page views tracking is enabled for your workspace.
Hi David_CMR
The issue you're experiencing—where report views are tracked but page views remain blank—is likely related to your use of the .pbip file format combined with deployment pipelines in Power BI. While report opens are captured, the page-level telemetry might not be fully supported or reliably tracked yet in setups involving .pbip and deployment pipelines, as Microsoft is still refining telemetry and logging behavior for these newer configurations. Additionally, if users are accessing the report through embedded links, Teams, or in any way other than directly in the Power BI Service, page views might not be logged. Workspace settings, such as disconnected datasets in a deployment pipeline stage or telemetry restrictions at the tenant level, can also cause this issue. To confirm, you can try publishing the same report as a regular .pbix file into a non-pipeline workspace and view it directly in the Power BI Service to see if page views begin to register. If they do, the issue is very likely tied to the pipeline setup or .pbip format.
