In a nutshell
Zoho Creator enables you to download your web application as a fully
rebranded mobile app for both
iOS and
Android devices. This feature helps morph the functionality of Zoho Creator into an app representing the admin's organization and can be created in two different variants for the employees (
users) and
customers, respectively. Using the mobile app metrics dashboard
powered by Zoho Apptics (a mobile application analytics tool), super admins and admins can monitor and analyze the usage of these rebranded mobile apps, track app performance and measure user engagement.
For Creator web apps, the
Metrics feature can be used to get the usage statistics.
Availability
Metrics for rebranded mobile apps is available:
- As a part of the rebranded mobile apps add-on for Portals or on the Enterprise plan (which contains rebranded mobile apps by default)
- Only in the Creator 6 version of Zoho Creator.
- Only super admins can enable this feature in the System Integrations page. Once enabled, both super admins and admins can enable app metrics during code signing and view the collected metrics data.
1. Overview
Zoho Creator lets you build and launch full-fledged web applications quickly, which can also be utilized as mobile apps. However, an app is truly complete only when its performance across devices and platforms can be effectively measured. Zoho Apptics is a Mobile Application Analytics tool that helps businesses measure key in-app metrics and understand how their app is performing, analyze usage trends, and optimize app health.
The Zoho Apptics integration with your Creator application enables you to seamlessly monitor rebranded mobile app usage metrics with the help of key performance indicators (KPIs), collect and analyze user behavior, track engagement patterns, analyze screens and drop-off rates, and much more via an intuitive dashboard, without the need for any third-party setups.
During the code signing process, Apptics can be bundled with the rebranded Creator mobile app. Once the code signed process is completed, Apptics will start tracking usage and you can view the usage data in the Mobile Metrics dashboard.
1.1 Benefits of metrics for app stakeholders
This integration captures application performance monitoring features that are useful for admins who want to understand how their rebranded mobile applications are being consumed by the end users. Based on these real-time analytics, they can then make informed decisions on how to improve their app, thereby reducing development cycles and ensuring their app evolves to meet their users' needs.
It also allows:
- App owners with a complete picture in a single dashboard.
- App developers to keep a check on usage statistics of their app and improve its performance.
- App marketers to understand adoption and engagement within the app along with drop-off at every step.
This enables you to deliver tailored, high-quality rebranded apps faster while maintaining a strong focus on user satisfaction and business goals.
1.2 How is the data collected to measure KPIs?
- Please note that the data collected is shared only with Zoho Apptics; third parties will not be able to access this data.
- Data collected is retained and available in Apptics for a maximum of five years . The collected data will however be deleted when the admin/super admin:
- Deletes the Creator application
- Deletes their Creator account
- Explicitly asks Creator to delete the data
- The collected data will also be deleted when when a user explicitly asks Creator to delete the data
- When a mobile app is deleted, new data collection will stop for that app, and you will not be able to view its metrics.
Input: The data collected to track the KPIs include devices in which the rebranded app has been downloaded and under use, active sessions, and app screens that your users see and interact with. Apart from these KPIs, goals can be configured by the super admin or admin to track a user’s journey toward completing a set of pre-defined steps.
Output (KPIs): This includes a set of metrics, charts, and graphs that can be viewed in the Mobile tab by clicking the View Metrics button beside the required rebranded mobile application. These metrics help you understand how your end users are consuming your mobile applications.
1.3 Privacy consent screen
Your users will get a consent screen on their mobile app for the first time after the Apptics integration with Creator has been enabled. They can choose to either give consent (anonymously) or deny consent to be tracked by Apptics. The super admin or admin is also informed about the usage of this feature while enabling this integration .
1.4 Terminologies used for KPIs
To track the success and usage of your mobile app, the categories we have include:
- App engagement metrics: Goal analysis, screens analysis, and sessions analysis
- App adoption metrics: New devices and active devices
Below are the various terminologies used and are application-specific.
Term | Definition | Examples | Snapshot |
Device count | Total number of unique devices on which your app has been installed or has reported activity(users accessed a screen, entered a funnel, and so on) within a specific time period. | - If one user installs your app on two phones, then the device count = 2.
- If one device has multiple user logins, then the device count = 1.
|
|
Screen Analysis | Enables you to understand how much time users spend on each screen of your app and which screens users engage better with. It displays five screens in random order in the dashboard.
| Users might spend a lot of time on the "Search Results" page screen, but few proceed to the "Product Details" screen in a Product Management mobile app. For example, the total no: of visits to the "Search Results" page is 28 and the average duration spent is 2 mins 21 secs. However, the total no: of visits to the "Product Details" screen is 19 and the average duration spent is 15 secs.
|
|
Goal Analysis | Helps you understand how users navigate and interact with your app by mapping the user journey, highlighting conversion points, and identifying stages where users may drop off. | You can create a video streaming app and analyze the user journey from app launch to subscription. This includes analyzing how users discover content, how much time they spend browsing or watching previews, where drop-offs occur, and which interactions most often lead to a subscription. These insights help you identify friction points, optimize onboarding flows, and refine subscription prompts to improve conversion rates. |
|
Goals | These consist of a sequence of steps that together represent a user action or outcome. By defining a goal with multiple steps, you can track how users progress through each stage, identify where they drop off, and understand which paths lead to successful completion. Goals must include at least two steps and can have up to ten steps. | In a food delivery app named, a funnel goal might include the following steps:
- Open app
- Browse menu
- Add items to cart
- Proceed to checkout
- Complete payment
|
|
Conversion Funnel | A visual funnel that shows the steps users take to complete a goal in your app. It shows how users move through each step, helping you identify drop-offs and improve completion rates. |
|
|
Steps | A bunch of steps together make a goal. You can name your steps and select the screen that you want to associate with each step. | A goal titled "Membership registration" in a Fitness Management mobile app can consist of the following steps.
Step 1 -> Open the mobile app
Step 2 -> Browse workout programs
Step 3-> Select a plan
Step 4-> Sign up for a membership (goal)
Step 5-> Complete payment
|
|
Conversion Rate | It denotes the total number of users who completed a specific goal till the last step. | If 28 users had had started from step 1 and only 10 completed all the five steps mentioned above, then the conversion rate in this case would be 23%.
|
|
Drop-off Rate | It is the total percentage of users who dropped off from the previous steps in a specific goal, instead of continuing from the previous step before completing a desired action | Users might drop off at the Checkout stage in a food delivery app which may indicate issues with payment options, pricing concerns, or a complicated checkout process. |
|
2. Prerequisites
- Enable Zoho Apptics in the System Integrations page.
- Enable App Metrics for the required mobile application during code sign in the Mobile tab. For example, let's assume you have an Order Management app. You code sign this app and enable the app metrics in the Code sign screen to bundle this app with Apptics and start collecting the stats.
If you've not enabled Zoho Apptics in the System Integrations page and try to enable App Metrics during code-signing, a popup will appear asking you to enable it first.
Click View details and tick the checkbox next to I acknowledge and agree to data collection and processing requirements. Then click Enable.
This enables you to track usage, performance, and potential drawbacks, thereby helping you improve the customers' app experience.
3. See how it works
<video>
4. Use cases for mobile metrics
(i) Online food delivery app
Let’s assume that an organization named Zylker uses the Creator mobile application titled "Online Food Orders" to display their menu, accept local customer orders, and manage these orders online. Initially, the business runs smoothly, but over the past week, the admin in Zylker notices that nearly 80% of app visitors are not placing any orders.To narrow down the root cause of this sudden drop, the admin enables mobile metrics and monitors the app's usage metrics using the Mobile metrics dashboard. They decide to set up a goal analysis based on customer events or screens visited.
Info: This analysis provides data on the number of users visiting specific screens.
The insights reveal that while over 90% of visitors reach the checkout screen, only 20% complete their purchases. This indicates a potential issue with the checkout process. Upon further investigation, the admin discovers that the most popular payment option is either greyed out or unavailable. After resolving this issue immediately, the checkout conversions improve significantly, restoring the app’s performance.
(ii) Financial learning app
Let’s assume that an organization, Zylker launches a financial literacy app titled "Finance for First-timers", designed for kids and young adults to teach them the basics of money management and kickstart their personal finance journey through live learning and engaging sessions. To figure out how well the app is being put to use, the admin wants to know insights like how much time students spend on the app daily and how engaging they find it.
To address this, the admin uses the sessions analysis feature in the Mobile metrics dashboard, which provides detailed metrics like total count of sessions, total duration of all sessions combined, and average duration per session. This data reveals that most users engage with the app for shorter intervals but more frequently. To encourage longer sessions, they introduce a messaging feature that allows students to interact and network within the app, boosting engagement and connection among users.
Likewise, to understand which screens or modules of their app are most visited, they use the screens analysis report in the dashboard. This provides insights like the exact screens students visited, time spent on each screen, and total visit counts. The data reveals that the Timetable screen is the most visited. Previously, students had to navigate to the dashboard and scroll to find it. To improve accessibility, the admin makes the Timetable a separate menu item on the sidebar, thereby making it easier for students to access.
5. Navigation guide for enabling Apptics integration
In the
Operations tab of your account, choose
System Integrations and enable
Zoho Apptics integration. When
code signing your mobile application, you can enable the <feature_name>.
<video>
6. Points to note
- To enable Apptics integration for rebranded apps in your Creator account, you must enable it for each rebranded mobile individually during its code sign process.
- For the same mobile app (let's say Order Management), you can opt to track metrics exclusively for Android while excluding iOS. To achieve this, you must enable app metrics during the Android code signing process but leave them disabled during the iOS code signing process for this app.
- Once enabled, you can't disable the Apptics integration currently. You can only deactivate (pause) the tracking
- When you create and restore a backup for an application, the mobile metrics data will not be included in the backup. The backed-up application will not contain any code-signed apps.
- When an account is migrated from one datacentre (DC) to the other, the existing Metrics data of that account will not be migrated to the new DC. After migration, ensure to complete the prerequisites. Your Metrics dashboard will then be populated with the statistics specific to the new DC.
- When users open your mobile app from their device, a consent form will appear, allowing them to choose from the below two options:
- Give consent to being tracked anonymously
- Deny consent to being tracked. In this case, data will not be collected and any actions the user performs will not be tracked.
- Mobile metrics are majorly measured in terms of devices by Zoho Apptics. If a mobile app is downloaded and opened on a device, then that count is registered as a "new device" by Apptics.
- Both users' and portal users' code signed apps will be considered as separate apps in Apptics, and their metrics will be captured individually.
- Understanding devices and sessions
- Understand screen analysis
- Understand goal analysis
- Work with mobile Apptics