Custom Events are collected via the
ruiTrackEventCustom() and optionally the
ruiTrackEventNumeric()* API calls. When collecting these events, they will be included with the statistics associated with event tracking reports. Additionally you will have the ability to download the custom events in CSV format on a daily and monthly basis, which will include the meta data related to each event as well as the custom data logged with the event.
When logging custom text the data field can contain any string length of your choice so you can collect multiple values delimited by a '|' (pipe) character for example.
Each tracked custom event contains:
- Meta data collected automatically by the Usage Intelligence SDK. Such meta data includes the full user profile such as product version, build number, OS, language, license type, geo location, hardware architecture, etc)
- The unique Usage Intelligence Client ID that generated that event.
- The custom string or numeric data that was collected with the event.
Custom events are designed for download and use for offline processing or automated parsing, as well as for integrating with third party BI solutions. For more information on Custom Event tracking check out this blog article.
Custom Events are billed by the amount of data collected. For more info on how this billing works check out this KBase article.
- Numeric events are not collected as custom events by default. Should you wish to enable numeric event data to be included with your product's custom data please contact support.