AB Tasty
How to configure AB Tasty at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Improve the service, Personalise the website
Overview
This guide explains how to implement different privacy configurations for AB Tasty and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. The AB Tasty client-side tag for A/B testing and personalisation. AB Tasty is a French company.
What the service does in this scope. The first-party ABTasty cookie (13 months) holds the visitor ID, campaign history and timestamps; ABTastySession holds session data. The cookie deposit method is selected in Settings > Privacy. With a consent condition, AB Tasty offers a default mode (the tag executes but collects and stores no data until consent) and a strict mode (the tag does not execute until consent). Proof of consent is sent to AB Tasty's servers and stored for 13 months.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Strict mode: tag blocked until consent; tests only. |
| Configuration B — Higher risk | Personalisation campaigns with audience segments, after consent. |
No configuration without prior consent. In default mode the tag runs before consent and can display variants, though it stores no data. Because running test variants still reads the device, this guide uses strict mode / Consenter blocking in both configurations.
Step 1 — Configure AB Tasty
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service; Personalise the website |
| 2 | Cookie deposit method | Settings > Privacy (consent condition, e.g. CMP or specific cookie) | Consent condition set | Consent condition set |
| 3 | Mode | waitForConsent.isStrict | Strict | Strict |
| 4 | Campaign types | Campaign editor | A/B tests | Tests and personalisation |
| 5 | URL sanitising | Regex to remove sensitive data from URLs sent to the collect | Configure | Configure |
Step 2 — Map the configuration in the Consenter Manager
Processing location. AB Tasty is a French company; check hosting and sub-processors in the DPA, and list the United States as a potential access location if US providers are used.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Improve the service | Improve the service, Personalise the website |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers |
| Data categories | Browsing and interaction data, Device characteristics, Device identifiers, Privacy choices | As A, plus Users' profiles |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | Group based (behaviour) |
| Maximum storage duration | 13 months | 13 months |
| Processing location | Per DPA | Per DPA |
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on