Managing Visitor Consent

Depending on the privacy regulations applicable in each country (such as GDPR or CNIL), you may have a legal obligation to ask visitors for explicit consent before tracking them or collecting personal data.

Feature Experimentation and Rollout (FE&R) allows you to control data collection through a variable exposed in the SDK. This variable determines whether visitor data can be collected depending on the consent status.

Accepting tracking (data collection consent) typically means that a visitor has accepted the website’s cookies, usually via a cookie banner or consent management platform.

Configuration

Visitor data collection can be managed through a parameter set directly in the SDK code of your Feature Experimentation and Rollout implementation.

The visitor consent parameter is currently available in the following SDKs:

• Android

• iOS

• Java

• Flutter

Variable set to true

By default, the .withVisitorConsent variable is set to true, meaning that visitor data can be collected.

If a visitor does not consent to data collection, you should update this parameter accordingly in your implementation.

Example using the Android SDK:

Variable set to false

You can set this parameter to false to block data collection when a visitor has not given their consent.

When the variable is set to false:

• A hit is sent to indicate that the visitor did not consent to data collection

• FE&R will still send technical data but will not collect visitor data

In this case:

• You cannot determine whether the visitor has been assigned to a flag

• You will not see the results of the visitor’s actions on the website or application

However, this parameter only impacts data collection. It does not affect campaign delivery. Visitors will still experience the campaigns they are eligible for, even if consent is set to false.

This setting is not retroactive. Data collected before the variable was set to false will not be deleted, but no new visitor data will be collected afterwards.

To learn more about implementation details for your specific stack, refer to the technical documentation