Consent Management for Purple App & Web
Since the introduction of the General Data Protection Regulation, known as GDPR in 2016, it’s mandatory within the EU to ask your users for permission to track and analyse their user data.
The consent management mechanism for Purple provides a modal screen while the initial app starts. The Consent Screen shows the option, which you have configured with the consent management provider before.
This is an example modal consent-screen of a configuration with 'Sourcepoint' in a Purple app:
In this example the primary buttons are 'Reject All' and 'Accept All' and additionally there is a 'Show Options' link.
The tracking/analytics service in your app will not load if the user has either not yet given consent or has not given consent for that particular service.
Often there are two layers used, the first one is like the one on the screenshot above and the second one displays the detailed configuration of all services. This screen can also be made accessible for the user via the app menu, so that she/he has the option to change the settings anytime. For you to open the screen, in the Purple Experience or another Html in the app, it can be shown via JS API or action URL: purple://app/consent/privacy_manager/open
Find an Example of this 2nd screen, made with a 'Consentmanager' configuration, below:
In Purple Manager, you can access the Consent Management Settings in
'Apps' → Three dot menu → 'Consent/Push/Analytics' -> 'General'
We currently provide options to
- connect with the Consent Management platform in order to obtain the consent of your users with Purple, either with 'Sourcepoint', 'Consentmanager', 'Usercentrics' or 'Traffective''.
- Choose the option 'none' which comes with a basic opt-out: If you don’t select a consent management platform for your app, the user has a toggle in the settings, to completely opt out for tracking.
When selecting 'none' (basic opt-out), please make sure first, that you don’t need to comply with GDPR, e.g. because your app will be only available outside the E.U.
For Configuration of the Consent Management Platform Sourcepoint, go to your Sourcepoint account on the Service Provider's website, copy the following properties and paste them into the fields:
- Sourcepoint Account-ID
- Sourcepoint Property-ID
- Sourcepoint Property-Name
- Sourcepoint Privacy Manager-ID
For Configuration of the Consent Management Platform Consentmanager, go to your Consentmanager account on the Service Provider's website, copy the following properties and paste them into the Purple Manager fields:
- Consent Manager Code-ID
- Consent Manager Server Domain
The Traffective CMP is an app only integration. This means that it only works for your app(s) not for your website(s). For Configuration of the Consent Management Platform Usercentrics, go to your Usercentrics account on the Service Provider's website and copy the Usercentrics Settings-ID into the entry field in Purple Manager.
The Traffective CMP is a Web only integration. This means that it only works for your website(s) not for the app. To configure it, go to 'Apps' → Three dot menu → 'Consent/Push/Analytics' -> 'Web', copy the following IDs from your account on the Service Provider's website and paste the IDs into the entry fields in Purple Manager.
For those tracking analytics services, which you have enabled in Purple Manager (e.g. Firebase) for your app, you will now configure this service (e.g. Firebase) as a vendor.
To Do so,
- Go to your Consent Management platform (e.g. Sourcepoint or Consentmanager)
- Configure your desired tracking analytics service as a vendor (e.g. Firebase)
- Copy the created Vendor ID
- Paste it into the field of the corresponding service in Purple Manager (e.g. into the field '13. Vendor-ID for Google Firebase').
- Enter the vendor ID for every tracking analytics service which you have enabled for your app in Purple Manager
- Save your changes
- Rebuild the app, test it and resubmit it to the app stores
It can be possible, that some Tracking SDKs are only activated from the second app start, since the consent can be only given during the first app start by the user. Considering this, it can be necessary to restart the app a second time, to take a change (adding/deleting/reconfiguring) in the tracking analytics services into account.