Getting Started

1. App developers to keep a check on the health and performance of the app.
   
2. App marketers to understand adoption and engagement within the app along with drop-off at every step.
   
3. App owners with a complete picture in a single dashboard.
   

Features

1. Quality: Crash reporting, in-app feedback and bug reporting, store reviews, performance metrics (iOS), and remote logger.
   
2. Growth: In-app updates, in-app ratings, and remote configuration.
   
3. Engagement: Flows, funnels, sessions, screens, events, and APIs.
   
4. Audience (adoption): New devices, active devices, retention, geography, and app version.
   
5. Channels: Push notifications.

Architecture

Apptics' architecture is based on a combination of how data flows from the user's device to Apptics console.

Supported SDKs

1. Android
   
2. iOS
   
3. iPadOS
   
4. macOS
   
5. tvOS
   
6. watchOS
   
7. React Native
   
8. Flutter
   
9. Unity (Vision OS)
   
10. Windows
    
11. JavaScript
    
12. Linux
    

Steps to get started with Apptics

Setup your Apptics account

1. Visit www.zoho.com/apptics/ on your web browser.
2. Fill in the necessary details to sign up, accept the Terms of Service and Privacy policy, and click on Get Started
   

1. If you already have an account, click Sign in.
   

1. Once you sign in, you will be redirected to the manage portal page. Click on Create new portal.
   
2. Add the details such as the portal name, phone number, the platform in which your app runs on, application ID, and production environment.
   
3. When you create a portal in Zoho Apptics and if you agree for Zoho Apptics to collect app data from your users, you are given a choice as to whether you will be willing to ask your app users for consent for data collection or not.
   

If you decide to use the user consent module, the user will be asked to review their privacy preferences in the app's settings upon their first interaction with your app. A sample screenshot from an Apple iPhone is shown below.

1. If the user selects Include my identity and all the other options are enabled, data is collected from the user's device will be associated with the user identity.
2. If the user disables Include my identity and all the other options are enabled, data is collected from the user's device but will remain anonymous in Apptics. A randomly generated identifier will be associated to the data.
3. If the user disables all the options, no data tracking will happen.

Create a project and add your app

1. Click Create a project.
2. Enter the project details. Provide the project name.
   
3. Select the platform in which your app runs on, i.e., iOS, tvOS, macOS, watchOS, visionOS, Android, Windows, Web, or Linux.
   
4. Add the application ID. You need to provide the bundle ID for Apple (iOS/iPadOS/macOS/tvOS/watchOS/visionOS) apps, package name for Android apps, and domain URL for web apps.
   
5. Select the environment, i.e., to choose whether the data should be tagged under the development or production environment.
   

1. Once you have provided the necessary details, click Next. The project will be created and the app will be registered under the project.
2. Once you register your app, you can complete the integration steps as given in the UI to start receiving app data in the console. 
   

You can complete the integration right-away or skip for now and later complete it from the Quickstart page in the console. Learn how to create a project and add an app from here.

Note: The user who creates the portal is the Super admin of the portal and will have all the privileges. There can be only one Super admin for each portal. There can be an `N` number of admins for a portal. An admin will also have all the privileges in the portal however the admin cannot update or delete an existing portal.

Analyze data in Apptics dashboard

The dashboard in the Apptics console gives you an overview about your app's key metrics such as crashes, sessions, new devices, active devices, top events, and top screens for the selected date range.

Invite users to the portal

Note: You can invite multiple users by separating the email addresses by a comma.

• Click on the profile picture in the upper right corner.
• Navigate to Portal Members and click Invite User.

1. Add the email addresses of the user(s) you want to invite to the portal.
2. Select the type of user, i.e. user or admin.
   
3. Select the project to which the user will have access and the role of the user. (This is optional)

• Click Invite and an invitation mail will be sent to the users. The users will have to accept the mail invite, to be able to access Apptics.

Add portal members to the project

1. Go to Settings > Project members.
2. Click on the + icon under the specific roles.
   
3. A pop-up will appear with all the portal members. Select the portal member and click Done. 
   The user will be added to your project. 

Note: Only the portal members will be listed in the pop-up. If the user you are trying to add is not available in the list, contact your portal admin to add them to the portal. You can find the portal admin on the portal members page.

Devices, users, and data

Definitions

1. New devices: The total number of devices in which the app has been downloaded and installed. Whenever the device is reset to factory settings or the app is removed and installed again, the device is registered as a new device in Apptics.
   
2. Active devices (cumulative): The total number of devices in which atleast one active session has happened.
   
3. Active devices (unique): The unique number of devices in which atleast one active session has happened in the past 30 days.
   

For example:
Day 1 - Device A, B, C, D (4 unique devices)
Day 2 - Device A, C, E, F, G (5 devices, 3 unique)
Day 3 - Device A, C, H, I (4 devices, 2 unique)

The total unique active devices for 3 days = 4+3+2 unique devices 

New and active devices in console

If you use the user consent management module for your app, the data collected based on the user consent is shown as opt-in, anonymous, and opt-out devices in the console. For the opt-out devices, only the total count of opt-out devices and the consent state will be maintained in the Apptics server. When a user downloads the app from the marketplace, the device is registered as a `New Device` in Apptics with a device ID and a randomly generated UUID.

Once the SDK is initialized within the app, by default tracking will start anonymously and the data will not be associated with any identifier until you use the setuser() method. You can use any identifier in the setuser() method. Refer to our SDK guide for detailed information:

1. For Android
2. For iOS
3. For Windows
4. For React Native
5. For Flutter

The user ID that you use in the setuser()  method should also be maintained at your end as well. You can later use this user ID to search data in the Apptics console.

WARNING: You should not use any direct personally identifiable information in the setuser() method. If you do have to use a direct PII, make sure that the same is conveyed to your app users.

Generally, the new devices in Apptics can be equated to the number of downloads from the marketplace. However, this data should not be compared with the App Store or Play Store installed count. The reason being, we collect data based on the consent preference from each device and tracking status set by the developer.

Note: When you use Zoho Apptics as your preferred analytics solution, you don't have to implement Apple's tracking transparency (ATT) framework.

Data collection and data sharing preferences

1. Use case A: A user has opt-in today and later changes to:
   Anonymous opt-in - This will be considered a new user. There will be no connection between user A and this new anonymous user.
   Opt-out - The data collection will stop immediately once the state is set to opt-out.
2. Use case B: A user is anonymous opt-in and later changes to:
   Opt-in with identity - This will be considered a new user. There will be no connection between user A and this new user.
   Opt-out - The data collection will stop immediately once the state is set to opt-out.
3. Use case C: A user has opt-out and later changes to:
   Opt-in with identity - Data will be collected with the user's identity once the state is changed to opt-in with identity.
   Anonymous opt-in - Data will be collected but not associated with the user's identity.

Note: User consent module is not mandatory to be used and the above use cases will be applicable only if you choose to use the User consent module from Apptics. If you choose not to use the consent module and yet the in-app data contains any direct personally identifiable information, make sure you convey this to your app's users.