Analytics analytics_storage

AB Tasty — consent fix

AB Tasty (A/B testing and personalisation platform) loads its script (cdn.abtasty.com/ACCOUNT_ID.js) before consent. ABTasty cookie (1 year) and ABTastySession are set before consent is given. AB Tasty processes visitor behaviour for experiment assignment and may be linked to CRM data.

Domains

  • abtasty.com
  • cdn.abtasty.com
  • try.abtasty.com
  • d2vu84xrmqbskl.cloudfront.net

Cookies

  • ABTasty
  • ABTastySession

The personalisation and A/B testing platform AB Tasty immediately sets the ABTasty (valid for 1 year) and ABTastySession cookies upon loading. The script tracks your visitor's behaviour to determine which test segment they fall into. Because this can be linked to CRM data and builds user profiles, it falls under analytical cookies (statistics). If you load this script before your visitor has accepted the cookie banner, you are in violation of the GDPR.

Why AB Tasty loads too early

AB Tasty is designed to start as early as possible in the page load process (often directly in the <head> or high up in Google Tag Manager) to prevent so-called "flicker" (the flashing of the original page before the test version loads). Because of this need for speed, the script often bypasses your Cookie Management Platform (CMP).

The Fix: Link AB Tasty to consent

To make AB Tasty compliant, you can use Google Tag Manager (GTM) or the native Privacy settings within AB Tasty itself.

1. Use an Exception Trigger in GTM (Most common)

If you load AB Tasty via GTM, you must tell GTM that the tag may only fire if there is consent for analytics_storage.

  1. Open your AB Tasty Tag in GTM.
  2. Go to Triggering.
  3. Click Add Exception.
  4. Click the + icon to create a new trigger, type Custom Event.
  5. For Event name, enter .* and check the box for Use regex matching.
  6. Select Some Custom Events.
  7. Set the condition: Consent State — analytics_storage does not equal granted.
  8. Save and publish.

2. AB Tasty Privacy Dashboard (if available)

Depending on your license, AB Tasty has its own privacy feature built into the dashboard.

  1. Log in to AB Tasty.
  2. Go to Settings > Privacy.
  3. Check the option Require consent before tracking.

3. The Native Consent API (For hardcoded scripts)

If you pasted the script directly into the HTML, you can use the AB Tasty Consent API to suspend the setting of cookies. First, initialise the configuration with consent set to false:

window.ABTastyConfig = { consent: false };

As soon as your CMP fires the approval event (statistics accepted), call the following function:

if (window.abtasty && window.abtasty.enableCookies) {
    window.abtasty.enableCookies();
}

How to Verify the Fix

Perform a thorough test using your browser's Network tab to ensure that AB Tasty waits patiently.

  1. Open your website in an incognito window.
  2. Ignore the cookie banner (do not click anything).
  3. Open Developer Tools (F12) and navigate to the Network tab (or the Application tab to inspect cookies).
  4. In Network, search for cdn.abtasty.com. There should be no requests visible (unless you are using the Consent API method).
  5. In the Application tab (under Cookies), verify that the ABTasty cookie has not been placed.

Not sure if the fix worked, or want to verify that no other scripts are leaking data? Run a free scan with ConsentChecker.eu for instant confirmation.

Sources

No CMP yet?

A Cookie Management Platform (CMP) handles consent automatically for AB Tasty and other trackers — including the correct GTM integration.

Cookiebot → CookieYes → CookieFirst → Complianz → Borlabs Cookie → Enzuzo → ConsentOS →

Check your own site

Scan your website for free to see if AB Tasty (or other trackers) loads before consent.

Start free scan →