Custom events and Exception Tracking are billed by the amount of data uploaded from your clients.
Custom events are counted and reported just like normal event tracking, however you also get the added benefit of collecting custom data whenever an event occurs. The list of raw events together with all data collected is made available as a downloadable CSV archive on a daily/monthly basis.
Custom data 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 Revulytics 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 custom string data that was collected with the event.
Every event usually consumes around 1KB of meta data plus the size of your custom string data (or stack trace in the case of exception tracking). Please note quota is counted in 1KB intervals.
So just as an example let's say you have 1000 installations using your software every day and each installation generates 2 events/exceptions per day. For each event/exception you are collecting 1KB of meta data plus 800 bytes of custom or stack trace data. This case scenario would generate:
30 days x 1000 installs x 2 exceptions x 2KB = 120,000KB = 117MB of data per month.
You can topup your account with prepaid data bundles such as 250MB, 500MB, 1GB, etc. Once you exceed the monthly quota available, the Revulytics server will stop collecting custom events/exceptions, unless you topup your quota or the quota is reset at the end of your billing cycle.
Please contact us for more details and quotes on using custom events and exceptions.