How to choose your cookies deposit method
Last updated
Was this helpful?
Last updated
Was this helpful?
The restrict cookie deposit option enables you to manage the AB Tasty tag’s behavior to comply with regulations and adapt the configuration to user specificities. Since the implementation of the Guidelines on consent under Regulation 2016/679 (GDPR) by the European Data Protection Board on May 4, 2020, you have a legal obligation to ask your visitors for their explicit consent before tracking them and collecting their personal information through the acceptance of a cookie banner (either fully or partially).
Moreover, you must provide proof of this consent and AB Tasty must help you do so.
As soon as consent is given, proof of this consent is automatically sent to AB Tasty’s servers and stored for 13 months.
Stored consent information includes the date and time, the condition and mode used, the visitor ID, and the perimeter.
It remains your full responsibility to implement the cookie banner on your website and make its content compliant with local data protection regulations.
In the page in the settings, you must select one of these three options:
Not restricting cookie deposits. This means no consent is requested from the visitors and the campaign is automatically displayed and data tracked. Select this option only if your country / geographical area does not require you to ask for consent before collecting data.
Managing the consent proper to AB Tasty within a third-party tool, such as a TMS. In this case, the TMS automatically checks the visitor’s consent before triggering the tags it contains. Proof of consent will still be collected; however, the consent will specify that it was collected by an uncited third-party source.
Delegating the consent to the AB Tasty. In this case, the tag will try to determine whether the visitor gave their consent on the website before tracking them and collecting their data.
To help you to choose the right method for your cookie deposit policy, you can trigger our virtual assistant Ally by clicking on Start on the banner.
The tour explains all the options you can choose and the benefits and risks of each of them.
If you select the ‘Do not ask for visitor consent and track data anyway’ option, you won’t ask your visitor’s consent to track their data.
AB Tasty campaigns will be automatically displayed and all the actions they will perform will be tracked and stored. We don’t recommend selecting this option as it may not comply with your local legislation.
To activate the consent obtained by a third party, just choose the option.
When activating this option, the visitor’s consent is considered to have been given as soon as the tag is executed. The proof of consent will be written in the AB Tasty infrastructure instantly without checking any other trace of consent on the website.
When selecting this option, AB Tasty won’t be responsible for collecting the consent of your visitors.
💡 We recommend selecting this option only if you are currently centralizing consent management for your website in a specialized tool.
If you select the ‘Manage visitor consent directly in AB Tasty’ option, you will need to ask your visitor’s consent before being allowed to track and store their data. Consent will be managed directly by AB Tasty.
AB Tasty will automatically check the visitor’s consent before displaying campaigns. 💡 We recommend selecting this option as it complies with the European legislation and it enables campaigns to display without waiting for the visitor‘s consent.
You now need to choose how the tag will operate on your website when the visitor has not given their consent according to the campaign type.
If you tick a campaign type: campaigns of this type are triggered and the visitor can be assigned to a variation, or to the original version. As data is not tracked, the visitor may see different variations when browsing the website.
If you don’t tick a campaign type: campaigns of this type are not triggered and the visitor sees the original version.
In both cases, data is neither collected nor stored until consent has been given. Data will be collected as soon as the visitor gives their consent.
If you tick the box, the visitor may be assigned to a variation, but the actions they perform won’t be collected and stored, so they won’t count in the reporting.
If you don’t tick the box, the visitor will see the original version so the actions they perform won’t impact the results of the test either.
💡 We recommend not ticking this box as you need to collect data to analyze the results of a test. If a visitor doesn’t give their consent, they will see the test but your reporting will be empty. Also, the visitor may see different variations of a campaign across their website journey.
If you tick the box, the visitor will see the personalization, but the potential actions they perform won’t be collected and stored.
If you don’t tick the box, the visitor won't see the personalizations.
💡 We recommend ticking this box as you don’t necessarily need to collect data. If a visitor doesn’t give their consent, they will still be able to see the personalization.
If you tick the box, the visitor may be assigned to a redirection, but the actions they perform won’t be collected and stored, so they won’t count in the reporting.
If you don’t tick the box, the visitor won't see the redirection so the actions they perform won’t impact the results of the campaign either.
💡 We recommend not ticking this box as you need to collect data to analyze the results of a split campaign. If a visitor doesn’t give their consent, they will see the campaign but your reporting will be empty.
If you tick the box, the visitor may be assigned to a variation, but the actions they perform won’t be collected and stored, so they won’t count in the reporting.
If you don’t tick the box, the visitor will see the original version so the actions they perform won’t impact the results of the test either.
💡 We recommend not ticking this box as you need to collect data to analyze the results of an A/A test. If a visitor doesn’t give their consent, they will see the test but your reporting will be empty.
If you tick the box, the visitor will see the patch, but the potential actions they perform won’t be collected and stored.
If you don’t tick the box, the visitor won't see the patch.
💡 We recommend ticking this box as you don’t need to collect data at all when launching a patch. If a visitor doesn’t give their consent, they will still be able to see the patch.
You now need to choose how AB tasty will determine that a visitor has given their consent and therefore that their actions can be tracked and stored : you need to choose between the following options:
The user completes an action on the page
My website deposits its cookies
A specific cookie is placed
Didomi consent
Custom deposit (JavaScript)
Heads up ⚡
If AB Tasty detects the revocation of the visitor’s consent (that is to say, if the visitor uses functionality that cancels the consent they have previously given, or deletes the cookies from their browser), all standard data stored by AB Tasty on the visitor’s browser will be deleted and the visitor will no longer be tracked.
If you choose this option, the consent of the visitor is considered to have been given as soon as the user completes an action on the page (a scroll, a click, or any other action).
If you choose this option, the consent of the visitor is considered to have been given if the AB Tasty tag detects any other cookies on the page (from the website itself or a third-party tool).
Heads up ⚡
The first two options are legacy methods that do not comply with the GDPR. Only select one of these two options if you want or plan to implement the AB Tasty tag on your pre-production or staging environment, and for testing purposes.
Choose this option if your visitor’s consent is stored in a specific cookie. To configure this option, follow these steps:
Specify the name of your cookie
Select an option from the drop-down list: contains expression, regular expression or corresponds exactly
Enter the expected value of your cookie
As soon as the tag is executed, it will seek to confirm this condition and visitor tracking will only begin once consent has effectively been acknowledged. The tag will then conduct regular checks (upon each reload) to ensure the condition is still valid. If not, it will apply the effects specific to the revocation of consent.
Choose this option if you want visitor consent to be managed by Didomi. Didomi is a Consent Management Platform (CMP) that enables you to manage your vendors (or third-party tools), and their associated purposes, and to configure the way your visitors can consent to data usage.
Select this option if you want to create a custom JavaScript function to personalize the way consent is given by the visitor. This function must return ‘true’ if the condition is valid and if consent was obtained by the visitor. In this case, the AB Tasty tag will trigger and execute the JS function and start tracking.
💡 We recommend selecting this option only if the above options don’t meet your needs.
For more information about the Didomi integration, please refer to the following .
Select this option if you manage consent with specific JavaScript events when a visitor has given or revoked their consent. For more information, refer to this .