In this section we are going to show you how to benefit from email reports, which helps product managers, application developers, and anyone involved with the product to take summaries of analytics, crashes, or push notifications on a daily & weekly basis, and also alerts, which sends you an email when a specific condition on session, custom event and crash analytics related metrics are met.
Getting access to data on-demand via beautifully crafted reports and dashboards is great and what we excel in. However, you sometimes need to be on top of changes in important metrics even if you aren’t looking at your dashboard.
At Countly we know that data is the most important basis for actions to be taken and should not be displayed randomly. Each product manager’s business requirements are different and so are their key metrics and performance indicators.
Alerts plugin helps you to define conditions on session, custom event, crash analytics related metrics and you’ll receive a notification email when a particular condition is met.
Below you can watch a video walkthrough of Alerts plugin:
We know that our customers are too busy to execute their businesses. We know that they can’t be online for all day and every minute. But we also know that their products are used by customers every minute and all day. That’s why getting information about immediate changes in product is very critical in some moments.
Alerts can let you know, in general, if there is something that needs your attention. Alerts give you an easy to use mechanism to be notified about changes in your data such as an increase/decrease in new users, occurrence count of a custom event or new crashes/errors.
With Alerts, you can get quick action to intervene and solve problems that your users are experiencing. For example, you released a new version. There may be bugs that may have run out of sight even though the tests go smoothly. Some bugs may even be critical in the level where your users may be prevented from using the application. An alert that you can identify in such situations can be a lifesaver.
To explain it in more detail, let's say you have an e-commerce application and you are going to release a new version in September. There are errors you know about in your application and these errors are not reflected in your users or do not interfere with using the application.
An e-commerce application can display a lot of products and the number of screens can be quite large. You may not be able to pass all the pages through the testing process, and there may be a bug that you have not experienced on pages you have not tested yet. Check screenshot below, where you define an alert when a new crash occurs.
In another example; the error/crash rate is starting to increase and most of your users are affected in an application you’ve just released a new version. If there is an increase of more than 10% in an existing crash rate, you need to identify the problem quickly and intervene it.
Do not forget that dissatisfied customers can have a very critical impact on your product, which is of course negative.
Let’s try to explain Alerts in more detail, this time with an event alert. Let’s say you have launched a campaign on your eCommerce website. You can define a clickable call to action a specific event for the campaign and you want to instantly observe the change in click rates.
Having an interest in this campaign may indicate that you need to increase the product in your stocks. Another situation is that the location of the campaign you define is the best spot for your users who can reach, and you can showcase other products you want to promote here.
20% increase in a specific event will give you a useful insight:
The number of users using your product is important metrics to follow, as well. Decreasing your user count may indicate a need for a field or a new feature that you need to develop.
For example, a decrease in the number of users on an eCommerce website will have an impact on sales in a negative direction, and the ongoing decrease will affect your business at a critical level in the long run. Defining an alert in the early stages and defining an alert to take action can be very beneficial for you.
Alert is much easier to set than you think. All you have to do is to do the following:
- Enter Countly panel and click on the
Management - Alertsmenu item.
- Define the state you want to create an alert for. This would be either an Event, a Metric or a Crash.
- You can define an alert for multiple apps at once for the most important metrics and crashes. For example, assume your new user count has increased by over 30%. In this case, it may also go to a level that is higher than your servers can normally take, and your application may lead to a problem that can not be reached.
- Save the Alert.
From now on, you are going to get an email comparing today's value with yesterdays, if an alert is triggered.
Countly can send email reports to you or your colleagues periodically. In order to do this, go to
Management > Email Reports reports and you'll see a page where you can define email reports for Analytics, Crash, Revenue or Events related data.
Below you can watch a video walkthrough of Reports plugin:
First, we are going to add a new email report to see how it works. When you go to
Management > Email Reports, you will probably see a blank page. Click on
Create new report on top right hand side of the screen.
In this screen, you are going to configure the following parameters:
- Frequency: Daily or weekly emails
- Time: Email sending time based on selected timezone of the application
- Emails: Users who are going to receive this email report
- Apps: Apps for which this report will be generated for.
- Include data: A selection of different metrics that should be included in the report.
When you click on
Save, your screen will look like the following. Email reports will now be generated every day or week depending on your selection.
Note that when you click on a report, you have the option to send an example, preview an email, or delete the corresponding report.