Active Devices (AD)
The number of devices that have been actively using the app for a given date range. If the same device is used on multiple days within the selected date range, it is still counted as one unique active device. In Apptics, you get unique active devices for 30 days, and for more than 30 days, the active device count is cumulative.
Affected devices
The total number of devices affected by a crash that occurred in the selected date range.
Anonymous devices
The total number of devices where users have chosen to share data without revealing their identity, hence allowing data collection without any PII associated.
ANR (Application Not Responding)
A type of error that helps detect instances when an app becomes unresponsive to user input or events within a specified time frame, prompting an Application Not Responding pop-up. This helps developers identify and address performance issues that could affect user experience. ANRs are available within the crash dashboard.
API Key
The unique token generated when you create a new application in Apptics. Application will communicate with Apptics server using this key.
API tracking
It allows you to track the APIs being called from your mobile to your server along with success, failure rates, duration, and the response code.
App stickiness
App stickiness is a measure of how frequently users return to use an app over a specific period of time. It tells you how engaging your app is by showing the percentage of users who come back regularly. It's calculated by taking the average number of unique devices that use the app every day, divided by the total number of active devices that used the app in the last 30 days, and then multiplied by 100 to get a percentage. A higher percentage means users like your app and use it often, while a lower percentage means users might try the app once but don't return.
App Version
A unique string assigned to a specific release of an app in the app's marketplace.
Application ID
An application ID is a unique identifier for your app, referred to as a bundle ID for Apple apps and package name for Android apps. These IDs help differentiate your app from others on a device and in app stores. These IDs are registered when setting up your app in Apptics, either during portal/project creation or later via the Quick Start or Application IDs page. Only platform developers, development leads, or project managers have permission to add, edit, or delete them. You cannot use the same application ID for both the production and development modes.
Brand
An application distributor like Apple, Google, Microsoft.
Bundle ID
A unique identifier for your Apple app.
Conditions
Conditions in remote configuration are the rules defined and associated with the parameters you add.
Crashes
Crashes are unhandled errors while users are interacting with it. These errors happen because of bugs, missing resources, or other issues in the app's code. Zoho Apptics automatically tracks each crash and generates a detailed report that you can view in the console. For each crash, AI-powered analysis helps by offering a summary that includes the cause of the crash, suggested remedies for fixing it, and a conclusion with insights into the root cause.
Custom properties
Custom properties are additional key‑value attributes you define and send along with your events to capture extra context—such as tracking type, item ID, button clicked —beyond Apptics' default metrics. You can add them in your SDK integration (up to 100 per app) as an object of property names and values (string, boolean, numeric), then view and manage them in the console.
Debug View
Debug view is a real-time monitoring tool that helps developers verify whether the SDK integration is working correctly during the development phase. It captures engagement data such as events, sessions, crashes, screens, and custom properties from a debug device or simulator and displays the data in console, which is temporary (retained for only the last hour).This allows you to validate event tracking, check parameter accuracy, and troubleshoot issues early on.
Device ID
Device id is a unique ID assigned to each device based on the UUID whenever a new device is registered in Apptics for any application.
Devices count
The total number of devices registered in Apptics for a particular application. Devices here means any smart device such as smartphones, iPads, smartwatches, smartTV.
Downloads
The total number of devices in which the application was downloaded, opened for the first time, and registered with Apptics.
dSYM files
dSYMs are debug files created when you build an app using Xcode. They hold information that connects the app's code to the crash report. When an app crashes, the report only shows memory addresses, which don't make much sense on their own. dSYM files help turn those confusing addresses into clear details like the exact file and line where the crash happened. This process is called de-symbolication, and it's key for figuring out and fixing crashes.
Events
Events helps you understand how users interact with your app by capturing specific actions like button clicks, swipes, form submissions, video plays, or even closing a popup. These user activities are called events.
You can track two types of events in Apptics : defined events, which are automatically tracked basic app lifecycle actions, and custom events, which you configure manually through the SDK. You can also manage your events, edit, delete, or retrieve both defined and custom events, and if needed, you can also export your data in the console.
Flows
Flows are the visual representation of how a user is navigating within the app,such as —what screen they open first, what actions they take next, and where they drop off. Flows provides multiple combinations such as screen‑to‑screen,event‑to‑event and event + screen transitions including optional backflows for a chosen time period.
Users can switch between screen‑only, event‑only, or combined views; apply filters for flow count, app version, device type, and country; and view data that is updated daily to reflect the previous day’s activity.
Funnels
Funnels help you visually track how users move through a series of steps or actions within your app, such as onboarding, browsing, adding to cart, and completing a purchase. It displays how many users enter each step, how many move to the next, and where they drop off along the way.
This helps you identify where users lose interest or face friction, so you can improve those steps to increase conversions. Funnels are essential for understanding user behavior and optimizing the app experience to meet business goals.
Geography
Geography lets you filter user data by country based on metrics like new devices, active devices, user IDs, and app versions, helping you understand where your users are and how they interact with your app across different regions.
In-app feedback
In-app feedback allows your users to share feedback, report bugs, or request help from within the app. This makes it easier for users to communicate issues or suggestions in real time. Developers can use either show the pop-up or the app users can simply shake their device to open the feedback form.
While sharing the feedback, users can do a screen recording, take screenshots, annotate the screenshots, and mask any personal information. They can also attach log files with their feedback—up to 5 files, each with a maximum size of 2 MB.
In-app ratings
In-app ratings allows you to collect user reviews directly from within your app using a native 'Rate Us' popup. You can configure dynamic criteria to trigger these popups at the right moment based on user activity such as screen views, events, or session duration, ensuring that only engaged users are prompted.
You can configure the rating pop-up either on: score-based, where each action carries a weight and a goal score must be met to trigger the popup, or hit-based, where specific actions must be performed a certain number of times. You can also define anchor points specific actions that, once triggered, show the popup instantly regardless of other conditions. You can edit, enable, or disable each configuration in Apptics console as per the app version.
In-app Updates
In-app updates let you notify users about new app versions through pop-ups displayed within the app. Supported across Android, iOS, and apps hosted via custom URLs (like MDMs)or third party apps. Apptics offers three alert templates: Android in-app alerts (for Android 5.0+), Apptics native alerts (with platform-specific UI), and Apptics custom alerts (fully customizable via SDK APIs).
Alert types include Flexible, Immediate, Force update, Ignorable, Remind me later, and Non-supported OS, depending on update urgency.
JavaScript (JS) errors
JavaScript (JS) Errors are errors that happen when something goes wrong in the code of a web application, such as missing variables, broken functions, or failed requests. These errors can be caught, uncaught, or appear as warnings in the browser console.
The JS errors module shows a complete list of these issues for your web apps. It includes helpful details like error messages, stack traces, device timeline, and information about the app version, operating system, and affected devices.
New Device
New devices refers to a device that is registered with Apptics for the first time. In Apptics, new devices are identified using a unique device ID. If the same device accesses the app again, it will no longer be considered a new device. This helps track the number of new installations of the app.If a device uninstalls the app and later reinstalls it or if it's reset to factory settings, it is counted as a new device again.
Non-fatal exceptions
Exceptions that are safely handled and sent to Apptics.
Opt-in devices
Devices where users have consented to share their data, allowing Apptics to collect data with PII.
Opt-out devices
Devices where users have declined to share their data, preventing Apptics from collecting any data.
Package Name
A unique identifier for your Android app.
Parameters
A parameter is a setting in remote configuration that allows you to control specific aspects of your app's behavior or appearance dynamically. It comprises a parameter key, a default value (the baseline setting used when no other conditions apply), and optional conditional values that apply only under certain circumstances, such as the device type, app version, country, or other custom conditions you set.
Performance Monitoring (iOS)
Performance Monitoring in Zoho Apptics helps you track key performance metrics for your iOS app, directly sourced from App Store Connect. After linking your App Store Connect account via the Store Reviews page, you can access performance insights in the Apptics console under Quality > Perf. metrics.
Metrics include battery usage (minutes/day), disk writes (MB/day), hang rate (seconds/hour), launch time (ms), memory usage (MB), scroll hitch rate (ms/second), and background terminations (terminations/day). These metrics—based on anonymized Apple data—reflect your app's stability, responsiveness, and resource usage.
Personal identifiable information (PII)
A unique identifier to recognize the end-user within the application, such as an email ID, mobile number, or a generated user ID.
Platform/OS
The software running on the native device that helps the application communicate with the device. Examples include iOS, Android, and macOS, etc.
Portal
A Portal is an organization-level directory for your organization. It acts as a central hub where all your apps, projects, and users are managed. When you create a portal, you're setting up the environment where your team can collaborate, manage apps, track analytics, and control user access. From inviting team members and assigning roles to registering apps and grouping projects, everything begins at the portal level.
Portal members
Portal members are users who have been added to your Apptics portal and have access to it. These members can be assigned roles and invited to one or more projects within the portal. However, being a portal member doesn't automatically give them access to all projects; they must be added separately to each project they need to work on.
Privacy shield
The Privacy shield is an additional security feature for iOS and iPadOS apps and is designed to protect in-app data from unauthorized screen captures or recordings, ensuring user information remains private,reducing the risk of unintentional data leaks and privacy breaches.
Proguard files
ProGuard is a tool that makes your Android app smaller and protects it by changing the code so others can't easily read or copy it. But because of this, crash reports can become hard to understand since the code names are changed.So Zoho Apptics uses deobfuscation method to convert these reports back into a readable format using a mapping.txt file generated after building your app (found in build/outputs/mapping/).
Proguard mapping file
Files used to deobfuscate the crash stack trace to a human readable format for Android.
Project
A project is a container for all your apps. It contains the application ids, bundle ids, or package names. For example, Zoho Apptics is a project that will contain the Android package name, Apple bundle ID, Windows application ids, and your browser app ids.
Project members
A list of users added to your project in Apptics. The project members can perform actions within the project based on assigned roles. You can add project members only if they are part of your portal.
Push notifications
Push Notifications are messages sent directly to users' devices to keep them engaged to the app. These messages can include text, images, videos, or interactive elements to engage users. They help increase user engagement, retention, and conversion by keeping users informed and encouraging them to take action.
To use push notifications in your app, you need to set up the necessary credentials and certificate for Android (via Firebase) and iOS (via Apple).
Remote configuration
Remote configuration allows you to make changes to your app's behavior and appearance without the need to release a new update. It enables you to toggle features, launch new updates for specific users, or show/hide elements based on user segments.
Remote configuration uses a combination of parameters (default key-value pairs) that control the app's look and behavior, along with conditions you set to adjust these parameters based on certain criteria.
Remote logger
Remote logger allows developers to track how the app is performing remotely, even if the user is offline. This tool gives developers a clear view of how the app is working on different devices, which helps them fix problems faster and improve the app's overall performance without needing the user to be actively using the app.
Retention
Retention tells you how many users return to your app after using it for the first time. For example, Day 0 retention shows how many users came back the next day, while Day 7 shows those who returned a week later. You can track retention over different durations, allowing you to monitor user engagement. Understanding retention helps you evaluate user loyalty and make data-driven decisions to improve user experience and app growth.
Role-based access control
Role-based access control is a measure in place to make sure that access within Apptics is restricted to authorized users based on their roles within an organization. This ensures that project members have access only to the information and functionalities necessary
Screens
Screens refer to the individual pages or views that users interact with within your product. Tracking screens helps understand user flow—how users move from one screen to another, which parts of the app are most viewed, and where users tend to drop off.
Segments
Segments are groups of users in your app that share similar characteristics or behaviors. These characteristics could be things like platforms, versions, and countries, etc. In Apptics, by creating segments, you can target specific groups of users with personalized content, messages, or features. Segments help you better understand and engage with different types of users based on their unique behaviors or attributes.
Sessions
A session in Zoho Apptics represents the time a user actively spends using your app, starting when the app is opened in the foreground and ending when it's closed or pushed to the background. Sessions are automatically tracked by the Apptics analytics SDK along with crashes and selected screen views.
The minimum session duration is 3 seconds, which defines the shortest time a session must last to be considered valid, while the maximum session timeout is 30 minutes, which sets how long the app can stay idle before ending the session. These thresholds apply to both mobile and web apps, helping ensure accurate tracking and measurement.
Signed-in devices (Total users)
The total number of signed-in devices by users with their consent to share their data over a selected period. If the user has two devices, then it is considered as 1 (given that they have registered on the same day).
Store reviews
Store reviews are public reviews and ratings given by users on app stores like Google Play and the Apple App Store. You can manage and analyze these reviews in a single dashboard by linking your App Store Connect and Google Play Console accounts. You can fetch complete review history, including app version data and rating breakdowns.
All the reviews are ran through our ML engine and provides sentiment analysis to classify reviews as positive, neutral, or negative. You can respond to reviews directly from the console—either manually or with AI-generated replies.
Unique active devices
Unique active devices refers to the number of different devices that used your app during a specific time. Each device is counted only once, no matter how many times the app is opened or how long it's used. If a user opens the app multiple times on the same device, it still counts as one unique device. But if they use it on different devices, each is counted separately. You get the unique active devices for upto 30days in Apptics.
User Consent
User consent enables app developers to obtain and manage user consent for data collection, helping to comply with various global data privacy regulations and giving users control over their data-sharing preferences.
User Email Notifications
The app developers/marketers can subscribe to notifications based on their preferences and roles in the project. They can anytime enable/disable notifications from the Apptics console. Notifications are mostly for Stats such as daily stats, weekly stats, summary, and different features in Apptics.
User group
A user group is a collection of users who share similar characteristics or behaviors. For example, you could create a group of users who have made a purchase or users who have been active in the app for a certain period.
User identity (PII)
A unique ID to identify the end-user within the application.
Example: email id, mobile number, generated User Id.