Tracking Settings

Apptics has six tracking states as mentioned below.

  • AppticsTrackingState.USAGE_AND_CRASH_TRACKING_WITH_PII
  • AppticsTrackingState.USAGE_AND_CRASH_TRACKING_WITHOUT_PII
  • AppticsTrackingState.ONLY_USAGE_TRACKING_WITH_PII
  • AppticsTrackingState.ONLY_USAGE_TRACKING_WITHOUT_PII
  • AppticsTrackingState.ONLY_CRASH_TRACKING_WITH_PII
  • AppticsTrackingState.ONLY_CRASH_TRACKING_WITHOUT_PII
  • AppticsTrackingState.NO_TRACKING

Usage Tracking

Events, APIs, screens, sessions, and the events and impressions from modules like In-app Ratings, In-app Updates, and Remote Configuration are a part of usage tracking.

Crash Tracking:

Crashes and non-fatal exceptions are part of crash tracking.

When the app is installed, the tracking state will be USAGE_AND_CRASH_TRACKING_WITHOUT_PII, i.e., all data will be tracked without the user id, even if the addUser method is called (by default).

If you want to stop the tracking completely (NO_TRACKING) when the app is opened for the first time after installation, use the defaultTrackingState field in Apptics Gradle extension.

Copiedapptics {
    defaultTrackingState = ["default" : com.zoho.appticsplugin.DefaultTrackingState.DISABLED]
}

To manually set the tracking state in app runtime, use the below method with the required state enum as mentioned above.

CopiedAppticsAnalytics.setTrackingStatus(state: AppticsTrackingState)