Countly offers revenue analytics for Countly Enterprise users to track revenue data in real time. Information you will get from revenue analytics will be:
- Total revenue
- Avg. revenue per user
- Avg. revenue per paying user
- Paying user count
- Paying/total users
There are two steps to start using revenue analytics right away;
In order to make revenue analytics simple to use, we made the process pretty straightforward. There are two ways to define one or multiple events as revenue event key(s).
You can type in the revenue event key while creating or editing your application as seen below.
Or, if you already have data for the event you plan to use as the revenue event, you can choose it from event management popup as shown below.
Note that you can provide multiple revenue event keys, separated by comma.
Start collecting data early
Note that revenue data can not be recorded post factum, so user numbers are only updated if Revenue plugin is enabled and revenue event is set. After this, paying member numbers increase. For this reason, we suggest that you set purchase events and enable Revenue plugin right from the time your application goes live.
Well, first step was pretty much all you had to do in order to use Revenue analytics. Payment data will be retrieved from the
sum property of your selected event. We will record the paying user counts based on the users who perform your revenue event.
Revenue currency conversion
Currency conversion for revenue should be done on client side. There are several online converters for this purposes and we suggest that you use a simple mapping to make sure that if a revenue data is retrieved in other currencies, it's easily converted to a reference currency (e.g USD or EUR).
Note that Revenue menu item seen above will be invisible unless system gets revenue events from devices.
This revenue information can also be seen from dashboard, right above world map.
If you are not familiar with Countly custom events, it is a great idea to check out the documentation now since revenue analytics depends on custom events.