Mobile Apps

Consent SDK Integration for Mobile Apps: iOS and Android

iJurug Soft2026-11-145 min read

Consent SDK integration for mobile apps is mostly a timing problem. Analytics, attribution and ad SDKs tend to initialize the moment your app launches, often before any consent screen appears. A correct integration shows the right prompt, stores the choice, and holds every data-collecting SDK until that choice exists, on both iOS and Android.

On the web, a tag manager sits between your banner and your scripts, so blocking is centralized. Apps have no equivalent layer. Each SDK is linked into the binary, many auto-initialize through content providers or app delegate hooks, and some begin collecting device identifiers before your first screen renders. You cannot patch a shipped build in an afternoon either; a mistake lives on users' phones until they update.

The platforms also add their own layers. Apple's App Tracking Transparency prompt, privacy manifests and the App Store privacy labels, plus Google Play's Data safety section, all have to agree with what your consent flow and SDKs really do. If you are planning a release now, send us your SDK list and we can map the gaps.

Getting initialization order right

Every app needs a written init sequence. The general rule is: read stored consent, show prompts if needed, then start SDKs according to the result.

iOS specifics

Android specifics

Flutter and React Native

Cross-platform apps add one more trap: plugins wrap native SDKs that may initialize natively before Dart or JavaScript code runs. Check each plugin's native setup, not just its package API. Teams using Flutter or React Native should keep the consent gate in a single service that every plugin initializer depends on.

Firebase Analytics supports the same four consent types as Google Consent Mode v2 on the web: analytics storage, ad storage, ad user data and ad personalization.

Set denied defaults at build time

Declare defaults in AndroidManifest.xml meta-data (for example google_analytics_default_allow_ad_storage) and the matching keys in Info.plist on iOS. This keeps the SDK from collecting with consent granted during the moments before your code runs.

Update on every decision

Call setConsent when the user makes or changes a choice, and again on launch from the stored preference. Missing the launch call is a common bug: the user consented weeks ago, but each session starts denied.

Attribution and ad network SDKs

Mobile measurement partners and ad networks each have their own consent APIs or flags. Map each SDK to a consent purpose, document the call it needs, and test it separately; one general "consent granted" broadcast rarely fits all of them.

If you use a CMP that implements the IAB Transparency and Consent Framework (TCF v2.3 is the current version), the TC string and related values are written to standard keys (IABTCF_TCString, IABTCF_gdprApplies and others) in SharedPreferences on Android or NSUserDefaults on iOS, where participating ad SDKs read them directly. Outside TCF, store your own consent record with a policy version, so you can re-prompt when purposes change.

Sync the choice to your backend when the user is signed in. Consent given on a phone should apply to server-side processing, email marketing and the web account too, and a withdrawal in one place should reach the others. India's DPDP framework makes this especially relevant for apps with Indian users, where withdrawal should be as easy as consenting.

A test plan that catches real leaks

  1. Fresh install, deny everything: capture traffic through a proxy such as Charles or mitmproxy and confirm analytics, attribution and ad endpoints stay silent apart from what you have classified as essential.
  2. Fresh install, accept everything: confirm each SDK starts and receives the right consent values.
  3. Change the choice in settings, background the app and relaunch: confirm the new state applies.
  4. Upgrade from the previous app version: confirm stored consent migrates and no SDK starts early.
  5. Compare observed data collection against your App Store privacy label and Play Data safety answers.

Ask candidates how they handle auto-initializing SDKs, how they test with a network proxy, and whether they have shipped ATT and UMP flows through store review. Ask for the init sequence as a diagram you keep. iJurug Soft builds native and cross-platform apps and treats consent as part of the mobile app engineering work: SDK audit, deferred initialization, Firebase and ad network wiring, backend sync and a repeatable test plan. For web properties, the same logic is covered in our guide to consent management platform scope.

Frequently asked questions

ATT governs tracking across other companies' apps and access to the IDFA. It does not replace consent for other purposes required by laws such as GDPR or India's DPDP Act, so most apps need both, coordinated.

Many commercial CMPs offer SDKs for all three with a shared dashboard. It simplifies policy changes, but you still need platform-specific init and testing work.

Will deferring SDKs hurt our crash reporting?

Crash reporting that does not profile users is often classified as essential, but that is a decision for your privacy and legal advisers. Configure it to strip identifiers if you start it before consent.

How often should we re-prompt users?

Re-prompt when purposes, vendors or your notice materially change. Versioning your consent record makes this a simple comparison at launch.

If your next release is close, start with the dependency list: your Podfile or Package.swift, your Gradle dependencies, and the Flutter or React Native plugins you use. That tells us which SDKs initialize early and how much rework the consent gate needs. Share it through the contact form or by email at info@ijurugsoft.com.