The LearnPlatform Browser Extension listens for three types of user actions:

• A tab is activated: user switches tabs
• A tab’s URL is updated: user navigates to a different page, or in some cases (like a single-page-app (SPA)), the user performs an action on the page which updates the URL.
• The current window changes: user has multiple Chrome/Edge windows open and switches between them (or switches away from Chrome/Edge)

When any of these actions occurs, LearnPlatform attempts to lookup the URL and match it against a list of tracking domains. Using the best match, the following two actions occur:

• For Load Events, the system increments a counter for the product. i.e. one URL change is a single load event. 
• For Minutes on System (MOS) Events, the system starts or resumes an “active” session for that product. This allows the system to track “how long” by accumulating the time that a session is active.

Every 60 seconds, the system takes all the usage data that it has collected and makes it available on LearnPlatform. Each time the system sends, all the existing usage information is cleared from the Chrome extension so that it does not accumulate and cause performance problems.

In the iOS app, the system uses the Web Content Filter. This essentially sends ALL network traffic. For each network request, the system inspects the URL and the bundle ID to determine if it’s an iOS App or iOS Web Usage Event. The system then matches that URL or bundle ID against a list of products and tracks usage based on that. 

Note: The system is using network traffic as an approximation of “usage”. Not every app sends a network request when the user interacts with the app, and not every network request is initiated by the user (e.g., an app might refresh data in the background). This is a “best guess” given the limitations in Apple’s ecosystem, but gives the system a way to gauge usage in broad terms.