This section refers to a deprecated version of the product. The new version is FE&R. To access FE&R, contact your CSM.
📘 To learn more, read the FE&R documentation.
LogoLogo
PlatformsPricingRessources
  • User documentation
  • Onboarding
  • Help Center
  • Release Notes
  • Flagship - Deprecated
  • Feature Experimentation & Rollout (ex-Flagship) is evolving!
  • GETTING STARTED
    • 👉Managing multiple environments
    • Using the trial version of Flagship
  • First steps with Flagship
    • Quick start guide
    • Glossary
  • Implementation
    • Sending transactions from the AB Tasty Shopify app directly to Feature Experimentation & Rollouts
  • Integrations
    • Heap Analytics integration (Push)
    • Tealium AudienceStream (receive audiences)
    • FullStory integration (segment exports)
    • Heap Analytics integration (Pull)
    • Google Analytics integration (pull audiences)
    • Segment Integration (receive traits)
    • Mixpanel integration (cohort exports)
    • 👉Retrieving your third-party tools’ audiences in AB Tasty - Feature Experimentation & Rollouts
    • Zapier integration
    • Segment integration
  • Steps configuration
    • 👉Configuring Sequential Testing Alerts
    • 👉Configuring your Flags
    • 👉Using the scheduler
    • 🛠️[Troubleshooting] How to target a large number of users at the same time?
    • 👉Configuring KPIs
    • 👉Using the automatic rollback option
    • 👉Targeting configuration
    • 👉Dynamic allocation
    • 👉Traffic allocation
  • Team
    • Access Rights, Teams & User Management
    • 👉Defining rights per project
  • DEMO
    • AB Tasty - Feature Experimentation & Rollouts Demo - How to use it
  • Navigating the interface
    • 👉Archiving use cases from the dashboard
    • 👉Flags page
    • 👉Running a search on the dashboard
    • Navigating the Flagship interface
  • REPORTING
    • 👉Verifying your hit setup
    • 👉Exporting reporting data
    • Understanding the "Chances to win" indicator
    • 🛠️[Troubleshooting] How can I know my test is reliable and my data significant enough to be analyzed?
    • Reporting - A/B Test
    • 👉Using the reporting filters
  • API keys & Settings
    • 👉Acting on your account remotely
    • 👉Using Experience Continuity
    • visitor experiment option
  • FEATURES SETUP
    • 👉Bucket allocation
  • SDKs integration
    • 👉Managing visitor consent
    • 👉Understanding the use of SDKs
  • FAQ
    • Can I make a comparison for each reporting?
    • Can I use Flagship even if my SDK stack is not available?
  • Platform integration
    • 👉Webhooks page
  • Decision API
    • Decision API for non-techie users
  • Account & Profile
    • 👉Configuring account restrictions with MFA
    • 👉Configuring a FA on your profile
  • RELEASE NOTES
    • October - Flagship becomes Feature Experimentation & Rollouts
    • February - Release Notes
    • 📅January - Release Notes
    • 🎉December - Release Notes 🎉
    • 🦃November - Release Notes
    • September Release Notes 🎨
    • June Release Notes 🐞
    • 🍸May Release Notes ☀️
    • Flagship Release Notes April 🐇
    • Flagship February release notes 🏂
    • Flagship January release notes 🎉
    • Flagship November release notes 🦃
    • Flagship October Release Notes 🎃
    • Flagship September Release note 🎒
    • Flagship August Release Notes 🐬
    • Flagship Release Notes July ☀️
    • Flagship Release notes June 🌻
    • Flagship Spring Release May 🌸
    • Flagship Release Notes: Fall
  • Use cases
    • 👉Duplicating a winning variation
    • 👉Configuring a Feature Toggle/Flag
    • 👉Configuring an A/B Test
    • 👉Configuring a Progressive rollout
    • 👉Configuring a Personalization
  • VIDEO TUTORIALS
    • [Video Tutorial] AB Test
    • [Video Tutorial] Feature Flag
    • [Video Tutorial] Progressive Deployment
Powered by GitBook
LogoLogo

AB Tasty Website

  • Home page AB Tasty
  • Blog
  • Sample size calculator
  • Release note

AB Tasty Plateform

  • Login

© Copyright 2025 AB Tasty, Inc, All rights reserved

On this page
  • 📖 Definition
  • ⚙️ Configuration
  • Variable set to true
  • Variable set to false

Was this helpful?

Edit on GitLab
Export as PDF
  1. SDKs integration

Managing visitor consent

PreviousBucket allocationNextUnderstanding the use of SDKs

Last updated 2 days ago

Was this helpful?

📖 Definition

Depending on the different privacy rules of each country (ie: GDPR and CNIL), you may have a legal obligation to ask your visitors for their explicit consent before tracking them and collecting their personal information.

A variable displayed in your SDK enables you to manage data collection, depending on whether a visitor accepts to be tracked or not.

Accepting to be tracked (data collection consent) generally means accepting a website’s cookies (often in the form of a banner).

⚙️ Configuration

Data collection can be managed via a parameter, directly in the SDK code of your Flagship implementation.

⭐ Good to know

The visitor consent parameter is available for the following SDKs:

  • Android

  • iOS

  • Java

  • Flutter

Variable set to true

By default, the .withVisitorConsent variable is set to true, meaning that you will be able to collect visitor data. Don’t forget to change that default behavior if the visitor does not consent to data collection. Here is an example with the Android SDK:

Variable set to false

You can change this parameter to false to block the data collection when a visitor has not given their consent. In this case, a hit will be triggered to specify that this visitor didn’t consent to data collection.

Flagship will still be able to send data but won’t receive any from the visitor.

When setting the variable to false, you won’t be able to know if the visitor has been assigned to a flag and you won’t see the results of their actions on the website or application (if any).This parameter only impacts data collection, but has no effect on use cases display. Even if your variable is set to false, your visitors will still see the use cases they’re affected to.

To know the implementation methods according to your stack, please refer to our technical documentation.

⭐ Good to know

This option isn’t retroactive. If you have collected data before the variable was set to false, it won’t be deleted. However, new data won’t be collected.

Need additional information?

Submit your request at product.feedback@abtasty.com

Always happy to help!

👉