Logged-in member figures
Logged in members adds daily counts of users with recorded activity. The same person can count on several days, platforms or devices.
ReferenceView as Markdown
Stay in the loop 🚀
Logged in members adds daily counts of users with recorded activity. The same person can count on several days, platforms or devices.
The administrator guide explains the graphs and date controls.
Signal selects distinct non-null user_id values from any recorded event within the tenant and daily time window. Empty IDs are removed during aggregation. All counts these IDs; anonymous activity and explicit login-attempt totals are outside this measure. Signal selection.
With subscription maps numeric user IDs to tenant members in batches of 500. It counts distinct member IDs whose effective active owner or sharing subscription count exceeds zero. This uses subscription state when the summary runs, including active shared access, rather than state at the event time. Daily card writer.
The API adds saved daily counts over inclusive dates, excluding deleted summary rows. One user active on 3 days contributes 3 to All. To reconcile With subscription, inspect the user-to-member mapping and effective subscription status at processing time. Card aggregation.
Graphs select page views and custom podcast events. Signal groups each user's rows by URL, event type and event name, taking MAX(user_agent) per group. Mixed-device activity within that group can therefore retain only one user agent. .
Classification applies in this order:
podcast_ become Podcast, even without a valid URL./podkaster or /podcasts become Podcast.minside. or paths containing /account become Mypage.Other events and invalid URLs are excluded, except the podcast events handled first. User agents matching Mobile, Android, iPhone or iPad become Mobile; all others, including missing values, become Desktop. For a misclassified count, compare the grouped URL, event name and retained user agent with these rules. .
The writer counts distinct user IDs separately for each day, platform and device. The browser sums these counts across dates. One desktop user visiting 2 platforms contributes 2 to the device column and 1 to that day's All. ; .
UI presets use Oslo calendar dates: Last 7 days sends today minus 6 through today. Last 30 days uses minus 29. Explicit fromDate and toDate override presets when both are present. Bare API requests default to today minus 7 through today, an 8-date range. Reproduce discrepancies using the exact dates sent by the UI. ; .
Both writers initially process today and the preceding 7 days. Later runs start after their last completed-day checkpoint and include today. Today remains open for recalculation; previously checkpointed days are not routinely revisited. Raw windows use Oslo day boundaries, while stored dataDate holds the Oslo calendar date. ; .
Raw pagination uses 1,000 users per page, capped at 100 pages for cards and 200 for graphs. Incomplete pagination throws before that day's summary is written. Check cursor errors and the relevant checkpoint when one report component stops advancing. ; ; .
Card processing writes explicit zero counts for an empty day. Graph processing only updates categories returned by its query. Source inspection suggests an existing category row can remain when recalculation returns no users for that category. Test this with controlled data before attributing stale counts to that behavior. ; .
Source checked on 28 September 2026 at commit 6cd1850; existing UI observations are from 27 September. Numeric reconciliation, mixed-device fixtures, recalculation behavior and ordinary-role access were not tested in this revision.