Consent management platforms allow a website or mobile application publishers to easily set up an interface for collecting user consent.

You can integrate Batch into any kind of CMP, here is how you can do it:

On mobile, you can disable the SDK by default and start collecting data only after users give consent:

For web push, data collection is triggered with the execution of Batch's JavaScript tag.

You can choose the trigger that will load the JavaScript tag. For example, you can trigger it when consent is provided via the CMP.

Here are more details on triggers for Google Tag Manager and TagCommander.

You also need to call batchSDK('unsubscribe') for users who revoke their consent after having opted in to push notifications. This will insure these users are unsubscribed from push notifications.

Most of the CMPs allow you to customize the purposes for which you collect consent. Here are examples in Didomi's documentation and Usercentrics' documentation.

Your legal team can help you to determine these purposes and how to handle these treatments in your specific case.
​

This guide summarizes all the data processed by Batch, as well as all the actionable features at your disposal to comply with GDPR: GDPR Compliance.