Usage Metrics

A page of FAQs on data in general

How are Unique Users calculated in the Interaction Cloud?

Each client app connecting to the Interaction Cloud is allocated a unique ID. This ID is then stored in local storage on the client device and used to identify this user next time a connection to the platform is made.

The total number of different IDs connected to the Event is displayed within Studio Timeline and Analytics pages as Unique Users.

Note that a Unique user count does not denote a unique human in all cases. Differing privacy rules, local storage and other factors mean that the metric can't be guaranteed as truly unique - this applies to all similar measurement systems.

The best way to ensure accuracy is to use signed-in identifiers. If your IdP is integrated with Monterosa via the Interaction SDK then logged-in users help reduce the risk of double counting.

What is "peak concurrent users"?

"Peak concurrent users" refers to the highest number of users who were simultaneously connected to the platform at any given point in the event. These users can connect to the platform through websocket and HTTP Proxy connections. The measurement of peak concurrent users is taken every 5 seconds, with the final figure being the highest number recorded during that minute.

How are Session Lengths measured?

• Session length - this is the duration between client app connecting and disconnecting to/from the platform in the context of an Event. For more information see Analytics.

• Average session length - this is the combined duration of all event sessions divided by the number of all user sessions. Note that a user may have multiple sessions.

Why do Analytics data not match Google/Adobe Analytics exactly?

In addition to Monterosa / Interaction Cloud built-in analytics, you may also be tracking user activity with Google Analytics, Adobe Analytics or another 3rd party product. On the face of it, these products track the same things - the number of users viewing or engaging with an Experience, or the number of responses to each option in a poll, for example.

There are some differences, which relate to the different ways in which analytics are being measured by these different approaches. The effect of this is that there will usually be a small difference in the figures reported.

Web or app analytics provided by a 3rd party service track users based on "Tracking events" that are fired when users perform an action that is identified in the agreed tracking plan. These are aggregated in reports by time (hour/day/month) and can be filtered by other metrics.

Monterosa's platform analytics count the number of users connecting to the platform and interacting with content via a websocket connection. These are aggregated based on the Elements, Events and Projects that users interact with and so are not always directly comparable with the time-based ranges of a web analytics product.

Another difference is the way in which users are identified. Web analytics products usually identify the user based on a cookie that is stored on the browser or device. Some users choose not to accept these cookies, or opt out of tracking, either through consent management on your site or in their browser settings, and this will affect the numbers reported by that service. Monterosa platform analytics assign a unique ID to each user. This is stored differently and may not be affected by these settings in the same way.

In general, both services will show the same trends and usually have a very similar number of users and interactions, but the differences in measurement and aggregation can sometimes result in differences between the two.