Countly Assistant


The objective for any analytics platform is to provide actionable information. However, Countly (as with most other analytics services) was only providing raw metrics (e.g. number of new users, a number of sessions, etc.) via our dashboard — till our last update.

Insights into what these raw metrics actually mean require a user with a more in-depth understanding of analytics and how to interpret them.

The typical end-user doesn’t have this depth of knowledge (at least not initially), so in order to make Countly more useful and valuable to our customers, we needed to interpret the available data and use it to provide predictive metrics and recommendations on which our dashboard users (not just admins) can act.

Countly Assistant is designed to give you easy to consume insights about your applications, such as active user changes over weeks and top entry/exit points for web. It’ll also give you information about features you are not taking advantage of, like new Countly releases and latest news from Countly team.

In order to make sure that this info is truly clear to understand, useful, and actionable, at minimum we need to answer the following questions:

  • What happened? Examples: a substantial increase in users, increase in crash rate, etc.
  • Why it happened? Due to a specific crash, due to user increase in a specific country?
  • Is this a good or bad thing? More users is a good thing, declining retention is a bad thing
  • What to do about it? These consist of some best practices and recommendations on our website or elsewhere to which we can direct users.

Since these types of recommendations and insights will probably only make sense on an app by app basis, the data should be relevant to the currently selected app. Depending on the app platform (e.g. mobile or web) the insights and recommendations may vary.

With Assistant, you can use “Pinning” to “pin” a specific notification. Those pinned notifications stay on the pane and are always visible. Unpinning a notification takes it back to its original queue level.

Assistant defines all timezones as “app timezone”, not “user timezone”. The reason for this is to eliminate any reporting synchronization problems and eliminate the chance to provide different numbers for different users for similar reports.

With Assistant, you can do great things. Let's have a look at them.

Delivering quick and easy to grasp tips

This notification includes tips and tricks that end user may not have done, but is useful to get most out of Countly to make sure Countly is a better and viable platform for their business. They are shown at most 2–3 times a week.

For example, you are not yet using the Funnel feature, which allows you to follow your users step by step. Thanks to the Assistant, we will transfer this feature to you as well.

Delivering insights

This type of information provides the most insight to end user and should be calculated so that user may not easily grasp it using dashboard.

For example; if your active user count has increased, you can see it as below.

You can also access information such as “Page View, Top install sources, top referrals, session durations” from Assistant.

Showing latest announcements

This includes Countly blog posts from Medium, or new SDK announcements. Since blog is not too often updated, all blogs can appear on notification pane immediately (e.g same day).

For example, when a new blog entry is posted, you will receive a notification as follows. With this feature, you will be constantly aware of any updates in Countly.

We are working to create a great environment for you to get important information instantly and make the best decisions. So we designed the Assistant feature to let you know about what is going on in your product.

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

Looking for help?