Product analytics
Review tenant-isolated semantic click usage and explicit instrumented outcomes without collecting record contents, field values or free-form user input.
Screen orientation
Tenant administrators only. Every aggregate is scoped to the authenticated tenant and the selected reporting window.
The header selects a 7-, 30- or 90-day window and refreshes the report. Summary cards show aggregate volume and outcomes; tables show allow-listed semantic actions, daily activity and role-track totals.
Field reference
The entries below describe the current screen controls and read-only values. They do not relax server-side validation, site scope, classification handling or required independence in a governed decision.
| Field or value | Control | Required or shown when | How to use or read it | Result |
|---|---|---|---|---|
| Analytics period | Select | Required; 7, 30 or 90 days. | Choose the shortest window that answers the usage question before comparing longer-term adoption. | Scopes every total, action row, daily bucket and role-track aggregate. |
| Clicks | Summary metric | Read-only aggregate. | Counts accepted semantic click events, not raw DOM events or page views. | Shows instrumented action volume for the selected period. |
| People and browser sessions | Summary metrics | Read-only, tenant-scoped distinct counts. | Use these aggregates to separate broad adoption from repeated activity without identifying individual people. | Shows distinct actor and session volume. |
| Succeeded, failed and outcome rate | Summary metrics | Read-only explicit outcomes. | Interpret only actions that emit an instrumented result; click-only actions do not imply success or failure. | Shows completion signals for supported actions. |
| Action / Surface / Screen | Read-only table keys | Stable allow-listed semantic identifiers. | Use the keys to locate the product control without inferring record identity or submitted values. | Groups click and outcome aggregates by governed product interaction. |
| Daily activity | Read-only chart | One aggregate bucket per active day. | Compare relative activity across the selected period; empty days carry no record-level detail. | Shows click volume over time. |
| Role tracks | Read-only aggregate list | Only approved coarse role-track labels. | Use the counts to assess adoption by operating role without treating them as authorization records. | Shows aggregate clicks and people by role track. |
| Privacy boundary and retention | Read-only policy statement | Always displayed. | Confirm the collection boundary before interpreting or exporting any aggregate. | States excluded data classes and the configured retention window. |
Actions and effects
When to use: When a tenant administrator selects 7, 30 or 90 days.
What it does: Reloads the same tenant-isolated aggregate report for that window.
When to use: When current aggregates are needed without changing the selected window.
What it does: Requests a fresh summary; it does not create, delete or alter analytics events.
Lists and states
- Top semantic actions groups stable action, surface and allow-listed screen keys with clicks, people and explicit outcomes. It never includes URLs, record identifiers, field contents, query strings, IP addresses or user-agent strings.
- Daily activity and role tracks are aggregate views only; they do not provide person-level activity history or authorization evidence.
Authority boundary
Product analytics is an administrator-only adoption view, not an employee-monitoring, audit-log or transaction-record system. It accepts stable allow-listed semantic keys and explicit outcomes only, retains tenant isolation and does not expose user identities, page contents, field values, record identifiers, URLs, query strings, IP addresses or user agents.