- 1 Minute to read
- Print
- DarkLight
Tracking
- 1 Minute to read
- Print
- DarkLight
The Tracking section of the Android SDK documentation covers all aspects of implementing tracking within your app, from automatic tracking to more advanced manual configurations. Whether you’re tracking user interactions, managing sessions, or configuring specific tracking settings, this section provides detailed instructions and use cases to help you tailor the SDK to your app’s needs.
Key Areas Covered in This Section
The SDK automatically tracks activities and fragments upon initialization, without requiring additional setup. This feature simplifies tracking for most use cases, as the SDK dynamically updates tracking configurations when new activities are added.
For more control, manual tracking allows you to explicitly configure which activities and fragments should be tracked. You can implement either Object-Oriented Tracking or Query Parameter Tracking, depending on your needs.
Learn how to manage user sessions and retrieve important session-related data:
Retrieving the User Ever ID: Access the unique identifier assigned to users.
Android Singleton Reset: Reset user data and the SDK’s state, typically used for debugging or testing purposes.
Get Current Global Configuration: Retrieve the current tracking configuration settings.
This section covers tracking various types of user interactions and app-specific behaviors:
Device Recognition vs. Email / Manual Login: Track how users log in, whether via device recognition or manual credentials.
Push/In-App Notification: Track interactions with push notifications and in-app messages.
Mapp Engage SDK & App Manifest: Set up the Engage SDK and track notifications.
Deep Linking: Track user entry points through deep links.
WebViews: Monitor interactions within embedded WebViews in your app.
Native Functionality Requests: Track user interactions with native app features, such as accessing the camera.
Configure advanced tracking options to customize your app’s tracking behavior:
Crash Tracking: Track app crashes to improve error handling and debugging.
Opt-out of Tracking: Allow users to opt-out of tracking, in compliance with privacy policies.
Change TrackID and Track Domain on Runtime: Dynamically update track IDs and domains during the app’s runtime.
Force Data Send and Clear Cache: Immediately send cached tracking data and clear requests, useful for debugging.
Review the default parameters that the SDK automatically includes with each tracking request, ensuring that comprehensive data is captured with minimal effort.