Consent Management for Purple Apps
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.
How Consent Management works in Purple Apps
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.
First consent screen
This is an example modal consent-screen of a configuration with 'Source Point' 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.
Second consent screen
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 'Consent Manager' configuration, below:
Configuring Consent Management
Access the Consent Management Settings in Purple Manager
In Purple Manager, you can access the Consent Management Settings in
'Apps' → Three dot menu → 'Consent/Push/Analytics'
Choose your Consent Provider
We currently provide the options to
- connect with the Consent Management platform in order to obtain the consent of your users with Purple, either with 'Source Point', or with 'Consent Manager'.
- Choose the option 'none' which comes 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 available outside the E.U.
Configuration of the Source Point SDK
For Configuration of the Consent Management Platform Source Point, go to your Source Point account on the Service Provider's website, copy the following properties and paste them into the fields:
- Source Point Account-ID
- Source Point Property-ID
- Source Point Property-Name
- Source Point Privacy Manager-ID
Configuration of the Consent Manager SDK
For Configuration of the Consent Management Platform Consent Manager, go to your Consent Manager account on the Service Provider's website, copy the following properties and paste them into the fields:
- Consent Manager Code-ID
- Consent Manager Server Domain
Configuration of the tracking analytics Vendor-IDs
For those tracking analytics service, 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. Source Point or Consent Manager)
- 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.