Modifying app-level configuration overrides requires Global Admin privileges.
App-level configuration overrides allow you to customize specific settings on a per-application basis. When an override is set for an app, it takes precedence over the corresponding global setting configured in Management > Settings. This is useful when different apps on the same Countly Server have different requirements for data processing, limits, or feature behavior.
To configure app-level overrides, in the Sidebar, go to Management > Applications, select the app you want to configure, and scroll down to the feature-specific settings sections in the app management panel.
How App-Level Overrides Work
When you set an app-level override, the global setting is ignored for that specific app. All other apps without an override continue to use the global value. If you later remove an app-level override, the app reverts to the global setting.
App-level overrides are only available for a subset of settings. Not all settings from Management > Settings can be overridden at the app level. The sections below list every setting that supports this functionality.
Access-Control-Origin
Allows you to configure a per-app Access-Control-Origin value. This specifies which origins are permitted to make cross-origin requests to the Countly API for a specific application.
| Setting | Description |
|---|---|
| Allow Access-Control-Origin |
List separate origins (including https://) per
line to allow cross-origin requests from those domains for
this app.
|
API Settings
The following API settings can be overridden per application. These are the same settings documented in the API Settings article.
- Safer API responses
- Maximal Session Duration
- Track country data
- Track city data
- Max unique event keys
- Max segmentation in each event
- Max unique values in each segmentation
- Metric limit
- Session cooldown
- Total users
- Prevent duplicate requests
- Record metric changes
- Trim trailing and ending spaces
Concurrent Users
Provides a per-app action to reset the maximum concurrent users value. For more information on Concurrent Users settings, refer to the Concurrent Users section of the Feature Management Settings article.
- Reset max concurrent users
Consolidate
Allows you to configure which other apps should consolidate their data into this app.
| Setting | Description |
|---|---|
| Consolidate | Select one or more apps whose data should be consolidated into this app. Data from the selected apps is merged together for unified reporting. |
Crashes
The following Crashes settings can be overridden per application. These are the same settings documented in the Crashes section of the Feature Management Settings article.
- Smart stack trace preprocessing
- Smart regexes to remove information from stacktrace
- Crash grouping strategy
Drill Settings
Drill app-level overrides are only available when the Drill plugin is installed and require Global Admin privileges.
The following Drill settings can be overridden per application. These are the same settings documented in the Drill section of the Feature Management Settings article.
- Limit of items in big list
- Record Big Lists
- Cache threshold
- Union with data from old collections
- Correct user estimation
- Max user custom properties
- Dropdown item limit
- Limit result in query with BY
- Record view actions in Drill
- Record crash data in Drill
- Record Drill Meta
- Record push actions in Drill
- Record pushes sent in Drill
- Record session data in Drill
- Record star rating data in Drill
- Record performance monitoring data in Drill
- Record consent data in Drill
- Record view data in Drill
Feedback
The following feedback widget settings can be configured per application. These allow you to customize the appearance of feedback widgets for the specific app.
| Setting | Description |
|---|---|
| Main color | The primary color used in feedback widgets for this app. |
| Font color | The font color used in feedback widgets for this app. |
| Feedback logo | A custom logo image displayed in feedback widgets for this app. |
Incoming Data Logs Settings
Incoming Data Logs app-level overrides are only available when the Logger plugin is installed and require Global Admin privileges.
The following Incoming Data Logs settings can be overridden per application. These are the same settings documented in the Incoming Data Logs section of the Feature Management Settings article.
- Set incoming data logging state
- Set incoming data logging limit per minute
JIRA for Crashes
The following JIRA integration settings can be configured per application. These are the same settings documented in the JIRA Integration subsection under Crashes in the Feature Management Settings article.
- Project
- Type
- To Do states
- Doing states
- Done states
Journeys
The following Journey Engine setting can be overridden per application. This is the same setting documented in the Journeys section of the Feature Management Settings article.
- Cooldown
Push Notifications
The following Push Notifications settings can be configured per application. These control the push provider credentials, rate limiting, and test users for the specific app.
iOS Settings
| Setting | Description |
|---|---|
| Authentication type | The authentication method used for Apple Push Notification service (APNs). Select between token-based (P8) or certificate-based authentication. |
| Key file (P8) | The Apple P8 key file used for token-based APNs authentication. |
| Key ID | The Key ID associated with the P8 key file, found in your Apple Developer account. |
| Team ID | Your Apple Developer Team ID. |
| Bundle ID | The Bundle Identifier of the iOS app that receives push notifications. |
Android (Google FCM)
| Setting | Description |
|---|---|
| Service account JSON file | The Google Cloud service account JSON file used to authenticate with Firebase Cloud Messaging (FCM). |
Android (Huawei Push Kit)
| Setting | Description |
|---|---|
| App ID | The Huawei App ID for Push Kit integration. |
| App Secret | The Huawei App Secret for Push Kit authentication. |
Rate Limit
| Setting | Description |
|---|---|
| Maximum number of notifications scheduled per period | The maximum number of push notifications that can be scheduled within the defined period for this app. |
| Period duration (seconds) | The time window (in seconds) for the rate limit. |
Test Users
| Setting | Description |
|---|---|
| User definition | Define test users who can receive test push notifications before sending to all users. You can send test notifications to these users to verify push notification content and delivery. |
Revenue Analytics
The following Revenue settings can be configured per application. These control how in-app purchase events are tracked and which currency is used for the specific app.
| Setting | Description |
|---|---|
| Revenue events | Select one or more events that represent in-app purchases for this app. |
| Default currency | The default currency code used for revenue calculations for this app. |
User Profiles
The following User Profiles setting can be overridden per application. This is the same setting documented in the User Profiles section of the Feature Management Settings article.
- Sampling Threshold
FAQ and Troubleshooting
Where do I find app-level overrides?
In the Sidebar, go to Management > Applications, select the app, and scroll down. The override sections appear below the standard app configuration fields.
What happens if I do not set an app-level override?
The app uses the global setting from Management > Settings. App-level overrides only take effect when explicitly configured.
Can I override any setting at the app level?
No. Only the settings listed in the sections above support app-level overrides. All other settings apply globally to all apps on the server.
Who can configure app-level overrides?
Only users with Global Admin privileges can view and modify app-level configuration overrides. App Admins can view the overrides but cannot change them.