Managing your visitors’ Privacy

This section enables you to manage campaign execution as well as the data collection based on visitor consent.

Restricting cookie deposit

The restrict cookie deposit option enables you to manage 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 adopted on 4 May 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 it is AB Tasty's duty to help you do so.
As soon as consent is given, proof of this consent is automatically sent to AB Tasty servers and stored for 13 months.
The consent information stored includes the date and time, the condition and mode used, the visitor ID and the perimeter.
You must select an option among these three:

• Not restricting cookie deposit. 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 doesn’t 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. Consent of proof will still be collected; however it will bear the specification of having been collected by an uncited third-party source.
• Delegating the consent proper to AB Tasty to the tag. 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.

It remains your full responsibility to implement the cookie banner on your website and make its content compliant.

Managing consent within a third-party tool

To activate the consent obtained by a third party, apply the following steps:

1. Toggle the Restrict cookie deposit button to No.
2. Check the The cookie deposit restriction and its consent collection are handled on my side box.

When activating this option, the visitor’s consent is considered as being 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 the consent on the website.
When selecting this option, AB Tasty won’t be responsible for collecting the consent of your visitors.

Delegating consent to the AB Tasty tag 

To enable AB Tasty to determine the presence of the consent and to execute the tag properly if need be, apply the following steps:

1. Toggle the Restrict cookie deposit button to Yes.
2. Choose one of the following options:

• The user completes an action on the page 
• My website deposits its own 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 a functionality that cancels the fact that the consent has previously been 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.
 

The user completes an action on the page

If you choose this option, the consent of the visitor is considered given as soon as the user completes an action on the page (it can be a scroll, a click or any other action).

My website deposits its own cookies

If you choose this option, the consent of the visitor is considered given if the AB Tasty tag detects any other cookies on the page (from the website itself or from a third-party tool).

🚩 Heads up

The two first options are legacy methods which do not comply with the GDPR. Only select one of these two options if you want/plan to implement the AB Tasty tag on your pre-production/staging environment and for testing purposes.
 

A specific cookie is placed

Choose this option if your visitor’s consent is stored in a specific cookie. To configure this option, apply the following steps:

1. Specify the name of your cookie.
2. Select an option from the drop-down list: contains expression, regular expression, corresponds exactly.
3. 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 carry out regular checks (upon each reload) to make sure the condition is still valid. If not, it will apply the effects specific to the revocation of consent. 

Didomi consent

Choose this option if you want visitor consent to be managed by Didomi. For more information on Didomi, refer to Didomi integration.

Custom deposit (JavaScript)

If you are not satisfied with the options listed above, you can create a custom JavaScript that will check the validity of the consent.
Because of the structure of consent storage on your website, it is not possible to target a cookie. However, you can build a JavaScript function which will check how the consent was given by the visitor. This function returns ‘true’ if the condition is valid and if consent was obtained.
In this case, the tag will trigger, execute the JS function and start the tracking. The tag will then carry out regular checks (upon each reload) to make sure the JS function still returns ‘true’. If not, it will apply the effects specific to the revocation of consent.

Restricting campaign execution

If you have chosen to delegate the consent proper to AB Tasty to the tag, you need to choose how the AB Tasty tag will operate on your website when the visitor has not given their consent according to the type of campaign. 
By default, all types of campaigns are ticked. In this case:

• Campaigns of this type are triggered and the visitor can be assigned to a variation/experience/Page. They can also see the original version, depending on the traffic allocation you have configured for your campaign.
• Data is neither collected nor stored until consent has been given. Data will be collected as soon as the visitor gives their consent.

When a box is unticked, it means that:

• Campaigns of this type are not triggered and the visitor sees the original version.
• Data is neither collected nor stored until consent has been given. Data will be collected as soon as the visitor gives their consent.

In both cases, AB Tasty only focuses on its own perimeter. Basing the execution of the AB Tasty tag on the consent of a different perimeter (such as other analytics or personalization tools) is completely non-compliant, as is basing the execution of a different tool on the consent granted to AB Tasty.
Indeed, the objective of a campaign may differ according to its type, and you should thus adapt the campaign execution restriction accordingly:

Type of campaign	Main objective	Need to collect data	Recommendation
TEST A/B Multipage Multivariate	Comparing one or several variations to the original version.	Yes	Restrict campaign execution (box unticked)
PERSONALIZATION Simple Multipage Multi-experience	Personalizing the experience of one or several visitor segments.	Not necessarily	Do not restrict campaign execution (box ticked)
SPLIT CAMPAIGN	Comparing a new page (created and hosted outside of AB Tasty) to the original page.	Not necessarily	Restrict campaign execution (box unticked)
A/A TEST	Tracking elements and monitoring visitor behavior on a specific page.	Yes	Restrict campaign execution (box unticked)
PATCH	Correcting an element urgently for a limited period.	No	Do not restrict campaign execution (box ticked)

🚩 Heads up

Even if some types of campaigns don’t necessarily need to collect data, they may include one or more targeting criteria that require visitor data such as the last purchase or the landing page criterion.
Even if you don’t restrict campaign execution (box ticked), the campaign won’t be displayed until visitor consent has been given.
 

Related articles

Managing cookie deposit