Countly can collect data from the webpages of your website, your users' activities in your app, or any custom views that you can report manually. This valuable information will help you understand how your users are using your app or website and which are the most popular sections that the users visit.
On the main page, you can select multiple views and compare them by metrics like:
- Total Users who accessed this view
- New Users who accessed this view for the first time
- Total Visits of a specific view
- Duration, which shows the average time spent per visit on this view
- Landings on this view, for users who started your application with this view or landed on your webpage
- Exits, which is how many users exited your app or website from this view or webpage
- Bounces, which shows when a user started and exited from the same view, without viewing other views
- Average scroll, which shows how much users scrolled down to the page (in %)
Note that you can also remove a view from the same table. If a view is deleted, then data for the view is also deleted, but not blocked. Hence, if the SDK or app sends the view again, it would reappear with new data.
On the top of the tabular list of views, click on the
Edit views button, which will take the editing page below:
It allows you to change the displayed name for each view in the table. This is useful when there is incoming data with long addresses so renaming makes it more readable. It is possible to make multiple changes at once, as well as deleting a view altogether using the 3-dot ellipsis menu on the right each view. After all the changes are done, click on
Apply changes in the top-right of the screen.
Views per Session (View Frequency)
The Views plugin also provides an overview of how many views has a user visited during a session, which is divided into buckets.
Views per Session is in the Understand section of your Countly Dashboard, under the Engagement category.
Last View Segment
This plugin also stores a user's last accessed a particular view or web page, letting you analyze and compare views. This is powered by Drill, which allows you to further segment your analysis, incorporating other plugins like Crash Analytics or User Profiles.
The Heatmaps for Web plugin is available only in Countly Enterprise.
Heatmaps allow you to see how your users interact with your website. Thus, it is available for web analytics only, and should be enabled from web SDK accordingly. You can view a Heatmap (whether it is Click or Scroll) by going to
Analytics > Page Views and clicking on the
Heatmap link on the table for the corresponding page.
Click Heatmaps allow you to see where your users usually click on your website. It also allows you to switch among different resolutions to see visitor behaviors in various devices.
Note that browsers do not allow loading HTTP iframe content on HTTPS websites. For this reason, if you are using HTTPS on your Countly instance, you will only be able to view HTTPS content and no HTTP page content will be visible.
Scroll Heatmaps will give you a clear overview of how far users scroll to in your page, giving you actionable data to position important content according to the average fold, or point out whether users are actually missing parts of pages that they should not.
Just like in Click Heatmaps, you can also segment your users by device, e.g desktop, tablet or mobile.
You might be in a situation where the Heatmaps simply will not show up on your application. This section will guide you through proper setup of Heatmaps on your application.
When viewing Heatmaps, the SDK loads the script heatmaps.js onto your application which in turn, loads some other scripts, styles, and fonts, displaying the Heatmap for the current view. The source for all these scripts is your Countly server. So you might want to allow loading scripts from a source that is different from your applications source (if your application and Countly have different origins).
Here are the scripts that you want to allow your application to load from the Countly server incase you are not allowing them: