Home › Documenation

Does Nelio A/B Testing Work with Cookie Plugins?

Yes. Nelio A/B Testing is compatible with most WordPress cookie consent plugins, including CookieYes, CookieScript, Cookiebot, WPConsent, and Complianz.

To ensure that consent is respected, you may need to configure both your cookie plugin and Nelio A/B Testing’s GDPR Consent Cookie setting. Once configured, Nelio will only record analytics after the visitor has granted consent, while continuing to deliver a consistent testing experience.

Table of Contents

Nelio A/B Testing uses two categories of cookies:

Essential cookies

These cookies are required for tests to work correctly.

For example, cookies such as nabAlternative and nabSegmentation ensure that visitors continue to see the same variant throughout a test.

These cookies don’t collect analytics data and are only used to provide a consistent user experience.

Analytics cookies

Analytics cookies are used to measure the performance of your tests by recording page views, conversions, and other test events.

The information collected is used exclusively for statistical purposes and does not identify individual visitors.

If you’ve configured the GDPR Consent Cookie setting, these cookies and the associated tracking events are only enabled after the required consent has been granted.

🔍 Learn more: What Cookies Does Nelio A/B Testing Set?

When a visitor arrives on a page participating in a test:

  1. Nelio assigns the visitor to a variant.
  2. The assigned variant is stored in the essential nabAlternative cookie.
  3. The visitor immediately sees the correct version of the page.
  4. If analytics consent hasn’t been granted, Nelio doesn’t record any page views, conversions, or other tracking events.
  5. As soon as the required consent cookie is detected, Nelio begins tracking test data.

This approach ensures that visitors enjoy a consistent experience while allowing you to respect their privacy preferences.

To enable consent-aware tracking, configure the GDPR Consent Cookie setting in Nelio A/B Testing → Settings → Tracking.

GDPR cookie settings in Nelio A/B Testing

The following sections describe the required configuration for the most common cookie consent plugins.

  • CookieYes
  • Cookie Script
  • Cookiebot
  • WPConsent
  • Complianz

After labeling nabAlternative and nabSegmentation as necessary cookies and the other nab cookies as analytics cookies in CookieYes, please set our plugin’s GDPR setting as follows to make sure our :

  • 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).

After labeling nabAlternative and nabSegmentation as strictly necessary or essential cookies and the other nab cookies as performance cookies in Cookie Script, please set our plugin’s GDPR setting as follows:

  • Name: CookieScriptConsent
  • Value: *"action"*"accept"*"categories"*"performance"*

​so that our plugin only tracks your visitor’s actions when the cookie CookieScriptConsent exists and its values contains “action” “accept” “categories” “performance” (that’s why we surrounded it with asterisks in the settings).

After labeling nabAlternative and nabSegmentation as necessary cookies and the other nab cookies as statistics cookies in Cookiebot, please set our plugin’s GDPR setting as follows:

  • Name: CookieConsent
  • Value: *statistics:true*

​so that our plugin only tracks your visitor’s actions when the cookie CookieConsent exists and its values contains statistics:true (that’s why we surrounded it with asterisks in the settings).

After labeling nabAlternative and nabSegmentation as Essential cookies and the other nab cookies as Statistics cookies in WPConsent, please set our plugin’s GDPR setting as follows:

  • Name: wpconsent_preferences
  • Value: *"statistics":true*

​so that our plugin only tracks your visitor’s actions when the cookie wpconsent_preferences exists and its values contains “statistics”:true (that’s why we surrounded it with asterisks in the settings).

After labeling nabAlternative and nabSegmentation as complz_functional cookies and the other nab cookies as cmplz_statistics cookies in Complianz, please set our plugin’s GDPR setting as follows:

  • Name: cmplz_statistics
  • Value: *"allow"*

​so that our plugin only tracks your visitor’s actions when the cookie cmplz_statistics exists and its values contains allow (that’s why we surrounded it with asterisks in the settings).