Sourcepoint's withdraw consent customization allows you to configure an experience for end-users whereby they can withdraw consent from purposes that utilize consent as a legal basis while preserving those purposes that utilize legitimate interest as a legal basis with a single button.
The withdraw consent customization detailed in this article is only available for properties utilizing a GDPR TCF or GDPR Standard campaign. In order to create a withdraw consent experience your organization will need to create two different privacy managers with distinct configurations:
Note: This customization is distinct from the Reject All button action in the privacy manager. The Reject All button action allows an end-user to withdraw consent from purposes that utilize consent as a legal basis and reject purposes that utilize legitimate interest as a legal basis.
Configure scenario privacy manager
The scenario privacy manager is displayed to end-users as part of your campaign's scenario conditions. This particular privacy manager requires the following buttons:
| Button Title | Button Action | Purpose |
| Withdraw Consent | Save & Exit | Leverages the default state of an end-user within the GDPR framework (i.e. opted-out of purposes that utilize consent as a legal basis while preserving legitimate interest) |
| Save & Exit | Save & Exit | Captures any specific changes end-user makes to consent preferences (e.g. only providing consent for a single purpose). |
While both buttons in this privacy manager utilize the same button action (Save & Exit), we are relying on the button title and leveraging the default opt-in regime of GDPR to achieve the desired results.
Note: Click here for more information on how to configure your privacy manager.
Once the scenario privacy manager is configured, create a first layer message with a button that will open your scenario privacy manager.
Be sure to connect the first layer message to the scenario(s) that will trigger for end-users visiting your property.
When finished, continue with the configuring the remaining campaign entities and launch your GDPR TCF or GDPR Standard campaign on the property.
Configure resurfaced privacy manager
The resurfaced privacy manager is linked to a button or link on-page and will be displayed to the end-user when they click the button or link. This particular privacy manager requires the following buttons:
| Button Title | Button Action | Purpose |
| Reject All | Reject All | Allows end-user to reject all purposes whether they utilize consent or legitimate interest as a legal basis |
| Save & Exit | Save & Exit | Captures any specific changes end-user makes to consent preferences (e.g. only providing consent for a single purpose). |
Unlike the scenario privacy manager that is surfaced to end-users as part of satisfying scenario conditions, this particular privacy manager is surfaced when an end-user clicks a link or button that has been added to your property.
Note: Click here for detailed information on how to add a link/button on-page to resurface a privacy manager.
<button onclick="window._sp_.gdpr.loadPrivacyManagerModal(123456, 'purposes')">Privacy Manager GDPR</button>
Implement a link or button on your page to resurface this particular privacy manager.
Comments
0 comments