Utilities is composed of a set of tools to fine-tune the operation and management of your application in Countly. Nested is this section of your Main Menu, you will find:

Report Manager

The Report Manager feature helps you to handle extensive queries that require significant execution time. It allows you to track and manage these queries easily.

This feature provides detailed information on all reports generated automatically by Countly features when lengthy queries are involved. These reports are auto-generated to save you from waiting and are stored for later access. With Countly 22.03 and newer, accessing running or completed queries is simplified through the recent reports popover within features like Drill and Formula. For an overview of how to use the Report Manager, click here.

Data Manager

The Data Manager feature enables you to plan, manage, edit, delete, and modify Events and Event Segmentations, including performing actions such as transformations on Events or User Properties and managing their data types.

This feature provides you with the capability of managing user actions related to events of your applications. You can create various functionalities that define the event usage and its analytics. It also allows you to control user accessibility. To learn more about using the Data Manager, click here.

Data Populator

The Data Populator feature enables you to populate your application with dummy user data for testing purposes. The Feature has an update that allows you to align the events and other features together in form of conditions, so that the dummy user data generated can form a realistic environment and, thus allowing you to test your applications with real test case scenarios. For an overview of how to use the Data Populator, click here.

Config Transfer

The Config Transfer feature allows you to export the configurations of other features into another instance of Countly. You can export entire A/B testing experiments or Dashboards, and import them to a completely different Countly instance.

Feature Dependencies

Config Transfer of data from specific features is dependent on the availability of those features in the edition you are using. As such, Config Transfer can be implemented in:

• A/B Testing
• Cohorts
• Dashboards
• Formulas
• Funnels
• Data Populator
• Remote Config
• Ratings
• Data Manager Transformations

Getting Started

To start using Config Transfer, go to Main Menu > Utilities > Config Transfer. The default View is the Export Configs View. You can also use Filtering Rules with Config Transfer.

Config Transfer Overview

Understand Config Transfer Views

The Config Transfer feature has two Views:

1. Export Configs: This View allows you to export configs. It is the default Config Transfer view.
2. Import Configs: This View allows you to import configs.

Using Config Transfer

Exporting Configs

To start exporting configs, go to Main Menu > Utilities > Config Transfer. The default view is the Export Configs View.

On the left side of this View (1), you will see all the feature configurations that can be exported. Use the dropdown arrow against any feature configuration to see items under it.

Use the Search bar at the top of the table to look for specific feature configurations. To select any feature configuration to export it, simply select the corresponding check box (2). Select as many feature configurations as you would like to export. You can also select individual items of a particular configuration using the collapsible arrow (3) on the right side of each configuration. As you select configurations, they appear in the Configs to Export table on the right side (4).

To deselect any of the plugin configurations, unchecking them in either the left or right table removes them from the selection to be exported.

You can then download these files to export them. To download the JSON file, you can simply click on the Export as File button (5).

Importing Configs

To import configs, click on the Import Configs tab at the top of the page and go to the corresponding view.

A file downloaded from the Export Config section from any Countly instance can be uploaded in this section by clicking the Browse Link or by dragging and dropping the file onto the white upload area.

Once the file has been selected, the import process can be started by clicking the Import Configs button on the top right corner of the upload area.

The imported configurations will be visible in their respective sections, e.g., imported dashboards would be visible in the Dashboards dropdown.

Dependencies

The dependencies for each exported item are exported and then imported into the new instance without any extra configuration.

For example: If Dashboard A depends on Cohorts x and y, both Cohorts x and y will be exported with the file as well.

Incoming Data Logs

Incoming Data Logs allows you to centralize all the incoming requests from your SDKs, allowing you further explore all requests received, request time, app version, device, location, crashes, performance, and other metrics of the requests.

Getting Started

First of all, make sure Event Logs is enabled. To do so, go to the Sidebar > Management > Feature Management and enable the Incoming Data Logs toggle.

Then, to access Incoming Data Logs at any time, on the Main Menu, go to Utilities > Incoming Data Logs.

Incoming Data Logs Overview

Understanding Incoming Data Logs

This feature logs all requests, originating device, and contents of the latest 1000 requests done to the SDK, something particularly useful during the development stage of your application.

In addition, the logs' data can be segmented based on different types of requests such as sessions, events, metrics, user details, and crashes.

Using Incoming Data Logs

The Incoming Data Logs View includes everything you need to know about the last 1000 requests done with the SDKs to your app.

1. You can visualize all the requests (selected by default) or filter per type. Note that the type will depend on the data types currently being collected by your SDKs.

2. Additionally, you can enable the Auto-refresh toggle button (disabled by default), which will automatically update the logs.

3. Each log entry is shown in a human-readable format. Upon expanding the content of each entry, you will find the actual information sent by the SDK.

SDK Manager

The SDK manager allows you to monitor the SDKs utilized by your application. This feature helps you provide data related to any SDK-related problems to the Countly team so that the problem is understood in a more comprehensive way. This feature also helps your team and your application stay up to date with the latest developments in SDKs by providing you with information on the version of the SDK used by your application. To learn more about the SDK manager, click here.

Location Targeting

Location Targeting allows you to create specific geolocations to use for Push Notifications. Therefore, you will only see this option if your Countly instance corresponds to a mobile application.

First of all, make sure Location Targeting is enabled. To do so, in the Sidebar, go to Management > Feature Management and enable the Geolocations toggle.

After that, you will find Location Targeting in the Utilities section.

There, the View will show you a list of existing geolocations (including the given name, applications in Countly that can use them, and specfic location) as well as the + Create New Location button

By default, the location will be available for all applications, unless you select a specific application.

Compliance Hub

• Supported Countly versions: 18.04 and higher
• Supported Countly SDKs: iOS, Android, Node.js, and web

The Countly Compliance Hub feature helps Countly administrators view and track users' consents, and manage them in one place.

Getting Started

Compliance Hub is enabled by default on each Countly instance and helps you do two things:

1. Collect user consents: Every first-time user/visitor (in web or mobile) should be asked for permission to collect analytics data. This data has several features (e.g. session, crash, view, clicks, etc.) and it should be clearly stated which data would be collected from the end user via a consent form. If a user does not give consent for data collection, no information will be sent until they clearly opt-in.
2. Manage user requests: This feature also creates a "Consents" tab for each user profile (available only in the Enterprise Edition). Any user, in mobile or web, can request their information exported or deleted via a contact form or via an SDK. When a request is retrieved from an SDK, this information can be viewed from that particular user's profile page. Upon reviewing this request, the Countly admin can either export this data and send it to the corresponding user, or delete the user's information altogether.

In order to collect consent, you can use a custom form, or use a form that we provide as examples for each SDK. When you have more than one vendor integrated in your app that collects user data, it is best to use a custom consent manager which will inform those SDKs.

Compliance Hub Overview

SDK Capabilities

Countly SDKs for mobile (iOS and Android) and web pages (Nodejs and web SDK) have the ability to get consent information from users and then send this data to Countly. The SDKs can separately send different individual metric data in case it is required (e.g., metrics, sessions, users, and crashes), send all of them, or not send them at all.

The SDKs can also send feature-based opt-in/opt-out requests for logging purposes for a specific device, instead of a particular user. Hence, users must send their opting choices for each device they have.

Each SDK is initialized without sending any information to a Countly server, and it is possible for each SDK to enable or disable a metric submission feature while the application is running. Hence, a user can opt-in for all metrics, but then decide to opt out from some of them. If there is queued data related to a user, and they choose to opt out, this queue is not sent to Countly.

The SDKs are configured as opt-in by default due to backward compatibility, as is the most common use case for first-party data collection. It is however possible to set an SDK into opt-out mode with the initialization configuration. In such a case, it would work only when specific consents are provided.

Getting Permissions via the SDKs

In order to comply with GDPR, you need to set all your visitors at 'opt-out' by default, and show them a consent form pop-up. At your discretion, in regions where it may be legal to do so, you can also opt-in your users by default and not show this consent form. However, for GDPR you must explicitly ask for permission to track data, explaining what you are tracking and why. Only when the user agrees can you start tracking your users.

When the app starts for the first time, it initializes Countly only after permission is given explicitly by the end user. In your application, you need to give the user a way to opt in/out in case the user changes their mind, and this method is provided by Countly SDKs.

If you want to have a feature-by-feature (e.g., metrics, users, crashes, views, etc.) selection, such as opt-in to crash submissions, but opt-out of views, you would need to manage the user preferences yourself, storing them persistently and starting or calling Countly features enabling methods based on those preferences upon each app start. There are examples of how to do that inside each SDK documentation where sending consent information is supported.

Using Compliance Hub

The Compliance Hub feature is enabled by default in all Countly instances. If, for some reason, you would like to disable it, go to Side Bar > Management > Feature Management and disable the Data Compliance Hub toggle.

To use Compliance Hub, go to Main Menu > Utilities > Compliance Hub.

The Compliance Hub feature has four Views:

1. Metrics: View data compliance metrics (e.g., sessions, events, views, clicks, forms, users, etc.) per metric, in a time-series graph. It shows all incoming requests about consents, e.g., both opt-ins and opt-outs.
2. Users: A visitor list with consent history. In this View, you can see each visitor's consent history and also export data of the corresponding user.
3. Consent History: List of all opt-in and opt-out requests, based on any metrics (e.g., sessions, events, views, etc.)
4. Export/Purge History: List of all exports and removals in a single view.

Other than the information above, each user profile (available in Enterprise Edition) has a tab titled Consents, which keeps the user's consent history. If you see a user sending export or deleting consent, you can just export this user's data or remove this user's information altogether from Countly.

These are detailed below.

Metrics View

In the Metrics View you can view all consent requests in a time-series graph, including opt-ins or opt-outs for each feature as shown below. In this screen, orange lines represent opt-outs and blue lines represent opt-ins. You can also filter by metric feature type, e.g., opt-ins and opt-outs by sessions, events, crashes, etc. from the Feature type dropdown menu. You can also showcase data for specific periods using the time buckets on the top right.

Users View

In the Users View, you can see all users' current consent options, broken by User ID, Device, App Version, and Consent Type.

On the right end of each user row, there is a 3-dot ellipsis menu where you can:

1. Go to consent history: Clicking this option will take you to the consent history of that particular user.
   1. • Download user's export data: Downloads user's exported data, including everything that this particular user's device has sent over, e.g., crashes/errors (if any) or events.
        Starting version 22.09.15 export format has been changed. Export is a single .json file. There is an array of objects, in which each describes a single document in different collections.

        [
        ....
        {"_col":"metric_changes63ef551128bad91a3c11d3e7","brw":{"o"...},.......},
        {"_col":"app_users63ef551128bad91a3c11d3e7",......},
        .....
        ]

        All fields except _col are coming from the database. _col is the collection from which data was exported. Before version 22.09.15 downloaded package is in a gzip format (.gz) which includes several JSON files.
2. Purge user's exported data: It completely deletes user's exported data on the server. This does not remove the user data.
3. Purge user's data completely: It deletes user data completely. Use with caution!

You can download the data table information using the Downward Arrow button on the top right of the table.

Consent History View

In the Consent History tab, you will see a historical list of all past consents. You can filter by status, i.e., those who opted-in, opted-out, or all, and metric type (sessions, events, views, etc.). Once you set your desired filter, the data table shows you the user's Device ID, Changes (i.e., opted-in / opted-out), UID, Consent (i.e., features opted-in), App Version, and Time of last change. You can also select a date range for which to populate the data table using the Dropdown Menu button at the top right of the table.

Download the information from any data table by clicking the Downward Arrow at the top right corner.

Export/Purge History View

The Export/Purge History View shows you all export and data removals a Countly admin has executed. Whenever you export or delete user data, is shown here. You can filter them on the basis of data type using the Dropdown Menu button at the top left of the data table. You can also download the report by clicking on the Downward Arrow button at the top right of the table.

Individual User Consents

When the Compliance Hub feature is enabled, each User Profile will have a new tab, Consents. This shows the application user's consent history, along with several actions you can take.

When you click on the 3-dot ellipsis menu on top-right hand side of the screen, you will see 3 options by default:

1. Export: Exports this app user's data and make it available for download later. This option does not directly download app user's data.
2. Purge user's data completely: This option purges this app user's data. Use with caution!
3. Create message: Opens the Push Notification panel so you can let this user know that their app data is being wiped. This option is only shown if the user has a push notification token obtained and sent via a mobile app. You can do this only before deleting the app user data, since push tokens will be invalidated.

When you export an app user data, there will be a 4th and 5th option shown here, Download user's exported data and Purge user's exported data, which downloads exported user data and deletes the exported data on Countly, respectively. Note that deleting exported data does not delete the user's data previously collected directly, and this user will be able to send data from the applications.

Compliance Hub APIs

Countly has several API sets that helps you remain compliant with several regulations in your country, or worldwide. This is useful especially if you send data to Countly not via SDKs, but via exposed Countly APIs.

Right to be forgotten: https://resources.count.ly/v1.0/reference#iapp_usersdelete

Right for retrieving user data: https://resources.count.ly/v1.0/reference#iapp_usersexport https://resources.count.ly/v1.0/reference#iapp_usersdeleteexportfilename https://resources.count.ly/v1.0/reference#oapp_usersdownloadfilename

Right for rectifying stuff (this is not in API, but in SDK):https://resources.count.ly/v1.0/reference#iapp_usersupdate

Symbolication Logs

You might come across a situation when trying to symbolicate a crash, it does not produce a symbolicated result after initiating it.

This means that there was a problem while trying to symbolicate your crash. To get more information on the problem, you can check out the symbolication logs to understand what failed, and how to mitigate the problem.

After the issue which caused the failure has been fixed, you may rerun that symbolication task.

Filtering Rules

Filtering Rules in Countly helps you take control of the data in your database by allowing you to block certain events or session data. This is important for keeping your database tidy and ensuring that only relevant information is stored, which can also boost server performance.

Key Functions:

• You can easily filter out data based on things like IP address, browser type, or event type, which helps prevent unnecessary clutter.
• By excluding irrelevant entries, you improve the quality of your data, making it easier to analyze and make decisions.
• While Filtering Rules do use some server resources to process incoming data, they ultimately help reduce the amount of data stored, lightening the load on your server.

Using Filtering Rules allows you to manage your database so that it only includes data that truly adds value to your operations. To learn more about Filtering Rules in detail, click here.

FAQ

Can we create Funnels in Data Populator?

Yes, you can create Funnels in Data Populator for testing purposes, which will also lead to a perfect testing scenario, as the steps of the funnel will be defined by the Data Populator.

In order to enter a funnel, each user generated by the Populator must trigger at least the first event in the defined funnel sequence.