--- title: "Anonymous Tracking" slug: "mapp-intelligence-android-sdk-v5-anonymous-tracking" description: "Enable and understand anonymous tracking in Mapp Intelligence Android SDK v5 for privacy-sensitive tracking scenarios." updated: 2026-04-24T10:43:22Z published: 2026-04-24T10:43:22Z canonical: "docs.mapp.com/mapp-intelligence-android-sdk-v5-anonymous-tracking" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.mapp.com/llms.txt > Use this file to discover all available pages before exploring further. # Anonymous Tracking Anonymous tracking lets the SDK send requests without user recognition in Mapp Intelligence. Use it only when your privacy setup requires it, because it reduces data quality and disables some identity-related features. > [!WARNING] > Important > > Anonymous tracking significantly limits user recognition and session continuity. Enable it only when this behavior is required by your privacy concept. ## What changes when anonymous tracking is enabled - User recognition across sessions is reduced. - Session detection can become less stable. - User matching with Mapp Engage is not available. - Functions such as `getEverId()` and `setEverId(...)` should not be used as part of a user-centric setup while anonymous tracking is active. ## Methods | Method | Description | | --- | --- | | `anonymousTracking(enabled: Boolean, suppressParams: Set<String> = emptySet())` | Enables or disables anonymous tracking and optionally suppresses additional parameters. | | `setTemporarySessionId(sessionId: String)` | Sets a temporary session ID that can be used only when anonymous tracking is enabled. | | `isAnonymousTracking()` | Returns whether anonymous tracking is currently active. | ## Enable anonymous tracking ```kotlin Webtrekk.getInstance().anonymousTracking(    enabled = true,    suppressParams = setOf("cd", "uc703", "uc1") ) Webtrekk.getInstance().setTemporarySessionId("user-xyz-123456789") ``` ## Disable anonymous tracking ```kotlin Webtrekk.getInstance().anonymousTracking(enabled = false) ``` ## Best practices - Prefer configuring anonymous tracking centrally if it should apply to the full app experience. - Use `suppressParams` only for the additional values that must be removed. - If you set a temporary session ID, treat it as session-scoped only. It should not be used as a long-term user identifier. - Do not combine anonymous tracking with user matching. Related pages: [User Matching](https://docs.mapp.com/docs/en/mapp-intelligence-android-sdk-v5-user-matching), [Configure Global Tracking](https://docs.mapp.com/docs/en/configure-global-tracking).