A re-consent refers to the act of collecting consent from an end-user again after that end-user has already provided their consent preferences to your organization. In this article we will cover the technical means by which your organization collects re-consents from its end-users using the Sourcepoint Dialogue platform.
- Consent cookies
- GDPR TCF/Standard scenario conditions
- U.S Multi-State Privacy scenario conditions
- Global Enterprise scenario conditions
- Preferences
Consent cookies
Note: The actions in the table below are applicable to all regulatory frameworks (GDPR, U.S. Multi-State Privacy, etc...)
| Action | Description |
| Consent cookie expiration | Consent/privacy choices are stored within a cookie for reference on future visits. The expiration date on this cookie (configured within your vendor list) has since lapsed for the end-user and they will be treated as a new user for whom your organization will need to collect consent again. |
| End-user clears browser cookies | Consent/privacy choices are stored within a cookie for reference on future visits. The end-user has cleared their cookies since the last time they visited your property and they will be treated as a new user for whom your organization will need to collect consent again. |
GDPR TCF/Standard scenario conditions
In this section we will cover two popular scenario condition settings (vendor list additions and legal basis changes) and how various updates to your vendor list can trigger each condition so that your organization can re-collect consent.
Vendor list additions
The following updates made to your vendor list will trigger the vendor list additions setting for your consent status condition.
| Action | Description |
| Add custom purpose to vendor list | Add a custom purpose to your GDPR vendor list that uses either consent, legitimate interest, or disclosure only for vendors. |
| Add an IAB vendor to vendor list | Add an IAB vendor to your GDPR vendor list. |
| Add Google ATP vendor to vendor list | Add a Google ATP vendor to your GDPR vendor list that uses consent, legitimate interest and/or disclosure only as legal bases for your configured purposes. |
| Add custom vendor to vendor list | Add a custom vendor to your GDPR vendor list that uses consent, legitimate interest and/or disclosure only as legal bases for your configured purposes. |
Legal basis changes
The following updates made to your vendor list will trigger the legal basis changes setting for your consent status condition.
| Action | Description |
| Change legal basis for IAB purpose |
For any vendor on your GDPR vendor list, change the legal basis used for an IAB purpose to consent or legitimate interest. Note: Changing a legal basis for a vendor to not allowed/not applicable for an IAB purpose will not trigger the condition. |
| Change legal basis for custom purpose |
For any vendor on your GDPR vendor list, change the legal basis used for a custom purpose to consent, legitimate interest, or disclosure only. Note: Changing a legal basis for an vendor to not allowed/not applicable for a custom purpose will not trigger the condition. |
U.S Multi-State Privacy (GPP) scenario conditions
In this section we will cover the vendor list additions scenario condition setting for U.S. Multi-State Privacy (GPP) vendor lists and how various updates to your vendor list can trigger the condition so your organization can re-collect consent.
| Action | Description |
| Add new IAB privacy choice | Add a new IAB privacy choice to your U.S. Multi-State Privacy (GPP) vendor list. |
| Add custom privacy choice | Add a opt in and/or opt out custom privacy choice to your U.S. Multi-State Privacy vendor list. |
| Add vendor | Add any vendor to your U.S. Multi-State Privacy vendor list. |
Global Enterprise scenario conditions
In this section we will cover two popular scenario condition settings (vendor list additions and legal basis changes) for your Global Enterprise vendor list and how various updates to your vendor list can trigger each condition so that your organization can re-collect consent.
Vendor list additions
The following updates made to your vendor list will trigger the vendor list additions setting for your consent status condition.
| Action | Description |
| Add new privacy choice | Add a new privacy choice to your Global Enterprise vendor list. |
| Add vendor | Add any vendor to your Global Enterprise vendor list. |
Legal basis changes
The following updates made to your vendor list will trigger the legal basis changes setting for your consent status condition.
| Action | Description |
| Change legal basis for privacy choice |
Change the legal basis used for a privacy choice to opt in or opt out. Note: Changing a legal basis for a privacy choice to not applicable will not trigger the condition. |
Preferences
In this section, we will cover the various actions that will re-trigger a Preferences message when using the Legal Transaction Status scenario condition with a user consent status set to Legal Doc Outdated. The following is applicable to any legal document type selected from the Value dropdown menu.
| Action | Description |
| Publish new version of legal document | Publish a new version of the legal document that is mapped to the specified document type (AI Policy, Terms and Conditions, etc...) in a Legal preference category. |
Comments
0 comments