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
  • 👉 Bucket allocation
  • 📖 Definition
  • ⚙️ Configuration
  • Interface
  • Use case attribution

Was this helpful?

Edit on GitLab
Export as PDF
  1. FEATURES SETUP

Bucket allocation

Previousvisitor experiment optionNextManaging visitor consent

Last updated 2 days ago

Was this helpful?

👉 Bucket allocation

📖 Definition

The Bucket allocation screen enables you to prevent your visitors from seeing all use cases at the same time and thus have reliable and statistically correct balance reports, as well as a clear and workable experience. This feature is especially useful when you have significant traffic and a lot of use cases running at the same time. You can place your use cases in different buckets in order to limit their visibility. The global traffic of your website is evenly split between the different buckets and your use cases can be placed in several buckets. It is available for all types of use cases: A/B test, Personalization, Feature Toggle and Progressive rollout.

⚙️ Configuration

Interface

The Bucket allocation screen displays two columns:

  • The use cases (left section)

  • The buckets (right section)

The left section displays all the use cases that can be placed in buckets, i.e. those you have enabled in the Main information step of your use case.

The attribution column indicates the number of buckets a use case has been placed in. On hover on the line, each bucket in which the use case is attributed is highlighted.

By default, use cases are not placed in any buckets.

🚩 Heads up

If a use case is in the left column but has not been attributed to any buckets yet, it won’t be seen by any visitors (0% of the traffic).

The right section displays all the buckets of your account.

You can use a maximum of 10 buckets and each one represents 10% of the overall traffic; meaning that traffic is evenly distributed between all buckets.

No matter how many buckets are used, they still represent 10% of the traffic. For example, if you fill only 5 buckets, those 5 buckets still include 10% of the overall traffic.

You can place several use cases within the same bucket (as many as you want). This means that a visitor belonging to a bucket will only see the other use cases attributed to the same bucket (if they meet the targeting criteria of the use cases).

However, they won’t be able to see a use case attributed to another bucket, even if they meet the targeting criteria.

For each bucket, you can see the number of attributed use cases at a glance. By clicking ‘see use cases’, you can visualize the names and types of the use cases.

You can also rename your buckets for easy organizing.

Use case attribution

Step 1: Enabling bucket allocation

For each use case, in the Main information step, you can decide whether or not you want your use case to be attributed to buckets.

If you push the toggle ON: you plan to restrict the visibility of your use case to a specific percentage of traffic (determined by the buckets) and commit to placing it in one or several buckets via the Bucket allocation page.

If you push the toggle OFF: there is no action required on the Bucket allocation page, your use case will be visible to all visitors matching its targeting with no traffic restriction.

Step 2: Placing use cases in buckets

To be able to place a use case in buckets, you need to have enabled the toggle from the Main information step of your use case beforehand.

To place a use case in a bucket, click it, select the desired buckets and save your configuration.

⭐ Good to know

If you want your use case to be visible to all of your traffic, you need to untoggle the bucket allocation button from the Main information step of your use case instead of placing it in all the buckets.

Once you have placed your use cases in buckets, you can save your configuration.

If you leave the page without saving, your modifications won’t be taken into account and won’t be applied to your website.

Need additional information?

Submit your request at product.feedback@abtasty.com

Always happy to help!

single_view.png

👉