Notes on SDKs for CMP
The CMP abstraction layer will tell the Consent Management Platform (CMP) to show itself on every app start, if needed. Once the CMP gives us the information that it showed the UI and was dismissed by the user, or it did not need to show the UI or there was an error showing the UI, etc., we continue with the app start. If the CMP does not give us a response of its outcome, the app will be stuck in the app start forever as we Don't know its result.
Our apps generally have some offline functionality. While the very first app start requires an active internet connection, the following app starts do not. End users can see a cached version of what they saw in a previous instance of the app.
If the app is started offline, the Consent Management Platform (CMP) must handle such a case and provide us its state accordingly. Some native analytics frameworks store events locally until the device becomes online again, so for those cases we need to have a consent state for given vendors.
Any CMP SDK we integrate must handle apple's app tracking transparency framework (ATT). For different approaches in handling we currntly follow the following strategies
- We've had cases where the Apple review rejected apps if we showed the CMP before the ATT popup and if we showed the CMP after the ATT popup, where the user declined tracking. So now we do not show any CMP and assume no consent is given for ALL vendors, if the enduser declines the ATT popup.
- If the CMP shows a different state depending on the user's selection for the ATT, e.g. only legitimate interests instead of all vendors - basically a fallback UI with reduced options - we show that and handle the consent state of the vendors from the CMP accordingly.
The following CMP Vendors are currently fully integrated: SourcePoint, ConsentManager, Usercentrics