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
  • Introduction
  • How to access the demo
  • The demo and the predefined use cases
  • The sandbox

Was this helpful?

Edit on GitLab
Export as PDF
  1. DEMO

AB Tasty - Feature Experimentation & Rollouts Demo - How to use it

PreviousDefining rights per projectNextArchiving use cases from the dashboard

Last updated 2 days ago

Was this helpful?

This article will provide information about the AB Tasty - Feature Experimentation & Rollouts demo made in React.js

Introduction

To help you understand what are the principles behind Flagship, we have created a hosted demo and a sandbox environment (for developers) which will help you understand how our solution can be used in a real use case.

We have created a set of predefined use cases which are linked to the demo. This article explains how to link your account to the demo to let you play with it.

The purpose of the demo is to show how to use Flagship and have examples of how to name a flag.

Here is the access to the hosted demo Here is the access to the sandbox to play with code

How to access the demo

The Flagship demo will require your credentials to let you control it. Below is the process to do so:

On the Flagship platform, go to Settings β†’ Environment setting

Capture_d_e_cran_2022-11-07_a__10.58.13.png

You will have access to your API KEY / ENVIRONMENT ID. This pair of keys will allow you to control the demo directly from your account.

Here is the link to access the demo: Flagship demo

To access and have control of the demo, you'll have to enter your API KEY and ENVIRONMENT ID in the dedicated sections.

After putting your credentials, you will have access to the demo.

The demo and the predefined use cases

For this demo, we have created a set of predefined use cases. You'll find them inside the project "Flagship demo" in your account.

Each use case will let you see how Flagship can affect the demo. Here are detailed explanations for each use case :

Use case: test on the "pay" wording of the CTA

This use case is an A/B test. It will show you how to set an A/B test on Flagship. It targets all users and has a targeting of 50/50. This means that you have a 50% chance to get either the original wording (Pay) or the variation one (Order now).

Every new visitor has a chance to have each message, to help you review the result of the A/B Test in our demo, we have implemented a way to change your visitor ID (The attribution system we use to differentiate every visitors of your website).

You can put what you want as a Visitor ID, validate, and it will set the new visitor to the page.

For each new visitor IDs, a new attribution will be made, with this you'll be able to test the results of the A/B test.

Use case: Enable PayPal for All

This use case is a feature toggle. It's controlling if the Paypal payment method is active or not on the demo app. This will show you how to enable/disable a feature for all users.

(the PayPal button to show or not on the demo)

Use case: Payment page settings - Header and CTA color

This use case is a feature toggle. It allows you to control some parts of the demo and shows how you can use Flagship as a remote control center to configure and control part of the website remotely and without doing a release.

(The use case is controlling the header color and title + the payment CTA color when it's enabled/disabled)

Use case: Choose Payment Provider Per Device

This use case is a feature toggle. It will show you how to set targeting criteria.

In the targeting section of this use case, we have set 2 types of targeting criteria, iOS users and Android users.

(iOS users targeting)

(Android users targeting)

if the user comes from an Android or an Apple device, we will show the different payment methods for each operating system.

(if the user is an Android user, the website will show the GooglePay payment method)

(if the user is an Apple user, we will show the ApplePay payment method)

The sandbox

We have created a sandbox environment to help developers understand how Flagship is implemented.

The hosted demo and the sandbox share the same code base, so it's the same code on both.

The sandbox also shares the same authentication method. You just have to follow the same steps as shown for the demo.

Here is the access to the sandbox environment: Flagship demo sandbox

Capture_d_e_cran_2022-11-07_a__11.00.08.png

Capture_d_e_cran_2022-11-07_a__14.19.39.png

(Original)

(Variation)

Capture_d_e_cran_2022-12-08_a__09.53.01.png
Capture_d_e_cran_2022-11-07_a__14.27.31.png
Capture_d_e_cran_2022-11-07_a__14.31.18.png
Capture_d_e_cran_2022-11-07_a__14.33.02.png
Capture_d_e_cran_2022-11-07_a__14.35.35.png

Capture_d_e_cran_2022-11-07_a__15.46.41.png
Capture_d_e_cran_2022-11-07_a__15.46.46.png
Capture_d_e_cran_2022-11-07_a__15.49.19.png
Capture_d_e_cran_2022-11-07_a__15.48.52.png