How Does Nelio A/B Testing Obtain Cookie Consent?

Nelio A/B Testing installs might install two type of cookies: two essential cookies, nabAlternative and nabSegmentation to ensure a consistent user experience while browsing the website and don’t track any information from any visitor, and some analytics cookies whose tracking data collected from visitors is used exclusively for statistical purposes without allowing identification of particular individuals.

The detailed list of cookies Nelio A/B Testing sets is described in the following article:

Several EU data protection supervisory authorities have recently issued guidance on which cookies require explicit consent according to the EU GDPR. From the information gathered so far, although it is mandatory to inform visitors about all cookies that may be installed in the user’s browser, only our analytics cookies fall into the category that requires explicit consent. Please note that this does not constitute legal advice and we recommend that you check the applicable law in your country.

Nelio A/B Testing adheres to data protection regulations in order to not collect tracking information. However, the decision to integrate the cookie consent control with Nelio A/B Testing is yours.

Your Visitors Cookie Consent

In this context, it is necessary to obtain the informed consent of visitors before installing our analytics cookies. One way to do this is to display a cookie consent pop-up.

Integration of Cookie Consent with Nelio A/B Testing

To integrate your cookie consent control with Nelio A/B Testing you have a GDPR Cookie setting which, briefly said, checks if your website has a certain cookie defined (with, optionally, a specific value). If it does, the plugin assumes your visitor gave you their consent and you’re allowed to track them–if it doesn’t, Nelio won’t track anything.

GDPR Cookie setting fields in Nelio A/B Testing

By using this setting and specifying the name of a cookie, you are setting the plugin to:

  • if the cookie does not exist, Nelio A/B Testing tracking is not executed and the events of your visitors are not tracked
  • if the cookie exists, it is executed, Nelio A/B Testing tracking is executed and the events of your visitors are tracked

💡 Make sure that in your cookie consent tool, you have set nabAlternative and nabSegmentation as Essential cookies, and all other cookies as Analytics.

Example

For example, you can set the GDPR Cookie field as follows:

  • Name: cookieyes-consent
  • Value: *analytics:yes*

​so that our plugin only tracks your visitor’s actions when the cookie cookieyes-consent exists and its value contains analytics:yes (that’s why we surrounded it with asterisks in the settings).

The process we follow is the following: when a visitor lands on a tested page, our plugin will randomly assign them one variant or the other, store the value in the essential cookie named nabAlternative, and load alternative content right away, regardless of their giving us consent or not.

If they don’t ever give us consent to track their actions, our plugin will honor their request and will not track them at all. However, the plugin will keep loading the appropriate alternative content. That is, it’ll keep loading the variant stored in nabAlternative. Then, as soon as the visitor gives us their consent to track their actions, our tracking script will kick in and do so.

See the following article for more details on how to integrate cookie consent plugins with Nelio A/B Testing: