Feature Management Settings are part of the Settings in Countly. To access them, in the Sidebar, go to Management > Settings, then browse the Feature Management Settings list below the Core Settings section.
The Feature Management Settings section allows you to configure the behavior of individual features and plugins installed on your Countly Server. The parameters you set here directly affect how data gets displayed and collected by the corresponding feature.
These settings are independent of whether a feature is enabled or disabled in the Feature Management section. A feature can be disabled but still have its settings configured for when it is re-enabled.
Changes to Feature Management settings require Global Admin privileges. For detailed information on the meaning and impact of each setting, please refer to the User Guide corresponding to each particular feature.
The Feature Management Settings list is sorted alphabetically and the available entries depend on which plugins are installed on your server. Below is a reference for each feature's settings as they appear in the configuration panel.
Active Directory
| Setting | Description | Default |
|---|---|---|
| Hide login form | Hides the standard login form when Active Directory authentication is enabled. | Enabled |
AI Assistants
Configures the AI assistant integrations available in Countly.
| Setting | Description | Default |
|---|---|---|
| Provider API key | API key provided by Countly. If you want to use your own API key with OpenAI, set the API base URL to https://api.openai.com/v1 and enter your key here. |
(empty) |
| Provider API base URL | Base URL of the Countly AI provider. Set to https://api.openai.com/v1 to use OpenAI directly with your own API key. |
https://ai-gateway.count.ly/v1/openai |
| Enable Drill Agent | Enables the Drill Agent to help you create, execute, and analyze Drill queries using natural language. | Disabled |
| Enable Cohort Agent | Enables the Cohort Agent to help you create cohorts using natural language. | Disabled |
| Enable Funnel Agent | Enables the Funnel Agent to help you create Funnels using natural language. | Disabled |
Attribution
Configures campaign tracking and attribution behavior.
| Setting | Description | Default |
|---|---|---|
| Allow custom links | Allows users to define the code part of the URL themselves. | Disabled |
| Provide campaign data | Provides campaign data to redirect URLs as query parameters. | Enabled |
| Forward query parameters | Forwards query parameters from campaign URL to redirect URL. | Disabled |
| Segment value limit Performance Data Processing Interface |
Maximum number of unique values in each campaign link segmentation. | 100 |
| Campaign domain | Provides a separate campaign domain that resolves to this server. | (empty) |
| Reattribution | Normally a campaign is only assigned if a user does not have any campaign. If enabled, the user campaign is reassigned to the newest one. | Disabled |
Audit Logs
| Setting | Description | Default |
|---|---|---|
| Disable IP Tracking | When enabled, IP addresses are not recorded in audit log entries. | Disabled |
Cohorts
Configures regeneration intervals and real-time behavior for the Cohorts feature.
| Setting | Description | Default |
|---|---|---|
| Regeneration Frequency | Cohorts are regenerated at the selected frequency. If a cohort regeneration takes longer than the selected frequency, it is regenerated at the next closest frequency. If the Realtime Cohorts setting is enabled, this setting only affects the adjustment frequency of the number of total users in a cohort. Available options: every 5 minutes, every 30 minutes, every hour, every 3 hours, every 12 hours, and every 24 hours. | Every hour |
| Realtime cohorts | If enabled, cohort calculation is done in real time. Upon enabling this setting, cohorts are in "Loading" status until the initial setup is done, at which point the status automatically switches to "Live." Users going in and out of a cohort are registered in real time for cohorts in "Live" status. | Enabled |
Concurrent Users
Manages update intervals for online user tracking in the Online Users feature.
| Setting | Description | Default |
|---|---|---|
| Read interval (in seconds) | How often to write current online users to the database. | 10 |
| Online time (in seconds) | Threshold for a user to be considered as online. If a user has not sent data within this period, they are considered offline. | 180 |
| Sampling interval (in seconds) | How often to sample aggregated data for online user statistics. | 30 |
| Alert interval (in minutes) | How often to check online user data for set alert thresholds. | 3 |
Countly Cognito
Configures AWS Cognito authentication integration.
| Setting | Description | Default |
|---|---|---|
| Base URL | The base URL of your AWS Cognito domain. | (from config) |
| Global admin group | The Cognito user group that maps to Global Admin privileges in Countly. | (from config) |
| URL expire minute | Expiration time (in minutes) for authentication callback URLs. | (from config) |
Crashes
Configures crash grouping, reporting limits, and symbolication server settings.
| Setting | Description | Default |
|---|---|---|
| Amount of reports displayed Interface |
Number of reports to display in each crash group's page. | 100 |
| Crash grouping strategy | How crashes should be grouped together. Available options: "Error and file where error happened" and "By full stack trace." | Error and file where error happened |
| Smart stack trace preprocessing | Merges together more groups by removing dynamic content based on heuristics. | Enabled |
| Smart regexes to remove information from stacktrace Interface |
JavaScript regex as string, one regex per new line (example: {.*?}). Used to remove variable parts from stack traces during preprocessing. |
{.*?} and /.*?/
|
| Latest crash update | Updates the latest crash in a crash group even when the incoming crash has the same app version as the latest crash. | Disabled |
| Maximum custom field keys Performance Data Processing Interface |
Maximum number of unique custom field keys to keep in a crash group. Do not set a large number as it increases the size of crash group data. | (system default) |
| Activate custom field cleanup job | When enabled, a background job periodically cleans up custom field keys that exceed the maximum custom field keys limit in crash groups. | Disabled |
| Automatic symbolication | Symbolicates crashes as soon as they arrive or when the symbol file for their version is uploaded. Enabling this option may be resource-intensive. | Disabled |
| Symbolication Server URL | URL for the server that performs symbolication. You do not have to change this unless you have an internal server for symbolication. | https://symbolication.count.ly |
| Custom external domain | Used to configure an external public domain for a Countly Server that is hosted internally. Enables the symbolication server to reach your Countly Server. | (empty) |
| Symbolication Server API KEY | API key for the provided symbolication server. | (empty) |
JIRA Integration
Configures the JIRA integration for creating JIRA issues directly from crash reports.
| Setting | Description | Default |
|---|---|---|
| API URL | URL of the JIRA server, for example https://foobar.atlassian.net. |
(empty) |
| API consumer key | An arbitrary key supplied by the Countly admin. It must match the one set in the JIRA application link. | (empty) |
| Client private key | Private key complementing the public key set in the JIRA application link. | (empty) |
| Callback URL | Fully qualified URL of the API server of this Countly instance, for example https://foobar.count.ly. |
(empty) |
| Login to JIRA | Authorizes Countly to synchronize crashes using your JIRA account. | — |
Dashboards
Controls sharing and public access for custom Dashboards.
| Setting | Description | Default |
|---|---|---|
| Allow Dashboard Sharing | Enables dashboard sharing for users to share a dashboard with other users. If set to off, dashboards cannot be shared with others. | Enabled |
| Allow public dashboards | Allows sharing dashboards with all Countly dashboard users. | Enabled |
Data Manager
Configures event validation, data masking, and schema enforcement.
Manage Events
| Setting | Description | Default |
|---|---|---|
| Manage Events | Determines how unplanned events are handled. Available options: "Allow unplanned events" and "Don't allow unplanned events." When set to "Allow unplanned events," unplanned events are visible on all features and tagged as "Unplanned" in Data Manager. When set to "Don't allow unplanned events," unplanned events are hidden, which is recommended to keep your data clean. | Allow unplanned events |
| Trigger Validation For Unplanned Events | When enabled, validation errors from Data Manager are triggered for unplanned events. Enabled state is highly recommended if Manage Events is set to "Don't allow unplanned events." | Enabled |
Validation Settings
| Setting | Description | Default |
|---|---|---|
| Perform Schema Validations for Incoming Data | For disabled state, you do not get any errors for events, segments, or data type validations. Only the Global Validation Regex works for disabled state. | Disabled |
| Global Validation Regex | A global regular expression to match against data sent by the SDK. | (empty) |
| Segment Level Validation Action Data Processing Interface |
Action to take when a segment-level regex matches. Options: WARNING or DROP. | WARNING |
| Global Validation Action Data Processing Interface |
Action to take when a global regex matches. Options: WARNING or DROP. | WARNING |
| Label for data dropped by Global Validation Regex | The masking value used to replace data matched by the Global Validation Regex. | [CLY_REDACTED] |
| Enable data masking Data Processing Interface |
Once enabled, Data Manager masks all data from database responses based on settings configured in the Data Manager plugin. Data redaction does not happen in Compliance Hub and Audit Logs. | Disabled |
Drill
Configures how raw event data is recorded, cached, and queried in the Drill feature.
Limitation Settings
| Setting | Description | Default |
|---|---|---|
| Dropdown item limit Interface |
Limits how many items to show in a dropdown element. | 100 |
| Max user custom properties Interface |
How many custom user properties can be stored in Drill. | 20 |
| Limit result in query with BY Interface |
Maximum results to display when you perform a query with BY. | 10 |
| Limit of items in big list Performance Data Processing Interface |
Limits how many items in big lists should be stored. A big list is a separate input for segmentation queries that fetches information from the server when needed in limited amounts. | 1000 |
Data Ingestion
| Setting | Description | Default |
|---|---|---|
| Record Big Lists | If true, lists are promoted to big lists instead of becoming text inputs. | Enabled |
| Record session data in Drill | Enables Drill to record data about user sessions. | Enabled |
| Record view data in Drill | Enables Drill to record data about user views. | Enabled |
| Record view actions in Drill | Enables Drill to record data about user actions in views. | Enabled |
| Record push actions in Drill | Enables Drill to record data about actions on push notifications. | Enabled |
| Record pushes sent in Drill | Enables Drill to record data about sent push notifications. | Enabled |
| Record crash data in Drill | Enables Drill to record data about crashes. | Enabled |
| Record star rating data in Drill | Enables Drill to record data about star ratings. | Enabled |
| Record performance monitoring data in Drill | Enables Drill to record data about Application Performance Monitoring. | Enabled |
| Record consent data in Drill | Enables Drill to record data about consent changes. | Disabled |
| Record Drill Meta | Records meta information that allows building the Drill UI for querying data. | Disabled |
| Batch Data Inserts | Batching inserts results in higher throughput, but can lead to inconsistencies as there are no acknowledgments if documents were successfully inserted. | Disabled |
Cache Settings
| Setting | Description | Default |
|---|---|---|
| Cache threshold | Queries taking longer than this set duration (in milliseconds) are cached. Queries that contain a BY rule follow the "Cache retention duration" setting, while others default to a 10-minute cache. | 10000 |
| Cache BY query results | When enabled, results for queries using the BY rule are always cached in the database, accelerating data retrieval for matching rules. If disabled, queries are cached based on the "Cache threshold" setting. | Enabled |
| Cache retention duration for BY queries | The duration (in seconds) after which BY query result caches are cleared. | 7200 (2 hours) |
Other Drill Settings
| Setting | Description | Default |
|---|---|---|
| Correct user estimation | Uses Drill data to correct user estimation in aggregated views. | Enabled |
| Prevent disabling Correct user estimation | When enabled, users cannot disable the "Correct user estimation" setting. This ensures estimation correction remains active at all times. | Disabled |
| Union with data from old collections | This setting should be enabled only if some needed data is still stored in old Drill data collections. The moment it is no longer needed, it should be toggled off. | Enabled |
| Record data in event timeline | This data is used for Flows calculations and for displaying all user history in the user profile. If disabled, the timeline must be reset and regenerated to have proper data after re-enabling. | Enabled |
Email Reports
| Setting | Description | Default |
|---|---|---|
| Secret key for unsubscribe link | Secret key must be 32 characters for AES 256. Used for encrypting report data and unsubscribe links. Auto-generated if not set. | (auto-generated) |
Feedback
Configures the appearance of feedback widgets (NPS, Surveys, and Ratings).
| Setting | Description | Default |
|---|---|---|
| Main Color | The main color of the feedback widget. | #0166D6 |
| Font Color | The font color of the feedback widget. | #FFFFFF |
| Feedback logo | Custom logo image displayed in feedback widgets. | (empty) |
Flows
Controls the generation and display parameters for user Flows.
| Setting | Description | Default |
|---|---|---|
| Sampling threshold | Number of session documents before sampling starts being used. | 2000000 |
| Max sampling size | Maximum number of session documents used for sampling flows. May affect performance negatively. | 5000000 |
| Regeneration interval | Minimum flow regeneration interval. If a flow regeneration takes longer than the selected duration, it is regenerated in the next closest interval. Available options: every 5 minutes, every 30 minutes, every hour, every 3 hours, every 12 hours, and every 24 hours. | Every hour |
| Nodes count Interface |
Maximum number of nodes to be calculated in a single step. | 10 |
| Max depth Interface |
Flows do not calculate more steps than this value. Increasing this number noticeably increases the calculation time of each flow report. | 20 |
| Skip auto flows | When enabled, Countly does not automatically recreate the "Basic view flow" and "Basic event flow," even if they are deleted. Keep this option disabled if you need to save data resources or are not interested in these flow examples. | Disabled |
Funnels
Configures limits and caching for the Funnels feature.
| Setting | Description | Default |
|---|---|---|
| Funnel step limit | Number of steps that can be generated and used in a single funnel. | 8 |
| Funnel caching | If funnels are slow to view in real time, you can enable this option to cache the result. They are automatically updated once per day for the selected default period. | Enabled |
| Funnel caching period | Sets the default period that is used for pre-generating cached funnel data daily. Cached data only has a fast response in this selected period. | 30 |
Hooks
Controls processing and rate limiting for the Hooks (automation) feature.
| Setting | Description | Default |
|---|---|---|
| Action Batch Processing Size | The number of actions to be processed in each batch. Set to 0 for no batching. | 0 |
| Refresh Rules Period | The interval (in milliseconds) between each refresh of the rules. | 3000 |
| Action Pipeline Interval | The interval (in milliseconds) between each batch of actions. | 1000 |
| Request Limit Data Processing |
The maximum number of requests that can be sent to the endpoint within the time window. Set to 0 for no limit. | 0 |
| Time Window for Request Limit | The time window (in milliseconds) for the request limit. | 60000 |
Incoming Data Logs
Controls the SDK request logging behavior per app. These settings can also be overridden at the app level.
| Setting | Description | Default |
|---|---|---|
| Set incoming data logging state Performance Data Processing Interface |
Controls the incoming data logging behavior. Available options: "On," "Off," and "Automatic." When set to "On," only the last 1,000 requests are saved. When set to "Off," no requests are logged. When set to "Automatic," requests continue to be logged until the limit per minute is reached. | Automatic |
| Set incoming data logging limit per minute Performance Data Processing Interface |
Incoming data logging turns off automatically when the number of requests logged per minute reaches this limit. This only applies when the state is set to "Automatic." | 1000 |
Journeys
Controls the engagement queue cooldown behavior for the Journey Engine (used by Journeys and Content features).
| Setting | Description | Default |
|---|---|---|
| Engagement Queue Cooldown | The minimum interval (in hours) between consecutive content deliveries to the same user. This ensures users are not overwhelmed with notifications or messages. | 24 |
Okta
| Setting | Description | Default |
|---|---|---|
| Hide login form | Hides the standard login form when Okta authentication is enabled. | Enabled |
Open ID Connect
Configures the appearance and behavior of the login page when OIDC is enabled.
| Setting | Description | Default |
|---|---|---|
| Hide Login form | If enabled, the user does not see the login form and can only use Open ID Connect. | Disabled |
| Login Button Image | Some Open ID Connect providers require specific styling. Use this to provide custom images for Login buttons. | (empty) |
| Login Text | If you are not providing an image, you can provide custom text for the Login button. | (empty) |
| Use PKCE Flow | If enabled, the application uses PKCE (Proof Key for Code Exchange) flow for enhanced security. Recommended for public clients. | Disabled |
| Revalidate tokens | If true, tokens are periodically revalidated and the user is logged out if they are signed out of the Open ID provider. If false, it relies on Countly internal session management. | Disabled |
Push Notifications
Configures proxy, rate limiting, and connection settings for the Push Notifications feature.
| Setting | Description | Default |
|---|---|---|
| Proxy Hostname | Hostname or IP address of HTTP CONNECT proxy server to use for communication with APN and FCM when sending push notifications. | (empty) |
| Proxy Port | Port number of the proxy server. | (empty) |
| Proxy Username | Username for proxy server HTTP Basic authentication (if needed). | (empty) |
| Proxy Password | Password for proxy server HTTP Basic authentication (if needed). | (empty) |
| Do NOT check proxy HTTPS certificate | Allows self-signed certificates without CA installed (if needed). | Disabled |
| Time factor for exponential backoff between retries | Exponential backoff factor (in milliseconds) applied between connection retries. | 1000 |
| Number of connection retries | Number of times to retry on recoverable connection errors when communicating with APN or FCM. | 3 |
| Bytes in binary stream batches | Bytes mode streams high water mark. Controls the byte-level batching for binary stream operations. | 10000 |
| Maximum number of same type connections | Maximum number of concurrent connections of the same type (e.g., APN or FCM). | 5 |
| Maximum number of connections in total | Maximum number of total concurrent connections across all push notification providers. | 10 |
| Number of notifications in stream batches | Object mode streams high water mark. Controls how many notifications are batched in each stream operation. | 400 |
| Send notifications scheduled up to this many ms into the future | Sends notifications scheduled up to this many milliseconds into the future. | 60000 |
| Message timeout | Timeout (in milliseconds) for a message that has not been sent yet. Messages exceeding this timeout receive a TooLateToSend error. | 3600000 (1 hour) |
| Set content-available to 1 by default for iOS | When enabled, all iOS push notifications include content-available: 1 by default, allowing background processing. |
Disabled |
Recaptcha
Configures Google reCAPTCHA protection for the login page.
| Setting | Description | Default |
|---|---|---|
| Enable Recaptcha | Enables or disables reCAPTCHA on the login page. | Enabled |
| Site Key | The Google reCAPTCHA site key for your domain. Get site key from reCAPTCHA admin. | (empty) |
| Secret Key | The Google reCAPTCHA secret key for server-side verification. Get secret key from reCAPTCHA admin. | (empty) |
Remote Config
Configures limits for the Remote Config feature.
| Setting | Description | Default |
|---|---|---|
| Maximum allowed parameters Data Processing Interface |
Maximum number of parameters that are allowed per application. | 2000 |
| Conditions per parameter Data Processing Interface |
Maximum number of conditions that are allowed per parameter by any application. | 20 |
Retention with Segments
Controls the number of days shown in the Retention feature.
| Setting | Description | Default |
|---|---|---|
| Span | The number of retention period columns displayed in the retention table. | 10 |
Slipping Away
Defines the inactivity thresholds (in days) used to categorize users as slipping away. Each period represents a tier of inactivity.
| Setting | Description | Default |
|---|---|---|
| Period 1 | Number of days of inactivity for the first tier. | 7 |
| Period 2 | Number of days of inactivity for the second tier. | 14 |
| Period 3 | Number of days of inactivity for the third tier. | 30 |
| Period 4 | Number of days of inactivity for the fourth tier. | 60 |
| Period 5 | Number of days of inactivity for the fifth tier. | 90 |
Sources
| Setting | Description | Default |
|---|---|---|
| Maximum character length for source name Data Processing Interface |
Sets a limit for source name length. Characters beyond the limitation value are ignored. | 100 |
Two Factor Authentication
| Setting | Description | Default |
|---|---|---|
| Enforce globally | When enabled, users without Two Factor Authentication enabled are asked to set it up. | Disabled |
User Profiles
Controls limits and behavior for the User Profiles feature.
| Setting | Description | Default |
|---|---|---|
| Maximum values in each custom property Performance Data Processing Interface |
Maximum number of values per custom property. Increasing this number may affect your server performance. | 50 |
| Maximum number of custom properties Performance Data Processing Interface |
Maximum number of custom properties on User Profiles. Increasing this number may affect your server performance. | 20 |
| Notes on User Profiles | Enables Notes on User Profiles to leave notes to each user profile's details. | Enabled |
| Sampling Threshold | Threshold to start sampling 5% of total records when a breakdown filter is applied. | 100000 |
| Batch size | Number of users to pull and process in the daily user processing job. | 100 |
| Batch cooldown | Amount of milliseconds to wait before pulling the next batch. | 10 |
| App user job | Runs a background job for app users to close sessions and calculate properties. | Enabled |
| Engagement score | Calculates an engagement score for each user based on their activity. | Enabled |
Views
Controls data limits and segmentation for the Views feature.
| Setting | Description | Default |
|---|---|---|
| View limit Performance Data Processing Interface |
Configures how many different view values are reported (all time). | 50000 |
| View name limit Data Processing Interface |
Limits view names to the provided number of characters. | 128 |
| Segment value limit Performance Data Processing Interface |
Configures the value limit for view segments. Having a value over 100 most likely results in segment omission from aggregated data. | 10 |
| Segment limit Performance Data Processing Interface |
Configures a limit for view segments. | 100 |
White Labeling
Allows you to customize the Countly interface branding, including logos, colors, and email settings.
Pre-login Pages
| Setting | Description | Default |
|---|---|---|
| Logo | Logo displayed on the login page. | (empty) |
| Button color | Background color of the login page button. | (empty) |
| Button text color | Text color on the login page button. | (empty) |
System
| Setting | Description | Default |
|---|---|---|
| Page title | Custom title displayed in the browser tab. | (empty) |
| Favicon | Custom favicon for the browser tab. Accepts PNG, GIF, or ICO formats. | (empty) |
| Sidebar logo | Logo displayed in the top-left corner of the Sidebar. | (empty) |
| Active menu item color | Color of the active Sidebar menu item. | (empty) |
| Email address to send emails from | Sender address displayed in outgoing emails from Countly. | (empty) |
| Company name to use in emails | Company name displayed in the footer of outgoing emails. | (empty) |
| Sidebar Footer Label | Custom footer text displayed at the bottom of the Sidebar. | (empty) |
Other White Labeling Settings
| Setting | Description | Default |
|---|---|---|
| Countly newsletter subscription | When enabled, all dashboard users receive a prompt asking if they are interested in subscribing to the Countly newsletter. When disabled, the prompt is shown exclusively to Global Admin account holders. | Enabled |
App-Level Configuration Overrides
Some feature settings can be overridden at the application level. This means you can have different configurations for different apps on the same server. App-level overrides take precedence over the global settings. For a complete list of settings that support app-level overrides, refer to the documentation below.
FAQ and Troubleshooting
Why do I not see certain feature settings?
Feature settings appear dynamically based on which plugins are installed on your server. If a plugin is not installed, its settings do not appear in the Feature Management Settings list. Contact your system administrator to verify which plugins are installed.
How do I know what each feature setting does?
For detailed information on each setting, refer to the User Guide for the corresponding feature. Most settings include a tooltip or helper text that describes their purpose when you hover over the setting label in Countly.
Do feature settings affect disabled features?
Feature settings are independent of whether a feature is enabled or disabled. You can configure settings for a disabled feature, and those settings take effect when the feature is re-enabled.