<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Custom user metrics report in DAX Commands and Tips</title>
    <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Custom-user-metrics-report/m-p/5004090#M187094</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;What you are seeing is expected and comes from how the &lt;STRONG&gt;auto-generated Usage Metrics report is calculated upstream&lt;/STRONG&gt; versus what is exposed in the Usage Metrics dataset.&lt;/P&gt;&lt;P&gt;The standard report is effectively working on a &lt;STRONG&gt;sessionized, report-level semantic layer&lt;/STRONG&gt;, while the dataset you connect to is &lt;STRONG&gt;event-level telemetry&lt;/STRONG&gt; (page renders, interactions, navigation events, etc.). The built-in &lt;EM&gt;ViewsCount&lt;/EM&gt; measure therefore tends to overcount compared to the standard report because it includes multiple events within a single viewing session.&lt;/P&gt;&lt;P&gt;In practice, the closest approximation is to reconstruct a session grain and then aggregate at report level:&lt;/P&gt;&lt;PRE&gt;Report Views =
COUNTROWS (
    SUMMARIZE (
        UsageMetrics,
        UsageMetrics[ReportId],
        UsageMetrics[UserId],
        UsageMetrics[SessionId]
    )
)&lt;/PRE&gt;&lt;P&gt;If SessionId is unreliable or not populated, you can approximate sessionization using time bucketing:&lt;/P&gt;&lt;PRE&gt;Report Views (Time Bucket Approx) =
COUNTROWS (
    SUMMARIZE (
        UsageMetrics,
        UsageMetrics[ReportId],
        UsageMetrics[UserId],
        FORMAT ( UsageMetrics[Timestamp], "yyyymmddhh" )
    )
)&lt;/PRE&gt;&lt;P&gt;Technically, you will never get a 1:1 match with the auto-generated report because Microsoft applies additional filtering and normalization before the metrics are surfaced. The recommended approach is to define a consistent session-based view definition and use that across custom governance or adoption reports.&lt;/P&gt;&lt;P&gt;If you can share which Usage Metrics tables you are using, I can help refine the session grain further.&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;</description>
    <pubDate>Tue, 10 Feb 2026 13:27:32 GMT</pubDate>
    <dc:creator>bariscihan</dc:creator>
    <dc:date>2026-02-10T13:27:32Z</dc:date>
    <item>
      <title>Custom user metrics report</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Custom-user-metrics-report/m-p/3581657#M156226</link>
      <description>&lt;P&gt;I'm trying to create a customer user metrics report. I have created a local report on the user metrics datamodel, but I can't seem to replicate the viewscount that is shown is the auto-generated user metrics report. The viewerscount measure that is provided does give the same result as the standard report.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;this is what the auto-generated report looks like. I can clearly see that I had 5 views and 4 unique users viewing my 'kredietacceptatie' report.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I try to re-create this in Power BI Deskop and use the provided measure ViewsCount, I get a different number.&lt;/P&gt;&lt;P&gt;I am pretty sure this has to do with this ViewsCount measure registrating page level views instead of report level views.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have tried different DAX measures, but I am not able to recreate the the Views from the auto-generated report.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm curious to learn if anyone has been able to tackle this problem or has any suggestions on what DAX measure will replicate the numbers from the standard report.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2023 10:33:10 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Custom-user-metrics-report/m-p/3581657#M156226</guid>
      <dc:creator>Brenda_Loznik</dc:creator>
      <dc:date>2023-12-13T10:33:10Z</dc:date>
    </item>
    <item>
      <title>Re: Custom user metrics report</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Custom-user-metrics-report/m-p/5004090#M187094</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;What you are seeing is expected and comes from how the &lt;STRONG&gt;auto-generated Usage Metrics report is calculated upstream&lt;/STRONG&gt; versus what is exposed in the Usage Metrics dataset.&lt;/P&gt;&lt;P&gt;The standard report is effectively working on a &lt;STRONG&gt;sessionized, report-level semantic layer&lt;/STRONG&gt;, while the dataset you connect to is &lt;STRONG&gt;event-level telemetry&lt;/STRONG&gt; (page renders, interactions, navigation events, etc.). The built-in &lt;EM&gt;ViewsCount&lt;/EM&gt; measure therefore tends to overcount compared to the standard report because it includes multiple events within a single viewing session.&lt;/P&gt;&lt;P&gt;In practice, the closest approximation is to reconstruct a session grain and then aggregate at report level:&lt;/P&gt;&lt;PRE&gt;Report Views =
COUNTROWS (
    SUMMARIZE (
        UsageMetrics,
        UsageMetrics[ReportId],
        UsageMetrics[UserId],
        UsageMetrics[SessionId]
    )
)&lt;/PRE&gt;&lt;P&gt;If SessionId is unreliable or not populated, you can approximate sessionization using time bucketing:&lt;/P&gt;&lt;PRE&gt;Report Views (Time Bucket Approx) =
COUNTROWS (
    SUMMARIZE (
        UsageMetrics,
        UsageMetrics[ReportId],
        UsageMetrics[UserId],
        FORMAT ( UsageMetrics[Timestamp], "yyyymmddhh" )
    )
)&lt;/PRE&gt;&lt;P&gt;Technically, you will never get a 1:1 match with the auto-generated report because Microsoft applies additional filtering and normalization before the metrics are surfaced. The recommended approach is to define a consistent session-based view definition and use that across custom governance or adoption reports.&lt;/P&gt;&lt;P&gt;If you can share which Usage Metrics tables you are using, I can help refine the session grain further.&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Feb 2026 13:27:32 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Custom-user-metrics-report/m-p/5004090#M187094</guid>
      <dc:creator>bariscihan</dc:creator>
      <dc:date>2026-02-10T13:27:32Z</dc:date>
    </item>
  </channel>
</rss>

