Alerts and reports


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 and weekly basis, and also alerts, which send you an email when metrics related to a specific condition on session, custom event, crash analytics, and ratings are met.

Alerts: Get notified when a case occurs

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.

The Alerts plugin helps you define conditions for metrics related to session, custom event, crash analytics, and ratings so that you receive a notification email when a particular condition is met.

Why Use Alerts?

Alerts is a very helpful feature that lets you get information about immediate changes in your data in relation to a given condition, triggering a notification when there is something that needs your attention. It is a simple but effective mechanism to know right away about changes such as an increase/decrease in new users, occurrence count of a custom event, new crashes/errors, or changes in user ratings for a new feature or page.
With Alerts, you can quickly identify where to intervene and solve problems that your users are experiencing. For example, you released a new version but there may always be bugs that may have run out of sight even though the tests went smoothly. Some bugs may even be so critical that they may prevent your users from using the application. Setting an Alert that allows you to identify such situations can be a lifesaver.

Alerts use cases examples

To explain Alerts 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. The screenshot below shows how you can 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 solve it.


Do not forget that dissatisfied customers can have a very critical impact on your product, which is of course negative. Conversely, changes to your product can be reflected positively on your audience satisfaction. Let’s see how Alerts can be deployed to let you know changes in Ratings.
Suppose you have released a new version of your Mobile Application. You already know how many of your customers are “Very Satisfied” but you want to make sure that the new version doesn’t negatively impact their satisfaction. You can set an Alert to be triggered if there’s a 10% drop in your “Very Satisfied” clients.


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 as 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.

20% increase in a specific event will give you a useful insight:


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.

The number of users using your product is an important metric to follow, as well. A decreasing 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 most likely have a negative impact on sales, and the ongoing decrease will affect your business at a critical level in the long run. To always be on top of both situations, you can create an alert in the early stages and create an Alert for when urgent action is needed.


How can I set Alerts?

Setting an Alert on Countly has 4 simple and easy steps:

  1. Enter the Countly left main navigation menu and click on the Utilities > Alerts menu item.
  2. Define the data type you want to create an Alert for. This can be either an Event, a Metric, a Crash, or a Rating.
  3. Then, determine the application for which the data selected is relevant and the conditions that will trigger the alert. 
  4. Save the Alert. Note that each field is mandatory, so a selection must be made in all of them in order for the “Create a New Alert” button to be enabled.

Your new Alert will be displayed in the Alerts table. From now on, you are going to get an email comparing the values from today with those from yesterday, but only if an Alert is triggered. If your Alert is stopped by disabling the toggle button, you will stop receiving alerts

Reports: Get summary data via email

Countly can send email reports to you or your colleagues periodically. In order to do this, go to Utilities > Email Reports. Here you will be able to define email reports for Analytics-, Crash-, Revenue-, or Event-related data.


Adding a new report

First, we are going to add a new email report to see how it works. When you go to Utilities > Email Reports, you will probably see an empty table. Click on the “Create new report” button on the top right corner of the screen.

In this screen, you are going to set the following parameters:

  1. Report name: what the email report will be called.
  2. Emails: Users who are going to receive this email report.
  3. Report Type: Core Reports provide data from the plugins used like Events, Analytics, Crash, etc.; while Dashboard Reports will be reflected in a custom dashboard, letting you select the dashboard in which you want to replicate the Report.
  4. Applications to receive reports from: Apps for which this Report will be generated. You can define a Report for as many apps as you want.
  5. Data included: A selection of different metrics that should be included in the Report. You can select as many metrics as you want.
  6. Frequency: Daily, weekly, or monthly emails.
  7. Time: Email sending time based on the selected timezone of the application.


When you click on “Create New E-mail Report”, your screen will look like the following. Email Reports will now be generated depending on the selected frequency. If your automated Report is stopped by disabling the toggle button, you will stop receiving the email Report.


Note that when you click on the Report overflow menu, you have the option to send an example, preview an email, or delete the corresponding Report.

Was this article helpful?
0 out of 0 found this helpful

Looking for help?