Consent in mobile SDKs

The Android (Kotlin) and iOS (Swift) software development kits (SDKs) now offer consent management capabilities. Developers can specify the user's consent choices, and the SDK will include this information in every event while blocking device mode destinations that the user has not approved. The app continues to feature its own consent user interface, and the SDK itself does not display a banner, save a user's decision, or prompt the user for input.

By default, consent management is inactive. Apps that do not activate this feature function identically to those that did not previously utilize the SDK—events carry no consent indication, and no destination is obstructed. This functionality is available solely through a custom consent provider. Pre-existing consent managers, such as OneTrust, Ketch, and iubenda, remain unsupported.

To incorporate consent data from these tools, developers must extract the user's choices from their respective SDK and transmit them as custom consent category IDs.

Prior versions of the Android and iOS SDKs surveyed a consent filter during startup. Modifications were only effective after the subsequent app launch, and developers had to manage destination access individually within their code. With the Kotlin and Swift SDKs, developers now dictate user consent choices, and each destination's consent settings in the dashboard determine what is permissible.

The setConsent method applies these new choices instantly, even during an ongoing session. The Kotlin SDK includes consent management for Android devices exclusively and is not part of the server-side (JVM) artifact. Consent category IDs are case-sensitive and must match the dashboard entries exactly. Developers can refer to the provided Kotlin, Java, Swift, and Objective-C code samples for guidance on enabling consent management within their mobile applications.