In this glossary you'll find explanations to abbreviations and other terms you see in articles and Countly dashboard.
- Total users: Number of unique devices your application is used from.
- New users: Number of first time users.
- Returning users: Number of users that have used your application at least one time before. It's simply calculated by subtracting new users from total users for the time period chosen.
- Total sessions: Number of times your application is opened.
- New sessions: Number of times your application is opened by a first time user.
- Unique sessions: Number of times your application is opened from a unique device.
- Time spent: Total time spent inside the application for a given time period.
- Average time spent: Total duration spent using your application divided by total user count.
- Events served: Number of write API requests the Countly Server received for your application.
- Average requests received: Number of write API requests Countly Server receives for each session (includes sessions, session extensions, events, etc).
- Session frequency: Indicator of how frequently users open your application. Usage is distributed into one of the ranges below:
- 1-24 hours
- 1 day
- 2 days
- 3 days
- 4 days
- 5 days
- 6 days
- 7 days
- 8-14 days
- 15-30 days
- 30+ days
- User loyalty: Indicator of how many previous sessions the users had. The number of users is distributed into one of the ranges below:
- Greater than 500
- Funnel: A Countly feature that's used to track the goal completion rates of a step by step path inside your application.
- Drill: A Countly feature that's used to perform advanced segmentation to your apps.
- Bounce: If the user landed on a page/view and exited from the same one without navigating through any other page/view, then it is counted as a bounce.
- Event: A custom metric such as number of button clicks, in app purchase times and amounts, number of times the player finished a game level etc.
- Event count: Total
countreceived for an event key.
- Event sum: Total
sumreceived for an event key.
- Event duration: When calculated, shows the duration of an event, usually in seconds
- Segmentation: Secondary key to slice the data for an event. Can be anything like an event key and it is used to categorize the event data. An example can be using
countrysegmentations for an
in_app_purchaseevent. This way, one can compare
in_app_purchasecount for different
countriesof the user.
- Crash: A crash is a software failure that causes the program flow to break unexpectedly. This term is usually used in the iOS world.
- Exception: An exception is an event which occurs during the execution of a program and that disrupts the normal flow of the program's instructions. This term is usually used in Java / Android worlds.
- Total occurrences: Number of repetitions of a crash or group of crashes.
- Unique crashes: Number of crashes that happen uniquely. In this case, only the first occurrence of a crash type is recorded.
- Non-fatal crashes: A crash that doesn't stop the application but allows it to run after a crash is encountered.
- Fatal crashes: A crash that causes the application to stop and quit.
- Unresolved crashes: Crashes that are not marked as "Resolved" are unresolved crashes.
- New crashes: New crashes that you haven't viewed (marked as red in the bottom table).
- Total users: Number of users using this application.
- Messaging-enabled users: Number of users who opted in to receive push notifications.
- Messages sent: Total number of messages sent for this application within a selected period of time.
- Actions performed: Number of actions performed for this app. An action represents a positive interaction of a user to your message.
- Production users: Users who are actively using your application downloaded from an appstore.
- Test users: Test users who have been testing your application.
- APM / GCM credentials: Credentials that are received either from Apple's or Google's console. This is required for push notifications to work
- Running Surveys: Total number of active surveys.
- Total Responses: Total number of the ratings given by each individual user who responded to an active survey. If a user responds to more than one survey, (i.e. gives scores 2 times for 2 active surveys), this is counted as 2 instances on Total Responses.
- Response Rate: Percentage of the Number of Responses over Total Shown
- Average NPS: Number of the Average Net Promoter Score for all running NPS surveys using the calculation method covered in the NPS documentation