The account under which your applications exists determine which features are enabled and the amount of data that can be received. Learn more about which features may be disabled and how the service reacts when the amount of incoming data approaches the limitations of the account.
You can view the full details on the active subscription plan of your account in the Telerik Platform. The subscription plan will typically include a license for the Analytics service as well as a Data Plan.
The Analytics License consists of a few items that relates to how the Analytics service enables features and handles data:
- The Data History describes the retention period for the recorded data. For instance, if you have a Data History of 365 days, then your data will be deleted 365 days after they have been recorded.
- The Report Type describes the types of reports you have access to.
The Report Type dictates potential limitations on which features are enabled. If you have the Standard Report Type then the following features are not enabled in your account:
- The ability to perform Advanced Queries
- Access to Feature Value and Feature Timing data
The Data History will enforce a retention on the recorded data meaning that data will be removed when it becomes older than the active window. Upgrading your subscription plan to a longer Data History will extend the life of your existing data.
The Data Plan describes a limitation for the number of installations that can be tracked under the given plan. This limit is expressed in installations pr. 30 days and is evaluated in 30 day periods where the number of unique installations are accumulated and compared to the limit. Once a given 30 day evaluation period has expired a new period is started anew and unique installations are again accumulated starting from this new period.
If the limitation is exceeded, data reception is stopped and all incoming data from the application under the account is rejected. The owner of the account should expect to receive an email warning of the limitation being reached with enough time to upgrade the Data Plan to cope with the increased data.
In the Analytics service the number of installations are determined by the number of unique anonymous identifiers that have been encountered in the evaluation period.
One typical issue with counting installations is that the number seems artificially high compared to the number of perceived users of the software. In these cases, there are a number of aspects that might affect the number that needs to be considered:
- The unique identifier is stored on the file system of the client device/machine as part of the meta-data stored by the integrated analytics monitor. If the user removes this storage, intended or not, the unique identifier will be recreated and effectively count as a new installation. This can be caused by e.g. a re-installation of the operating system or a hard reset of the device.
- Unless explicitly altered when integrating the analytics monitor in the software, the default behavior of the monitor for .NET based platforms is to store the unique identifier per user on the machine and this might cause confusion for software that is installed in a multi-user environment or even in a terminal based system such as Citrix. In these cases the recommended approach is to customize the storage implementation used by the integrated analytics monitor to ensure that the meta-data is stored as a granularity that matches expectations.