Understanding Usage Activity Events in One Model
This article explains how Usage Statistics are generated in One Model; the system triggers that produce usage events, the usage event data processing, and how to correctly interpret metrics, especially queries, storyboards, and Explore activity. Usage Statistics reflect how One Model executes actions behind the scenes, which can differ from how users describe their behaviour.
Usage data updates approximately every 10 minutes, however these updates will not be reflected in your Storyboards or Explore views until the next full data processing run has completed.
Please note: The event mappings in this guide reflect the current, documented behaviour of One Model event triggers and default usage event processing at the time of publication. Whilst system triggers are the same across all One Model customers, those customers with custom/ non-default event processing may have a Usage Statistics configuration that differs from what is outlined below.
This document will use the following definitions:
| System Triggers | Markers embedded in each One Model instance that will generate a usage event. These can be triggered by certain user behaviours or other actions within the instance. |
| Usage Events | Records that log system triggers and include additional details relevant at the time of the trigger. These records constitute the raw data that is then processed and used in metrics, dimensions and storyboards for Usage Statistics. |
| Usage Statistics | Encompasses the whole of usage reporting, from system triggers, to usage events, through data processing and culminating in metrics, dimensions and storyboards. |
System Triggers: How Usage Events Are Triggered
Usage events are generated from a defined set of core system triggers. When certain actions occur in the One Model instance, the system trigger generates a usage event by logging the event, the datetime of the event, and other details relevant to the type of event that was triggered. System triggers are not location dependent; a user exploring a query in Explore and a user exploring a query within the Design panel in a Storyboard Tile will both generate QueryExplored usage events. Additionally, system triggers are not tied to user clicks, a user viewing a storyboard page will trigger usage events for each query configured in the page tiles, including any supporting queries.
Because of this:
- Different user actions can legitimately trigger the same event
- Usage classifications are based on technical execution context
- Usage counts reflect actual system activity, including the running of background and supporting queries, rather than user ‘clicks’.
Usage Events Matrix
| Query Execution | |
| Usage Event | Triggers |
| StoryboardRunQuery | Viewing a Storyboard page or tile, editing a tile, or pinning to a Storyboard. Storyboard ID logged. |
| ExploreRunQuery | Ad-hoc Explore queries, Drillthrough, AI Assistant chats, or span metric calculations. No Storyboard ID logged. |
| Storyboard Lifecycle & Navigation | |
| Usage Event | Triggers |
| StoryboardViewed | Navigating to a Storyboard, changing a page, or refreshing the view |
| StoryboardCreated | New Storyboard saved from Library, Org Chart, or AI Assistant |
| StoryboardDeleted | Storyboard deletions |
| Exports and Administration | |
| Usage Event | Triggers |
| CsvExported | Individual data extract as a CSV: Tiles, Drillthrough, AI |
| ExportedtoPowerPoint | Exporting an entire Storyboard. |
| Login | Successful session start (includes first-time logins). |
| UserFirstLogin | First successful session start for a user (earliest dated). |
| UserProxied | Admin "acting as" another user via the Account Menu’s ‘Proxy as User’ option. |
| AI Features | |
| Usage Event | Triggers |
| AssistantExampleSelected | Selecting a pre-configured example prompt in the assistant. |
| AssistantInsightsGenerated | Generating insights by clicking the lightbulb icon below a chart in the assistant. |
| AssistantPrompted | Submitting a user defined prompt in the assistant. |
| AssistantResultAnalyze | The assistant returns an analysis of a chart based on the user’s prompt. |
| AssistantResultAnswers | The assistant returns a pre-configured answer based on the user’s prompt. |
| AssistantResultAnswersList | The assistant returns a list of pre-configured topics or answers pertaining to a topic based on the user’s prompt. |
| AssistantResultStoryboard | The assistant returns a list of Storyboards related to a specified subject or topic based on the user’s prompt. |
| AssistantResultVisualization | The assistant returns a visualization based on the user's prompt. |
| ClickedCorrelation | Manually running a correlation from the lightbulb menu on a scatterplot chart. |
| ClickedForecast | Manually running a forecast from the lightbulb menu on a time series chart. |
| ClickedRegression | Manually running a line of best fit from the lightbulb menu on a time series chart. |
| ClickedTableInsights | Manually running Table Insights from the lightbulb menu on a list report. |
| ReferenceLineAdded | Adding a reference line to a chart. |
Query Execution Events
QueryExplored events track query execution and have a number of system triggers:
- Explore
- Storyboard tiles
- Query Designer editor preview (creating or editing tiles)
- Insights Library preview
- AI Assistant
- Drillthrough
- Funnel or span metric queries
StoryboardRunQuery and ExploreRunQuery
A QueryExplored event is logged every time a query is executed. Running queries however is not location specific within the One Model instance, so this event is reclassified when processing usage events into one of two customer facing activities, depending on whether a Storyboard ID is logged with the QueryExplored event.
- StoryboardRunQuery is a query executed in the context of a storyboard and is identified as a QueryExplored event with a Storyboard ID.
- ExploreRunQuery is a query executed outside the context of a storyboard and is identified as a QueryExplored event without a Storyboard ID.
Please note that some chart types (eg: funnel) run secondary queries that do not log a Storyboard ID with the QueryExplored as they are auxiliary system calls required to calculate secondary metrics. Since these QueryExplored events do not log a Storyboard ID, they will be classified as ExploreRunQuery.
How This Affects Reporting
StoryboardRunQuery
- Triggers per tile
- A storyboard with 10 tiles = 10 query events logged when fully loaded
ExploreRunQuery
- Includes ad-hoc analysis and background/system queries
- Does not mean the user was literally in Explore
Key takeaway: ExploreRunQuery ≠ “user was in Explore”. It means: “a query ran without a storyboard context.”
Storyboard Lifecycle & Navigation Events
StoryboardViewed
StoryboardViewed events track high level storyboard/ page navigation and trigger when a user:
- Navigates to a storyboard/ page
- Changes storyboard page
- Replaces the storyboard
- Opens a storyboard via AI Assistant
In multi page storyboards, a page level event is recorded only when a user actively views the page. Opening a storyboard does not automatically trigger events for all pages, just the page/s viewed.
StoryboardCreated
StoryboardCreated events track storyboard creation in the instance and trigger when:
- Creating a new storyboard from the storyboard library
- Pinning to a new storyboard from:
- Org Chart
- AI Assistant
- Explore
StoryboardDeleted
StoryboardDeleted events track storyboard deletions in the instance and trigger when:
- Deleting a storyboard from the Storyboard library
- Deleting a storyboard from the Storyboard settings panel (right-side panel)
Note: Deleted storyboards continue to appear in Usage Statistics reporting to preserve historical accuracy. For default implementations of Usage Statistics, deleted storyboards can be found in the ‘Storyboard/ Tile Used’ dimension grouped under ‘Deleted Storyboards’.
Exports and Administration Events
CsvExported
CsvExported events track csv exports and are triggered by:
- Exporting from Storyboard tiles
- Exporting from AI Assistant
- Exporting from Drillthrough
ExportedToPowerPoint
ExportedtoPowerPoint events track PowerPoint exports and are triggered by:
- Exporting a Storyboard using the ‘Export to PowerPoint’ option (on the Export tab) in the Storyboards settings.
Login and UserFirstLogin
Login Events events track logins and trigger at:
- Normal login
- SSO login
- Login after password update
- Login after password reset
A Login event tracks every time a login occurs. For reporting purposes this event is also used to track the number of first logins by users, using the earliest login date/time for the user.
- Login is any login (including a user's first).
- UserFirstLogin only counts each user's earliest login.
Key takeaway: Login includes all Login events. UserFirstLogin only counts the first (earliest dated) Login event per user.
UserCreated
UserCreated events track new account creations and are triggered by:
- Manually creating a user via the Admin > the Users page.
This event does not currently track users created via the Bulk User Upload tool or automated API integrations.
UserProxied
UserProxied events track when users act as (proxy as) other users and is triggered when:
- Using the ‘Proxy As User’ option from the Account menu.
AI Features Events
AI Features events track usage of the AI Assistant and integrated services and are triggered at the following behaviours/ actions:
AssistantExampleSelected
When the Assistant is queried with a selected pre-set question offered by the Assistant.
AssistantInsightsGenerated
When the Assistance enables/ generates Insights.
AssistantPrompted
When the Assistant is queried with a user defined prompt.
AssistantResultAnalyze
When the Assistant is queried with a user defined prompt using ‘Analyze’.
AssistantResultAnswers
When the Assistant is queried for a result that can be answered by ‘Answers’.
AssistantResultAnswersList
When the Assistant is queried for a list of the questions that can be answered by ‘Answers’.
AssistantResultStoryboard
When the Assistant is queried for a list of storyboards relevant to the prompt/ query.
AssistantResultVisualization
When the Assistant returns a visual to the user query/ prompt.
ClickedCorrelation
When ‘Run Correlation’ is selected from the lightbulb icon in a scatterplot chart configured with correlations.
ClickedForecast
When ‘Run Forecast’ is selected from the lightbulb icon in a line/ spline chart configured with forecasts.
ClickedRegression
When ‘Draw Line of Best Fit’ is selected from the lightbulb icon in a scatterplot chart configured with a line of best fit.
ClickedTableInsights
When ‘Run Table Insights’ is selected from the lightbulb icon in a table configured with table insights.
ReferenceLineAdded
When a reference line is enabled on a chart.
Reporting on Usage Statistics
Usage statistics can be used to determine the uptake and ongoing use of your One Model instance eg: who are regular users, most valued/viewed storyboards, user preferences for exploring or consuming pre-built content. A Usage Statistics storyboard is available and (by default) will use the following data fields, metrics and dimensions to report on: number of users, number of logins, and usage trends.
Data Fields
Usage Statistics data fields can be found in evt_usage_statistics and related dim_usage_statistics_[ ] tables under Explore >> Tables and Columns:
| Data Field | Description |
|---|---|
| User ID |
A unique identifier for the user triggering the event occurrence. This identifier is created and assigned by One Model (is not the user's employee, worker or person id) and will be prefaced with ‘OM’ if the user is a One Model employee. This data field is used to build the User dimension, with user names grouped by One Model/ Customer then alphabetically by first name. |
| Effective Date (UTC) |
The date of the usage event. This date defaults to the UTC time zone. This data field is used to align usage events to any Calendar or Fiscal time period dimensions. |
| Event Occurrence |
A unique identifier for the usage event. A count of this data field is used for generating many of the Usage Statistics metrics. |
| Additional Column Used |
(if applicable) The name of the additional column used when exploring queries, exporting to csv and/ or creating a new storyboard from a query built in Explore. There will be one record/ row per additional column used in the query, however all records will have the same Event Occurrence identifier. The additional column will be in the format [database].[table].[columnname] This data field is used to build the Additional Column Used dimension, with columns grouped under their relevant database and table name. |
| AI Assistance Query Text | (if applicable) The query text (prompt) entered into the One AI Assistant. For sensitivity reasons, this data field is disabled by default and may be enabled on request. |
| Datetime | The date and time of the usage event, defaulting to the UTC time zone. |
| Dimension Used |
(if applicable) The name of the dimension used when exploring queries, exporting to csv and/ or creating a new storyboard from a query built in Explore. There will be one record/ row per dimension used in the query, however all records will have the same Event Occurrence identifier. This data field is used to build the Dimension Used dimension, with dimensions grouped under their latest/ most current dimension category. |
| The email of the user triggering the event occurrence. | |
| Metric Used |
(if applicable) The name of the metric used when exploring queries, exporting to csv and/ or creating a new storyboard from a query built in Explore. There will be one record/ row per metric used in the query, however all records will have the same Event Occurrence identifier. This data field is used to build the Metric Used dimension, with metrics grouped under their latest/ most current metric category and subcategory. |
| Page ID |
(if applicable) A unique identifier* for the page used when viewing storyboards, exploring queries within storyboard pages, exporting, and running One AI integrated services. *With the exception of the ‘-1’ page identifier. Page ID’s in Usage Statistics were introduced in 2023 in line with the release of multi page storyboards. When Page ID’s were added to Usage Statistics, all existing single page storyboards were given a ‘-1’ page identifier. |
| Page Name |
(if applicable) The name of the page used when viewing storyboards, exploring queries within storyboard pages, exporting, and running One AI integrated services. Only the most recent known name* of the page will be used. This data field is used to build the Storyboard/ Tile Used dimension, with pages grouped under their storyboards latest known current or deleted status, their storyboards category and their storyboard. *Page details are recorded only when a user triggers a page level event. Any pages which have not been part of a trigger event recently may be grouped under historically used storyboard and page labels. |
| Storyboard Category |
(if applicable) The name of the category applicable to the storyboard used when viewing storyboards, exploring queries within storyboard pages, exporting, and running One AI integrated services. Only the most recent known name* of the category will be used. This data field is used to build the Storyboard/ Tile Used dimension, with storyboard categories grouped under their latest known current or deleted status. *Storyboard details are recorded only when a user triggers a storyboard event. Any storyboards which have not been part of a trigger event recently may be grouped under historically used storyboard labels. |
| Storyboard ID | (if applicable) A unique identifier* for the storyboard used when viewing storyboards, exploring queries within storyboard pages, exporting, and running One AI integrated services. |
| Storyboard Name |
(if applicable) The name of the storyboard used when viewing storyboards, exploring queries within storyboard pages, exporting, and running One AI integrated services. Only the most recent known storyboard name* will be used. This data field is used to build the Storyboard/ Tile Used dimension, with storyboards grouped under their latest known current or deleted status and their latest known category. *Storyboard details are recorded only when a user triggers a storyboard event. Any storyboards which have not been part of a trigger event recently may be grouped under historically used storyboard labels. |
| Storyboard Original Name | (if applicable) The original/ first known name for the storyboard used. |
| Storyboard Page Tile ID | (if applicable) A combination of storyboard id, page id and tile id. Identifier is in the format [storyboardid]_[pageid]_[tileid] |
| Tile ID |
(if applicable) A unique identifier* for the tile used when viewing storyboards, exploring queries within storyboard pages, exporting, and running One AI integrated services. *With the exception of unsaved tiles, which are given a negative tile identifier which can be reused over different storyboards. Negative tile identifiers are used when tiles are initially created but not yet saved on the storyboard page. Once the page is saved, the tile is given a unique identifier. |
| Tile Name |
(if applicable) The name of the tile used when viewing storyboards, exploring queries within storyboard pages, exporting, and running One AI integrated services. Only the most recent known tile name* will be used - please note that there are often instances where, as a design choice, tiles are not named (tile header is hidden). This data field is used to build the Storyboard/ Tile Used dimension, with tiles grouped under their storyboards latest known current or deleted status, their storyboards category, their storyboard and their storyboards page. *Tile details are recorded only when a user triggers a tile event. Any tiles which have not been part of a trigger event recently may be grouped under historically used storyboard, page and tile labels. |
| Time Dimension Used |
(if applicable) The name of the time periods dimension used when exploring queries, exporting to csv and/ or creating a new storyboard from a query built in Explore. This data field is used to build the Time Dimension Used dimension. |
| User Name |
The full name of the user triggering the event occurrence. This data field is used to build the User dimension, with user names grouped by One Model/ Customer then alphabetically by first name. |
Metrics
| Activity | |
| Metric | Description |
| Admin | Total admin access within the selected time period. |
| Explore | Total explore activities within the selected time period. |
| Exports | Total exports within the selected time period. |
| Exports per Login | Average exports per login within the selected time period. |
| First Logins |
Total first logins within the selected time period. A “first” login is defined as the very first time a user logs into the One Model instance, users can only ever have one first login for their user details. |
| Logins | Total logins within the selected time period. |
| Usage Activity | Total usage activity within the selected time period. |
| Storyboards | |
| Metric | Description |
| % New Storyboard Views | The percentage difference in storyboard views over time. |
| Storyboards Viewed | Total Storyboards viewed within the selected time period. |
| Storyboards Viewed - Previous Period | Total Storyboards viewed within the previous time period to the currently selected time period. |
| Storyboards Viewed per Login | Average Storyboards viewed per login within the selected time period. |
| User | |
| Metric | Description |
| Logins per User | Average logins per user within the selected time period. |
| Users | Total users within the reporting selected time period |
Dimensions
| Activity | |
| Metric | Description |
| Additional Column Used | The additional column (if any) used by the user, grouped by the One Model fact or dimension table the column is found in. |
| Dimension Used | The dimension (if any) used by the user, grouped by the category the dimension is found in. |
| Metric Used | The metric (if any) used by the user, grouped by the category the metric is found in. |
| Storyboard/Tile Used |
The storyboard, page and tile (if any) used by the user, grouped by storyboard category, storyboard, page and tile. Displays the last known labels only, grouped into current/active storyboards and deleted storyboards. Deleted storyboards will display in the category they were assigned to at the time of deletion. |
| Time Dimension Used | The time dimension (if any) used by the user. |
| Usage Activity | The user action that generated a count for Usage Statistics. |
| User |
The name of the user performing an action in the instance, grouped alphabetically (One Model users grouped separately). The user identifier reflects a One Model internally generated user identification key and not the user’s worker, employee or person id. |
Verifying Usage Statistic Counts
Why are Explore query counts higher than expected?
Queries are counted per tile and include background queries (AI, previews, span metrics) are included
Why does Explore usage include non-Explore activity?
Many features reuse the same query execution triggers (eg: running queries within the context of a storyboard tile), classifying the query execution into ExploreRunQuery or StoryboardRunQuery depends on the presence of a Storyboard ID captured in the event details.
Why do deleted storyboards still show usage?
Usage is preserved for trend and historical analysis so deleted storyboards are grouped in the Storyboard/ Tile used dimension under ‘Deleted Storyboards’. Note this dimension reflects the last known labels for storyboard categories, storyboards, pages and tiles.
Are deleted pages and tiles also grouped into the Deleted Storyboards category?
Deleted pages and tiles are grouped under their storyboard. If this storyboard is deleted it (and its pages and tiles) can be found under the Deleted Storyboards grouping. If not, it will be found in the Current Storyboards grouping.
Why does the grouping for Storyboard/ Tile used not reflect the most current (“todays”) view of storyboards and their categories?
Usage Statistics metrics and dimensions are built using Usage Events. If no event has been triggered on a storyboard recently it can mean that storyboard details captured for that event will not be up to date. Eg: if a storyboard has been moved from Category A to Category B, this change will only appear in the Storyboard/ Tile dimension once an event on that storyboard has been triggered.
Comments
0 comments
Please sign in to leave a comment.