Permission: Campaign entities
In order to comply with certain regional regulations, many organizations offer a button on their GDPR first layer message or privacy manager that enables end-users to reject all purposes whose legal basis is user consent while allowing purposes whose legal basis is legitimate interest.
At Sourcepoint, this specific configuration is called continuing without agreeing. In this article, we will cover how to implement the continuing without agreeing setup in your GDPR TCF and GDPR Standard messages.
- Add continue without agreeing button to message
- Test continue without agreeing end-user consent flow
Add continue without agreeing button to message
Navigate to an existing GDPR TCF or GDPR Standard first layer message or privacy manager builder and click + in the toolbar pane.
Select the Button component from the subsequent modal to add a new button.
Select the newly added button and use the Settings panel to style the button as needed.
With the button selected, expand the Action accordion and select Accept Legitimate Interest Only from the provided dropdown menu.
Note: Select the following links to learn more about button actions for first layer messages and privacy managers.
The Accept Legitimate Interest Only action assigned to your button will, when selected by an end-user, reject all purposes whose legal basis is user consent while allowing purposes whose legal basis is legitimate interest.
Save your first layer message or privacy manager and (re)launch your GDPR TCF or GDPR Standard campaign.
Test continue without agreeing end-user consent flow
Test the end-user consent flow by navigating to your property and selecting your continue without agreeing button in your message when it is displayed.
Open the browser console and retrieve the end-user's consentUUID
.
Navigate to Sourcepoint's API end-point to retrieve an end-user's consent status for either GDPR TCF or GDPR Standard and input the property's siteId
and consentUUID
in the provided fields. Click Try It to run the request.
GDPR TCF: GET end-user consent status
GDPR Standard: GET end-user consent status
Review the response. Vendors who have legitimate interest configured for at least one purpose will populate in the legIntVendors
array and purposes who have legitimate interest configured as legal basis will appear in the legIntCategories
array.
Note: Additionally, confirm that the vendors
and categories
arrays are empty. These arrays detail the vendors and purposes have been consented to by the end-user, respectively.
[
{
"dateCreated": "2024-01-29T11:18:40.277Z",
"consentUUID": "123456-a960-4fce-b7ee-c3e1a3fa4a1a",
"messageId": 1234567,
"vendorListId": "1234561fa2286382161cc6aa",
"vendors": [],
"legIntVendors": [
{
"_id": "123456beb8e05c306f2a1ed6",
"name": "Vendor 1",
"vendorType": "CUSTOM"
},
{
"_id": "12345fbeb8e05c30686fd713",
"name": "Vendor 2",
"vendorType": "CUSTOM",
"googleId": 0000
},
{
"_id": "12345da6b8e05c306c0597d7",
"name": "Vendor 3",
"vendorType": "IAB"
}
],
"categories": [],
"legIntCategories": [
{
"_id": "12345cdf4f3f9789140e23a0",
"name": "Custom Purpose"
}
]
}
]
Comments
0 comments