Active Cookie Consent Method of Visitor Data Privacy Management – Dynamic Yield Knowledge Base

Active Cookie Consent is one of two methods of managing the data privacy settings of your visitors using APIs. In this method, users are not served personalized experiences unless they actively provide consent.

What Happens When Users Have Not Provided Consent?

Data about users is not collected, and they are not served personalized experiences unless they actively indicate their consent. This list provides more details about how users are treated who have not provided consent:

They will not have any Dynamic Yield cookies in their browser unless it is a cookie you create in the Javascript code of a variation.
Their data will not be included in any reports.
No record of which variations they were served is saved, so the variations they are served may change with every refresh (no variation stickiness). However, you can use the opt-out targeting condition to target variations to these users.

Additionally, different campaign types are affected in different ways:

They will not be served with any Overlays, Notifications, Custom Code, Visual Edit, and Push Notification campaigns.
Recommendations using personalized algorithms will fall back to the closest un-personalized algorithm. For details, see Recommendation Fallbacks.
For all other campaign types, they will only be served with experiences that do not include personalized targeting conditions (the conditions in the category Who › User Properties and Session Behavior).
Consent for triggered email campaigns is not managed using Active Cookie Consent. To handle consent for these campaigns, see Enabling Triggered Emails.

Users can opt-in or out at any time, and can change their previous state without limitations.

Limitations:

When previewing campaigns or variations as a Dynamic Yield teammate, you must consent to Active Cookies on the site. Otherwise, you will not be served variations that use personalized targeting conditions.
Dynamic Links, Display Ads, and Landing Pages may fail to attribute conversions when Active Cookie Consent is enabled. These campaigns will continue to be served as expected.

Using the Active Cookie Consent APIs

Determine each user’s privacy preference and manage the list on your side.
If you were previously using the Assumed Consent APIs and are migrating to Active Cookie Consent, delete the original API calls in your site before implementing this method.
Indicate each user’s preference by adding one of the following lines to the header of each page on your site. If you do not have information about the user's preference do not add anything. If the line is missing and there are no previous cookies from Dynamic Yield, we assume the user does not consent.
Visitor consents:
```
DY.userActiveConsent = { accepted: true }
```
Visitor does not consent:
```
DY.userActiveConsent = { accepted: false}
```
If the user changes their consent status, use the following API call to immediately start or stop collecting their data.
Visitor consents:
```
DYO.ActiveConsent.updateConsentAcceptedStatus(true)
```
Visitor does not consent:
```
DYO.ActiveConsent.updateConsentAcceptedStatus(false)
```
Preview your site for users who have not provided consent after the feature is enabled:
1. Go to Settings › General Settings › Active Cookie Consent and click Preview Site.
2. Make sure all of your campaigns are being served.
3. If a campaign is not being served, update the targeting settings to make sure that at least one variation does not use personalized targeting conditions (the conditions in the category Who › User Properties and Session Behavior). You will be able to use a dedicated targeting condition to target opted-out users directly.
Contact your Customer Success Manager to enable active cookie consent mode on your site.
If you are using a custom integration, use an additional API in the code of the Custom Integration to prevent private user data from being sent to a third party.

You can preview your site and view the status of Active Consent in Settings › General Settings.

If you use a personalized targeting condition when creating variations, an indication is added to let you know that users who have not given active cookie consent will not be served this variation.

Verifying That Data is Not Being Collected

If a user would like to verify that data is not being collected by Dynamic Yield, they should look for the strings px.dynamicyield.com and px-eu.dynamicyield.com in their network calls. These strings should not exist if data is not being collected.