Revulytics > Revulytics - Support Help Desk > Knowledgebase

Search help:

What is the difference between standard and current properties / filters / segments?


In the filters and segmentation panel at the top of every report (see screenshot below), you will notice some filters are highlighted in green whilst others in blue. The green filters show those based on Standard properties, whilst the blue ones are based on Current Properties. The difference between these two is explained below.

Standard Properties / Filters

Most of the reports within the Revulytics Usage Intelligence dashboard use daily granularity, which implies that the underlying data from each unique client installation is stored on a daily basis. This also means that if on a particular day a user was running version 1 of your software and later on that same day they updated to version 2, then in this case Usage Intelligence will only record the last known version number seen on that client installation during that particular day. Therefore in this case this user will be tagged as running version 2 being this was the last known value.

When generating timeline/trend reports for a particular date range, and you set a filter to show only active users running version 2, then the above user will only show up on those days when they were running version 2 (and not on the days when they were still running version 1.

In the case of date range reports that show aggregated data (such as a bar chart or a table that does not involve a timeline chart with daily values), then a user installation would only be included in that report if at the end of the selected date range they are still running version 2 (assuming you are still filtering for users matching version 2). This policy was adopted to have accurate counts in pie-charts or tables, where users are only included once (based on their last known value), even if they switched between version numbers during the selected daterange.

Note: If you are using Custom Properties of type 1, these are collected and stored in the same way as Standard Properties/Filters.

Current Properties / Filters

Unlike standard properties that are stored on a daily basis for each user, current properties are not stored daily but instead Usage Intelligence only stores the latest known value for that client installation. These kind of properties are normally used for data that rarely or never changes - such as the machine architecture including CPU, RAM and screen resolution. In fact reports related to these properties are only available as a "current snapshot" and not as a historical timeline. Thus you can only get a report of what CPUs are being used right now, and not what CPU distribution looked like 6 months ago.

When filtering timeline reports by Current Properties - for example to show only users having less than 2GB of RAM - the decision on whether a user installation matches the property criteria (in this case the amount of RAM on the user's machine) is based on the latest known data stored within that user's profile. Therefore if a particular user had less than 2GB RAM 2 months ago, but now has upgraded to 4GB of RAM, that user would not show up in any timeline reports filtering for users with 2GB of RAM. This is because for this type of Current Property, Usage Intelligence only retains the last known value.

NOTE: If you are using Custom Properties of type 2 and type 3 or license key tracking, these are collected and stored in the same way as Current Properties/Filters.

standard-current-filters.png standard-current-filters.png

Was this article helpful? yes / no
Related articles What type of data can I store in Custom Properties?
What are Product Usage Filters?
How do I enable Custom Properties on my account?
Using Custom Properties to collect Marketing Campaign Details
How does Revulytics Usage Intelligence identify unique users/installations? What happens when a user uninstalls, reinstalls or formats?
Article details
Article ID: 49
Category: SDK integration and Technical queries
Date added: 2015-05-28 09:51:07
Views: 274
Rating (Votes): Article rated 3.0/5.0 (2)

« Go back