Policy - Usage Tracking and Analytics

We are evolving our usage tracking to better balance the needs of our clients, this document will get updated as soon as the changes roll out. Current expectation is March/April 2023.

Overview

NimbleStory has three different methods of usage tracking.

• NimbleStory (internal) - Named Users

• NimbleStory (internal) - Anonymized for Shared Content Only

• Google Analytics (external) - Anonymized for all Content

NimbleStory Activity Tracking (Internal) - Named Users

NimbleStory generates internal Events in the backend for specific events. All of these events are tracked against individual user accounts so we can identify trends and problems with content and system usage. As of July 2022, the following events are captured.

Activity Type	Trigger	Frequency/ Limits	Example of Details
ALL TYPES	As below	As below
Customer - Login	When a user authenticates to NimbleStory, any method, including SSO.	Limited - 1 per user/ per day *** This event is planned to change to Full so all logon attempts (successful and failed) are tracked as activities. (these are all logged and will remain so; but tracking as activities makes them easier to report on)
Organization - Access	When a user accesses a NimbleStory Organization	Limited - 1 per user/ per day ***
Project - Access	When a user accesses a NimbleStory Project for any reason	Limited - 1 per user/ per day ***
Project - Contents Listing	When a user accesses a NimbleStory Project Content Listing	Limited - 1 per user/ per day ***
Content Access - Portfolio Content	When a user accesses a Portfolio Content item	Limited - 1 per user/ per day ***
Content Access - Digital Workspace	When a user accesses a Digital Workspace item	Limited - 1 per user/ per day ***
Content Access - Concept Explorer Solution	When a user accesses a Concept Explorer Solution item	Limited - 1 per user/ per day ***
Content Access - Concept Explorer Perspective	planned	tbd - do we need more than the above
Content Access - Concept Explorer Waypoint	planned	tbd - do we need more than the above
Content Access - Geographic Explorer	planned	Limited - 1 per user/ per day ***
Customer - Password Change	planned	Full - every attempted and successful event
Content Edit - Portfolio Content	planned
Content Edit - Digital Workspace	planned
Content Edit - Concept Explorer Article	planned
Content Edit - Concept Explorer Core Visual	planned
Content Edit - Concept Explorer Perspective	planned
Content Edit - Concept Explorer Solution	planned
Content Edit - Geographic Explorer Solution	planned

*** One event, per user, per day with the event creation date as first login and last update date as last login.

NimbleStory Activity Tracking (Internal) - Anonymized for Shared Content

In addition to our Named user activity tracking, NimbleStory also generates internal Events in the backend for specific events when content is shared. These events are assigned to our SHAREDUSER account but otherwise track the same as above - just to a central account.

Google Analytics (External Usage Tracking)

NimbleStory uses Google Analytics to collect and analyze basic, visitor and system level analytics to identify trends in general usage (which browsers are most people using, what pages are most popular, where are most users arriving from, etc.)

How data collection works:

• When you visit NimbleStory, Google Analytics code arrives and runs in your browser.

• On first run, it will generate a ga_ cookie that is unique to your browser

• On each page view, Google Analytics records

  • the NimbleStory Google Analytics profile id

  • the unique google cookie value (this does not have your name, userid, or any other personally identifiable information in it)

  • the URL path of the click/ page view

  • relevant browser and device information (IP Address, Window size, Browser name, Browser version, etc.)

  • More Information: https://support.google.com/analytics/answer/11593727

How analysis and reporting works:

• NimbleStory administrators visit Google Analytics and login to view reports using Google Accounts that are not tied directly to NimbleStory and require 2FA for access.

• Reports are viewed by time period (today, last week, this month, custom periods)

• Reports can be filtered by any of the recorded information (URL Path/ Page, Window Size, Browser Name, Browser version, etc.)

• Important: Individual user information is not available in Google Analytics. It is purposely not collected to avoid privacy concerns.