Showing results for 
Show  only  | Search instead for 
Did you mean: 

What are Product Usage Filters?

What are Product Usage Filters?

Product Usage Filters are filtering options available in reports and ReachOut™ campaigns that allow you to create filters based on usage properties, i.e. how users have used your product.

Usage properties represent the entire lifetime of the user since the first time that they installed your software and made the initial call home to the server. This means that as long as the same data path has been used when calling ruiCreateConfig(), the values carry over when your software is upgraded or re-installed. For example if after 30 days the user uninstalls the product and re-installs it again the next day, the server will recognize that this is a known user and continue to count the usage statistics from his previous installation.

For more information on how Usage Intelligence tracks unique user installations visit this KBase article.

Available Product Usage Properties

Days Since Installation

This is the number of days that have passed since the user installed your application for the first time. Therefore if your software was installed on January 1 and today is January 15, this property would be translated to 15 days.

This property is only available for filtering in ReachOut™ campaigns.

Date of Installation

A user's date of installation is the date when your application made the first call home to the server for this user. You can filter by this property to see activity for users that were new in a particular date range.

This property is only available for filtering reports.

Date Last Seen

The date last seen of a user is the date when your application last called home to the server for this user, i.e. when the user last ran your application.

This property is only available for filtering reports.

Lifetime Runtime Minutes

This is the number of minutes that the user has run your software for. In single-session installations it is calculated according to when ruiStartSDK() and ruiStopSDK() have been called in your application. In environments where multi-session mode is being used, this value will be calculated according to when ruiStartSession() and ruiStopSession() are called.

Lifetime Number of Sessions

The number of sessions represents the amount of times that the user has opened your application. In single-session mode this means the amount of times that ruiStartSDK() has been called, while in multi-session mode this means the number of times ruiStartSession() has been called.

More information on single-session and multi-session modes can be found in this KBase article.

Lifetime Event Usage

Event usage filters allow you to filter your users based on how many times they generated an event since the application was installed. This can be a single event, or a combination of events which when added together amount to the specified number. For example I can create an event usage filter which includes eventA, eventB and eventC, and specify 10 as the minimum value. This means that the filter will apply to users who in their lifetimes have generated those events combined for at least 10 times, i.e. eventA could have been generated for 5 times, eventB for 8 times and eventC never generated at all.

More information on event tracking is available in this KBase article.

Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Apr 04, 2020 01:18 AM
Updated by: