Consent
Consent signals in mobile SDKs
Shipping a consent banner is not the same as gating analytics. We still meet teams whose CMP looks polished while SDKs buffer events offline and flush them after a revoke. Data Governance for App Analytics has to include the wire between policy UI and collectors.
Map the states you actually have
List every state your CMP can emit: grant, deny, revoke, region unknown, and “pending.” Then list what each analytics SDK does in those states on iOS, Android, and web. Gaps usually appear in pending and revoke. Pending often defaults to “collect anyway,” which is convenient for growth charts and painful for privacy reviews.
Test revoke like an incident
In staging, grant analytics, generate identifiable events, revoke, and watch network traffic for two minutes. Confirm queued events are dropped or stripped according to your policy. Measure latency from revoke tap to last outbound analytics call. If the answer is “next cold start,” document that limitation or fix the listener.
Keep product experiments honest
Feature flags that depend on behavioral events must degrade when analytics consent is denied. Otherwise you create a shadow incentive to keep collecting. Pair experiment owners with the SDK steward so denied cohorts still receive safe defaults.
The SDK Consent Wiring Lab walks through these drills with sample apps. Start from the courses list if your collectors still outrun your banners.