[Troubleshooting] Why does my user see a campaign when they did not give their consent?

You have launched an experiment (e.g., A/A test, A/B test, or multi-page test) or a personalization campaign that requires visitor consent, and yet you keep seeing it even without consent. Here's why:

Understanding when the tag needs consent

Visitor consent is required to retain, use or collect data about their navigation and behavior. The AB Tasty tag is not supposed to create cookies or browser storage, send data to our servers nor fetch information about the visitor that might identify them. To help you with that, we provide tools to set the tag correctly.

However, consent is not required to display a campaign as long as it is not based on personal data. This is why you can display a patch, personnalization or an A/B test without consent.

ℹ️ note that since no data will be collected, there is no sense in displaying an A/B test without consent.

If you are seeing a campaign that should not be displayed, this can come from several causes.

Possible cause: incorrect consent setup

In your account privacy and consent configuration page, make sure you have allowed the correct campaign types to launch without consent.

Possible cause 2: unexpected campaign type

Eventhough you can create determine campaign type (A/B, Perso, A/A, patch, etc), the tag can consider a type to be another type, regardless of what you have created. This comes from the legacy management of the period where a user couldn't create a certain type (eg. the patch type).

Make sure your campaign is not recognized as another type. The patch type is much prone to this issue.

Solution: review and correct your consent configuration

Verify the types of campaigns allowed to launch without consent. Also make sure that the campaign(s) you are seeing when you should not is not considered as another type by the tag. For further guidance, refer to our dedicated articles.

Traffic allocation stepHow to create a Segment (Who section)