We’re making major improvements to the platform, adding new features and enhancing your overall experience.

You are currently viewing documentation for the deprecated version of our product. The latest version, called FE&R (Feature Experimentation & Rollout) is now on early access for all clients on AB Tasty platform.

Official Early Access for everyone!

We’d love to hear your thoughts and offer you exclusive early access to these exciting updates.

Answer a 30 sec form and get your access to a brand new experience!

. 📘

Introduction

The AB Tasty > Mixpanel Connector allows you to automatically send server-side experiment data from AB Tasty’s Feature Experimentation platform to Mixpanel. This integration enables you to analyse how specific feature flags and variations impact your product metrics directly within Mixpanel, providing consistent, event-based tracking without requiring client-side scripts.

📖 Definition

Environments are organizational units which allow you to manage your use cases throughout the entire development lifecycle, from local development to production, in order to minimize bugs, facilitate QA and accelerate your team development capacity. By default, you only have access to the PROD and PREPROD environments, but Flagship enables you to create new environments and to manage and personalize the existing ones directly from the platform. \

⚙️ Configuration

Creating environments

Adding multiple environments on your Flagship account can be helpful as it enables you to have the same environment configuration as your engineering team and to reproduce the same workflow. To create a new environment, you must have a Super Admin .

1. Once an environment is created, all projects (use cases not included) and persona keys from your PROD environment are duplicated to your new environment. From the dropdown menu displaying all your current available environments, click Create an environment: A pop-up appears.

2. Fill in the name of your new environment.

3. Click CREATE: You are redirected to your new environment.

The same quota as the PREPROD default environment is applied. To be able to use your new environment, you must enter its specific Environment ID and API key in your codebase.

Managing existing environments

You can also manage your existing environments.

From the dropdown menu displaying all your current available environments, you can:

• Edit an environment’s name by clicking the edit icon.

• Delete an environment by clicking the delete icon (except PREPROD).

These actions do not apply to the PROD default environment.

💡 Use case

Let’s say you have a development lifecycle made of three different environments: Staging, Pre-production and Production. To make it easier for you and your team, you want to reproduce the same workflow on Flagship and want to add the staging environment, as the Pre-production and Production ones already exist by default on your account. To do so:

1. From the dropdown menu displaying all your current available environments, click Create an environment.

2. Enter the name of your new environment.

3. Click CREATE.

4. Go to Settings > Team.

You can now duplicate your existing use cases from the Production and Pre-production environments to the Staging one, or create new use cases from scratch.

Need additional information?

Submit your request at

Always happy to help!

\

Introduction

The AB Tasty > GA4 Push Connector enables you to automatically send server-side experiment data from AB Tasty’s Feature Experimentation platform to Google Analytics 4 (GA4). This integration allows you to analyse how specific feature flags and variations impact your key metrics directly within GA4, without requiring client-side tracking.

Once configured, the connector pushes campaign and variation identifiers as custom events in GA4 whenever a decision is made for a visitor. This ensures consistent experiment tracking across both platforms, enabling more unified reporting and deeper behavioural insights.

How-to

Heap is a Product Analytics company that provides analytics infrastructure and helps their clients to focus on discovering insights and taking action, not writing tracking code.

The Heap Analytics integration allows you to import your Heap segments in Flagship so you can target them with Flagship use cases.

Once the integration is active on Flagship you need to export the segment from Heap.

This article will walk you through the different steps to setup the integration on Mixpanel side and to export your cohorts.

Enable the integration on Flagship

To enable the integration on Flagship, follow the steps below:

1. Access Settings > Integrations > Pull

2. In the dropdown, select Heap Analytics.

3. Click the link in the description Click Here (in the red square in the screenshot above).

4. You will be redirected to the Heap Analytics interface in which you will be able to allow the Flagship integration to access your Heap environment (this is necessary to enable integration between the two tools). Click Allow.

The Heap Analytics integration is set up. You now need to export the Heap segment to Flagship. This is done on the Heap Analytics interface, and it is explained in the next part of this article.

Export the the Segments From Heap Analytics to Flagship

To be able to target your Heap segments with Flagship usecases, you now need to export the desired segments to Flagship.

To export the segments to Flagship, follow the steps below:

1. Access Definitions > Segments to see the list of defined segments.

2. Select the segment you want to export to Flagship.

3. In the segment panel, under Integrations, turn on the Flagship switch.

4. In the export config, choose FlagshipVisitorId as the Heap User ID.

1. Click Confirm.

You will be able to choose Enable Recurring Sync. We recommend using this option to keep your segment updated in AB Tasty. Confirm by clicking Enable Recurring Sync or Sync now.

For global information on retrieving audiences, please refer to .

Need additional information? Submit your request at Always happy to help!

Quick start guide

This article explains how to start with Flagship, including basic concepts and giving you keys to create your first feature.

🧙 Technical implementation

In Flagship, traffic allocation depends on a combination of a Murmurhash algorithm and a variationGroupId. Each visitorId sent to the API (through POST request or thanks to the SDK) will be processed by this algorithm and, depending on the results, the visitor will be assigned to a specific variation.

The API uses the same bucket-style as the bucketing feature. Depending on the percentage of traffic you configured in the platform, visitors will be assigned to a specific bucket. It is the same principle for dynamic allocation. The only difference is that the allocation changes depending on report results. However, a user who has already been assigned to a variation will still see the same variation. Dynamic allocation redirects only new visitors to the best performing variation. Learn more about dynamic allocation.

Need additional information?

Submit your request at [email protected]

Always happy to help!

What is a reporting comparison?

A reporting comparison is used to analyze different variations of a feature. It allows our Bayesian algorithms to accurately determine which variation will perform best in terms of earnings, conversion rate and so on.

Which use case is it available for?

Being able to compare several variations is only applicable for A/B tests. In Feature toggling, there is no variation to compare when doing feature management, as we are evaluating the individual performance of the feature itself. For personalization, we are mainly looking to create several scenarios for specific audiences, and separately analyze their performances. For progressive rollout, we are looking to deploy a feature gradually to your users and want to measure the effectiveness of the feature deployment.

FullStory is a digital experience analytics platform that tracks how visitors interact with your website or app to optimize the customer experience.

The FullStory integration allows you to import your FullStory segments in Flagship so you can target them with Flagship use cases.

The FullStory pull integration will use the FullStory API to create of existing segments and import them into Flagship. So, you can see in the FullStory interface one data export for each segment. Segments are exported daily at 3 am, with the data from the day before. A user entering an audience at D/8 am or D/11 pm can be activated in Flagship at D+1/3 am.

This article will walk you through the different steps to setup the integration on FullStory side and to export your segments.

Get a FullStory API Key

The FullStory pull integration will use the FullStory API to pull segments and import them into Flagship. To use the FullStory API and access the segment, we need an API key.

To enable the integration on Fullstory, follow the steps below:

1. Access Settings > Integrations > API Keys

2. Click “Create key”

3. In the drawer that appeared, give a name to the API key you will create and give it the “Architect” permissions.

4. Click “Save API Key”.

For further information on FullStory API keys, please refer to the .

Enabling the Integration on Flagship

To enable the integration on Flagship, follow the steps below:

1. Access Settings > Integrations > Pull

2. In the dropdown, select FullStory.

3. Copy and paste the FullStory API key.

4. Click “Add tool” to finalize the integration.

The FullStory integration is now set up. This allows AB Tasty to pull the segments from FullStory.

For global information on how to retrieve audiences, please refer to .

Need additional information?

Submit your request at

Always happy to help!

Heap is a Product Analytics company that provides analytics infrastructure and helps its clients focus on discovering insights and taking action, rather than writing tracking code.

The Heap Analytics integration allows you to send the Feature Experimentation & Rollouts (FE&R, formerly Flagship) campaign data to your Heap Analytics project.

How to set up the integration

Troubleshooting

You can verify the hit in real time in Heap by navigating to Data → Live data feed, where your flagship The event should appear alongside other user actions.

📖 Definition

Sequential Testing Alerts offers a sensitivity threshold to detect underperforming variations early and trigger alerts or pause experiments. It enables you to make data-driven decisions swiftly and optimize user experiences effectively. Sequential Testing saves time and resources by stopping experiments that are unlikely to yield positive results.

⚙️ Configuration

To enable Sequential Testing alerts on an experiment, apply the following steps:

1. Access the AB Test configuration

2. At the bottom of the first step, the Main information step, click on the Advanced Options

3. You can then configure 2 options: \

   1. The type of automation You can either receive an email if your campaign is failing, a kind of “Warning, you’re experiment is going right into the wall” or directly pause the campaign if it’s failing.\

You can learn more about detection level on the .

Also, more information about Sequential Testing in the article

Good to know 💡

You can only configure this setup if you selected a Primary Goal at the previous step!

When doing experimentation or feature management on Flagship, you need to target the right users at the right time. For example, you may want to deploy a new feature to your early adopters only. However, you may have a list of over a hundred early adopters.

In the targeting step, you can target a list of values when creating or editing a use case. There are 3 ways of doing this:

• Manually adding the values of the users you want to target (Users by ID or Key) in the Values field. These values (ID, email, and so on) allow Flagship’s Decision API to identify the users you want to target among all your users.

• Copying and pasting the values of the users you want to target (Users by ID or Key) in the Values field and pressing ENTER. Each value must be separated by a comma.

• Importing the values related to the users you want to target in a CSV file by clicking on the Import CSV icon at the edge of the field. You must fill in the first column only, so that all the values are taken into account.

Need additional information?

Submit your request at

Always happy to help!

📖 Definition

Dynamic allocation (also called Multi-Arm bandit) is a method used to divert new traffic to the best performing variation depending on the results of each variation. It is based on the Thomson algorithm.

⚙️ Configuration\

If one variation is performing better than the others, that is to say, if one variation has more unique conversions on the KPI you configured, new traffic will progressively be sent to that variation. Dynamic allocation is only available for A/B Tests. Dynamic allocation only works for new users (for an application)/visitors (for a website). If a user is assigned to a variation and returns to the website, they will still see the same variation, even if this variation is under-performing. The allocation of a recurring visitor doesn’t change over time. Dynamic allocation only takes into account unique conversions

💡 Use case

The Dynamic Allocation algorithm is particularly suited to websites/applications with a lot of traffic. As soon as your A/B Test has at least one conversion for each variation on the selected KPI, the algorithm starts running and your users will progressively be redirected to the best performing variation.

Need additional information?

Submit your request at

Always happy to help!

📖 Definition

Archiving a use case enables you to get rid of obsolete use cases and keep your dashboard clean and up-to-date by viewing only the projects and use cases that you are currently working on.

⚙️ Configuration

This action can be performed by users with a User, Admin or Super admin role. To archive a use case, apply the following steps:

1. Hover over the use case you want to archive and click the 3 dots.

2. Click Archive.

3. Select the folder you want to move the use case to. If no folders are created, click New folder.

4. Click Archive: Your use case is archived.

Once a use case is archived, you can access it from the Archived tab of the dashboard. From there, you can organise your use cases by folders (instead of projects for the non-archived ones). This enables you to better organize your use cases once they are archived. For instance, you can store outperforming experiments in the same folder. You can still access the reporting of your archived use cases until the legal timeframe specified in your package.

Need additional information?

Submit your request at

Always happy to help!

📖 Definition

When performing the QA of your use case, you may want to verify that your hits have been set up correctly. For example, you may want to verify that the transactionId is the proper one, that the eventName is correct, and that the visitorId is properly taken into account in the reporting. The Hits stream feature enables you to carry out these checks.

⚙️ Configuration

To access the feature, click the Hits Stream tab from the Details or Reporting page of your use case. Click the Start recording button and wait a minute for the hits to appear.

You will see all the hits landing on your reporting. Hover over a hit type (left column) to verify its configuration.

⚙️ Use case

You are working on a new feature and just finished setting up the measurement part. You are trying to QA your feature to verify if the hits will be received correctly on your reporting. Without Hits Stream, you still benefit from the Real Time feature, enabling you to see the hits landing on your reporting. If you don’t see your hits, enable the Hits Stream recording, trigger your hits again and check their configuration. If you still don’t see them, you either made an error in the payload of the hits or forgot to activate the flags via the userExposed method of the new SDK versions (activate methods for the old ones).

Need additional information?

Submit your request at

Always happy to help!

If you are running several experiments at once on your site or application, a visitor will see each of them, which may influence the results, since one experiment can impact the results of another.

To avoid this, we offer an option that enables you to display only one experiment per visitor, even if there are several running.

To enable this option, click "Settings" in the menu, then select "Environment & Security" and under the "1 visitor 1 test" section, toggle the option "I want my users to be assigned only one experiment at a time" on.

• If you toggle the option on: a visitor cannot see more than one experiment.

• If you toggle the option off: a visitor can see more than one experiment.

This option only affects Experiments (A/B Test). All Personalization and Feature management scenarios will continue to work as expected.

Flagship November release notes 🦃

Flagship New Releases

📅 Scheduler :

Stressed out about forgetting you have an experiment to launch or busy with urgent business and not being able to launch the personalization you spent so much time on? What impact would it have on your business if you forgot about it while other stakeholders thought it was done? How much time and money would you lose by moving on to another task in a hurry to belatedly activate an experience or personalization?

Wouldn't it be great if you could agree with all stakeholders, set a date, and stop thinking about it to focus on other things? Flagship scheduler not only allows you to plan your experience or feature launch but also to be in sync with all your stakeholders and avoid any missteps of a GTM launch. Don't waste time or worry anymore about forgetting to toggle on a use case.

Try it now 🚀

Want to know more about it?

👉 Consult the

GA 4, Mixpanel, Segment, integration (Pull)

Unleash the Power of User Analytics with Our New Integrations with Google Analytics 4, Mixpanel, and Segment

Revolutionize your product development with these 3 new integrations. Understanding your users' behavior and product usage is crucial to making informed decisions about your product's evolution. But then you need to be able to leverage that data in your feature deployment process. Our integrations with these best-of-breed solutions allow you to unleash the power of user analytics in your targeting. Use your user behavior data for feature toggling, experiments, personalization, and progressive rollout scenarios to perform data-driven targeting that delivers real results. You'll also save time by automatically finding your integrations sorted in the drop-down menu. Take your product development to the next level with these powerful integrations.

Check the video below for an example of our Mixpanel integration: Want to know more?

👉 Check out 👉 Check out 👉 Check out\

🎉 December - Release Notes 🎉

Tracking manager

Give your app a boost in performance

Improve your app's performance with the Tracking Manager, a new feature available now on our JS, React and React Native SDKs that help improve performance and save bandwidth. You can reduce the number of requests between your application and our server by managing the hit sent in batches. Decide and control whether this is based on the number of hits or a period of time. This not only saves valuable bandwidth but also ensures that your application is working at its best, giving you a competitive advantage in today's fast-paced digital world.

More information here:

What's new?

A new name, and use cases closer to your needs

Say goodbye to Flagship!

AB Tasty presents AB Feature experimentation & Rollouts, the new brand identity for our offer around API based experimentations and SDKs.

Platforms are about to be merged for a seamless experience and much more cross-technologies use cases.

What doesn't change

AB Feature experimentation & Rollouts is the new commercial name for Flagship. &#xNAN;Flagship name is still used in our API and codebases and remains the basis for all our technical methods and functions. The technical documentation will continue to refer to Flagship as nothing changes from a technical and implementation points of view.

Tealium AudienceStream is a Customer Data Platform (CDP) that enables you to qualify the users who visit a website to create audience segments.

The Tealium AudienceStream integration allows you to import your FullStory audiences and badges in Flagship so you can target them with Flagship use cases.

The Tealium AudienceStream pull integration will use a webhook connector setup on Tealium’s end and the .

This article will walk you through the different steps to setup the integration.

💡Good to Know

You must be an AB Tasty customer for both client-side (AB Tasty WE&P) and server-side (FE&R formerly Flagship) features to activate the transaction reporting in your Feature Experimentation & Rollouts workspace (formerly Flagship). You will need your AB Tasty identifier (the ID of your tag) to complete the installation.

AB Tasty app administration

For more information on How to install the Shopify app though the Shopify app Store, please refer to article.

Once the app is installed, you can activate it by clicking on "Enable Extension".

Segment integration

Segment is a customer data platform (CDP) that helps you collect, clean, and control your customer data.

📖 Definition

The scheduler enables you to automatically toggle a use case ON (launch) or OFF (pause) at a specific date and time depending on your needs. Using the scheduler enables you to save time and to anticipate the activation or deactivation of a use case, particularly when you are located in a different timezone or outside of working hours.

📖 Definition

KPIs (or Key Performance Indicators) are metrics that enable you to measure the performance of an element or a variation through your end-user journey. You need to select a primary KPI, which will serve as a point of reference for the entire feature and enables you to determine the best-performing variation. You can also select one or several secondary KPIs, which are metrics that you want to track, but whose results don’t impact your feature as much. All the KPIs you configure can be tracked in the reporting of your feature.

📖 Definition

The rollback option enables you to stop the deployment of a feature and to revert all the changes that have been made in order to ensure that your feature isn’t breaking your customer experience, thereby damaging your business. For this, you must define the business KPI you want to track and which can be an indicator of the performance of your feature. To this KPI (of any type you want), you must associate a value (in %) which, if exceeded or reached, will trigger the rollback. To make the rollback significant, you must define a specific number of visitors from which the rollback comparison will be triggered. When the conditions are met, the progressive rollout feature will be rolled back, which means that no more of the targeted visitors will see the feature. You will be alerted by email.

📖 Definition

On your dashboard, you may have multiple projects or feature teams working on different projects. To avoid configuration mistakes, you can allow specific rights to specific users on each project.

⚙️ Configuration

📖 Definition

On the dashboard, you may need to run a search by project or use case. You can do so by using the search bar and associated filter at the top of the page.

⚙️ Configuration

The Chances to win is a statistical index which indicates the odds of a strictly positive gain on a variation compared to the original version. It is expressed as a % for any selected KPI.

This measurement is based on the number of conversions collected. The Chances to win enables you to determine the risk percentage (100% minus the Chance to win). It enables a fast result analysis for non-experts and simplifies the decision-making process.

Interpretation

The Chances to win indicator can take on values between 0% and 100%, rounded to the nearest hundredth and should be interpreted only if the business rules are complied with.

Flagship Release Notes July ☀️

Flagship New Releases

Flagship September Release note 🎒

Flagship New Releases

When running an experimentation on your users, you must wait until Flagship has collected enough significant data before analyzing the reporting of your campaign in order to get reliable insights.

Flagship’s reporting displays a statistical reliability index that enables you to know if your test is statistically reliable. We recommend reaching the ‘Reliable’ status before making any firm and definitive decision.

If this label is not displayed, it means that one or several of the rules mentioned above have not been complied with.

We also strongly recommend leaving a test active for at least the amount of time related to your business cycle. This time may be estimated at several days for classic e-commerce websites (browsing, verification, purchasing), but may take several weeks for less traditional websites (e.g.,: B2B activities, large purchases, etc.).

Not every test gives reliable results, and sometimes, you may have to pause some of them due to low statistical reliability, because the tested hypotheses have no impact on your conversion rate.

Decision API for non-techie users

First of all, if you're a tech guy, you might want to check out our to get access to extensive knowledge on how our Decision API works, but do feel free to read this article, which is shorter but still useful.

Why the Decision API?

Mixpanel is a product analytics platform that helps teams understand how users interact with their digital products. It tracks events, user behaviour, and retention in real time. With powerful segmentation and funnel tools, it supports data-driven decisions. You can find their getting-started guide and the official partnership page.

The Mixpanel integration allows you to target the cohorts created in Mixpanel with AB Tasty.

Once the integration is active on Flagship you need to activate the integration on Mixpanel.

This article will walk you through the different steps to setup the integration on Mixpanel side and to export your cohorts.

Enable the integration on Mixpanel

You must be a Mixpanel project Admin to enable the Flagship integration:

• Go to Integrations under the Data Management tab in the top navigation bar

• In the Integrations list, select Flagship, and click Connect

• To set up the Flagship integration you need to enter your account’s API Key. Copy paste the API Key of your Flagship account. Click “Continue”. ()

The AB Tasty integration will show a "Connected" tag once the connection is established.

Export the cohorts from Mixpanel to Flagship

Now that the connection between the tools is established, we have to export the desired cohorts to Flagship to target them.

• Click Cohorts under Users in the navigation bar.

• Select the cohort that you want to export. Click on the three-dot icon on the right side of the cohort.

• Click Export to Flagship. Select either one-time sync or dynamic sync. Click Start Sync.

Mixpanel Documentation on cohort exports is available .

Congratulations, the integration is now set up and you can target your Mixpanel cohorts with Flagship!

For information on how to use your cohort, please refer to .

For global information on how to retrieve audiences, please refer to .

Navigating the Flagship interface

Flagship is an all-in-One Feature Management & Product Experience Optimization Platform which enables Product and Technical teams to mitigate risks and ship faster. It includes four types of features:

- A/B test;

- Personnalisations;

- Feature flag;

- Progressive rollout.

Your features are implemented via a web platform, which can be accessed from any browser.

In order to access the Flagship interface, you will need a specific Flagship account.

Dashboard

Persona

September Release Notes 🎨

Archive & Move to

Time to clean up your dashboard

Organize your dashboard to focus on the projects you’re currently working on. We've introduced two new features: the archive option and the "move to" option. The former allows you to keep track of old use cases by archiving them and the latter allows you to re-organize a use case into another project.

Want to know more?

👉 Check out the

Use case overview update

To save your time and provide you with important information at a glance, we have added new details when you click on a use case, such as:

• The creation date

• The status of the use cases (draft/paused/launched)

• Scheduling, if activated

• The bucket associated (for those participating in the Early Adopter program)

SDK update: Flutter V2

Flutter V2 has been updated to make it compatible with Bucketing mode, Experience Continuity, and predefined keys. Want to know more?

👉 Check out the B

👉 Check out the

👉 Check out the

Early Adopter: Flag API Update

More simplicity to get Flag Data

A quick and easy way to retrieve data on your flags without having to go through the campaign endpoint. We've introduced the Route Flag, the new flag endpoint. Get data directly from flags without any additional development, reducing implementation time and complexity.

If you want to try it now, you can join our Early Adopter program.

Want to know more?

👉 Check out the

Interested in being an Early Adopter? Get in touch with your CSM or send us an email at [email protected]

Early Adopter: Remote Control API

Our Remote Control API makes your life easier. It allows you to control Flagship directly from your IDE:

• Create and manage flags from outside of Flagship.

• Directly query the corresponding Flagship environment to know which flags are already used in Flagship.

• Automatically duplicate your use case from the pre-prod environment to the production environment to avoid spending time duplicating actions in Flagship.

Want to know more?

👉 Check out the

Interested in being an Early Adopter? Get in touch with your CSM or send us an email at [email protected]

📖 Definition

An A/B test is a type of feature that enables you to test the performances of a new version of an element on your website or application. After analyzing the results of your test, you need to decide which version has performed best according to the KPIs you wanted to reach (e.g., the conversion rate). You can then apply these changes directly to your website/application.

⚙️ Configuration

To configure an A/B Test, apply the following steps:

1. From the dashboard, click Create a use case.

2. Select the AB Test template. &#xNAN;[Basic information]

3. Fill in the name of your AB Test and its description.

4. Choose the primary and secondary KPIs you want to follow.

💡 Use case

Let's say that on your e-commerce website, you have noticed that your users have trouble proceeding to checkout once their order is complete. You think this may be due to the color of the button and the wording "Proceed to checkout", which would not be suited. You have come up with 2 solutions but don't know which one would bring the highest conversion rate. In this case, you can create an A/B Test:

1. Create an AB Test use case on your Flagship account.

2. In the basic information step, select the KPI related to a click on the “Proceed to checkout” button. You need to have configured it in your codebase beforehand.

3. Select the conversion rate as a sub KPI type.

4. In the targeting step, select “All users”.

Need additional information?

Submit your request at

Always happy to help!

Flagship February release notes 🏂

New Developer Documentation

A change of look but not only!

We've reorganized the documentation, it's had a facelift but that's not all; it also includes examples of JS implementations and a new search function for all documentation.

And, because we like to hear feedback from our users, you can now share your comments and suggestions in the documentation. So get to your keyboards and let us know what you think!

Want to see it?

👉 Consult the

SDK Cache Management

Handling data cached on Android, Java, JS & React SDKs has never been so easy.

To improve the development experience, we have streamlined and optimized the Android, Java, JS & React SDK architecture and the way data is cached on SDKs. You can now customize the way the cache is managed. You (or your developers) can implement your own cache and tailor what it does or does not cache. A quick reminder on what the cache offers natively: Prevent user reassignment as the assignment is stored in the cache: a visitor will always be assigned to the same variation. Prevent data loss as the cache stores the hit and returns it later in case of an issue. Manage Offline moments. No connection, no worries, the SDK will take the last stored value.

Want to know more?

👉Check out the

👉Check out the

👉 Check out the

👉Check out the

SDK method updates: get Flags

Managing flags just got easier.

Making developers' lives easier is in our ADN. This is why we updated the Flag management and revamped the getModification, getModificationInfo, activateModification and synchronizeModification methods to make it easier to understand. From now on, the following method will be swapped:

• getModification() -> getFlag(“newRelease”).value()

• getModificationInfo() -> getFlag(“newRelease”).metadata()

• activateModification() -> getFlag(“newRelease”).userExposed()

• synchronizeModification() -> fetchFlags()

This redesign of the methods allows for easier implementation, more self-service and better accessibility of information ("all in one" method).

PHP SDK Update

PHP was updated to v2, and therefore is now compatible with experience continuity and Bucketing mode.

On Flagship, you can export your reporting data directly from the Reporting screen by clicking the Export button.

You must select at least one type of data you want to export among the following:

• Visitors

• Transactions

• Items

• Events

• Pageviews

• Screenviews

• User context

This list coincides with each type of hit that is sent from your website to Flagship. Once your export request is complete, you will receive the data by email in a CSV file. You will receive one CSV file per type of data requested.

Need additional information?

Submit your request at

Always happy to help!

📖 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.

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 .

Need additional information?

Submit your request at

Always happy to help!

📖 Definition

The targeting step enables you to make your feature visible to one or several groups of users with shared characteristics. To define your targeting, you can either configure feature targeting for:

• All users: target all the visitors landing on your feature.

• Users by ID: target the users belonging to a specific ID.

• Targeting by key: target the users matching a specific key.

Using the Decision API directly, or one of our SDK (in API or Bucketing mode), you can target your users via different criteria depending on the package you have subscribed to. These criteria are also called User Context keys and are useful to target users, but also to filter reporting of your feature when analyzing its results.

⚙️ Configuration

For targeting by key, you need to define a User Context key. To do so, you can either use an existing key, by selecting Key from the first dropdown list and its matching value in the Select a value field; or create a new key and define its value. To configure a new User Context key, click ‘Add a criterion’ and select Key in the first dropdown list and 'Add new' in the Select a value field.

There are two types of User Context keys:

• Technical keys (for example device, system, geolocation, version).

• Behavioral keys (for example VIP, Early Adopter, Buyer, Viewer, DefaultUser, age, name).

To send these criteria through one of our SDKs or our Decision API, refer to the .

💡 Use case

For example, you may need to deploy your feature progressively to different groups of users. Let’s say you want to test your feature internally first, then make it visible only to your early adopters and finally to all your users. To do so, you can first push a user context key that you would call “userType”:“internal”, then change it to “userType”:“earlyAdopter” and finally to “All users”.

Need additional information?

Submit your request at

Always happy to help!

Flagship Release Notes April 🐇

Hit Stream

Find out immediately if your tracking is working

Check in QA that your hits have been configured correctly before launching a use case. For example, you may want to double check if the transactionID, the eventName, or the visitorID are correctly reflected in the reporting. Make sure that any event sent is received, and check that everything is properly configured:

• Check all hits related to the use case

• Check all payloads related to the hits

• Check if your QA hits are received by confirming your visitorID

iOS SDK update

iOS SDK is now compatible with tvOS, watchOS & macOS!

This update allows you to manage features or experiment across smart devices that support tvOS, watchOS and macOS.

Cache management has been streamlined for the iOS SDK

To improve the development experience, we have streamlined and optimized the iOS SDK architecture and the way data is cached on SDKs. You can now customize the way the cache is managed. You (or your developers) can implement your own cache and tailor what it does or does not cache.

A quick reminder on what the cache offers natively:

• Prevent user reassignment as the assignment is stored in the cache: a visitor will always be assigned to the same variation.

• Prevent data loss as the cache stores the hit and returns it later in case of an issue.

• Manage Offline moments. No connection, no worries, the SDK will take the last stored value.

Managing flags just got easier in the iOS SDK

The methods have been redesigned for easier implementation, more self-service and better accessibility of information ("all in one" method). We have revamped the getModification, getModificationInfo, activateModification and synchronizeModification methods to make them easier to understand.

From now on, the following methods will be swapped: getModification() -> getFlag(“newRelease”).value() getModificationInfo() -> getFlag(“newRelease”).metadata() activateModification() -> getFlag(“newRelease”).userExposed() synchronizeModification() -> fetchFlags()

You might be convinced that Flagship, our feature management, and experimentation software, is only compatible with companies that have an infrastructure built exclusively with integrated SDKs such as Android, IOS, NodeJS & JS, React, etc. But you can, in fact, use Flagship even if your SDK stack is not available, thanks to our decision API.

📝 Explanation

To illustrate, an SDK can be compared to a library that you will download onto your codebase to use pre-made functions. The Flagship SDKs are made of pre-coded methods that will facilitate the communication of your code base with our decisional API. this is the control center of Flagship, which in a way will allow you to perform your experiments and feature management.

If the SDK you are looking for is not available, you can easily implement Flagship in your codebase with a simple HTTPS request to the Decision API.

To find out how to successfully communicate with our Decision API, please refer to the .

Need additional information?

Submit your request at

Always happy to help!

🦃 November - Release Notes

Flag Management Dashboard evolution

Creating and managing your flags just got easier!

Easily view and manage all your flags at once with the redesign of the Flag Management Dashboard! We improved it to save you time, especially when setting up multiple flags. You can now create and sync your flags directly from the page while having immediate visibility on the list of existing flags to ensure a name isn't already taken and you're sticking to naming conventions. To help you better manage your flags, we've also improved the layout, added a new search function, and introduced filters. Finally, for better team collaboration, users can now add comments and details in flags to provide additional information, and we’ve added logs so you can see who created a flag and when.

Want to know more?

👉 Check out

Remote Control API

Control Flagship from your own stack!

Switching between multiple platforms can be time-consuming, lead to errors, and interrupt focus. Because we aim to make your lives easier, we are excited to introduce our new Remote Control API! This new feature will allow you to leverage your existing stack and develop your own set of tools for how you want to use Flagship:

• You can now perform all Flagship tasks directly with API calls, including managing your projects, use cases, variations, variation groups, users, targeting keys, and your flags.

• As an administrator, you will also be able to manage the different scopes to which a user has access.

• We have also developed a CLI to help you use the Remote Control API directly on a terminal.

Want to know more?

👉 Check out

👉 Check out the

Flag API update

More simplicity to get Flag Data

A quick and easy way to retrieve data on your flags without having to go through the campaign endpoint. We've updated the FLag API with a new flag endpoint. Get data directly from flags without any additional development, reducing implementation time and complexity.

Want to know more?

👉 Check out the

📖 Definition

When performing an AB Test and after analyzing its results, you need to decide which version has performed best according to the KPIs you wanted to reach (e.g., the conversion rate). You can then apply these changes directly to your website/application.

Applying these changes can be done by duplicating the winning variation to a Feature Toggle.

⚙️ Configuration

To duplicate a winning variation to a Feature Toggle, apply the following steps:

1. From the dashboard or the report interface, click on the Duplicate button.

2. Select the destination type for the duplication -- the default type is selected by default, so here you'll need to select To Toggle option.

3. Verify that all the fields are correctly set:

When everything is clear for you, click on Use this configuration.

❓Need additional information?

Submit your request at

Always happy to help!

Flagship October Release Notes 🎃

Flagship New Releases

📁Multiple Environnements :

To optimize the product life cycle, the development team must be able to work not only on a pre-prod or prod environment but also on Staging, RC, or any other environment where they may need to minimize bugs, facilitate testing and accelerate the team's development capacity. The ability to quickly create a local environment gives the developer the flexibility to work safely on a feature without impacting the work of the rest of the team.

This is why we are excited to introduce the Multi-environment manager, allowing you to create any environment you need in just 3 clicks.

Want to know more about it?

👉 Consult the

✔️ User Consent SDK

To be GDPR compliant or simply to meet your users' preferences, you may need to get their consent to collect data before exposing them to an experiment, personalization or for feature management. To that end, we have released the User Consent parameter for SDKs to disable data collection if your users have not consented to the experiment/personalization/data collection.

This method will not prevent you from displaying changes to your users, it will simply block data collection. This means that you will still be able to use Flagship, even if visitors have not consented to data collection, to manage KillSwitches, Release Toggles, and Permission Toggles.

The user consent parameter is available for the following SDKs:

• Android

• iOS

• Java

• Flutter

Flagship August Release Notes 🐬

Flagship New Releases

💾 Data export - User Context Key

We previously released the ability to export data from our reports, which was a key milestone to ensuring our customers could view all the hits and visitor IDs in any other system within their TechStack. Now the goal is making sure to continue adding the most valuable data to this report extract and are happy to announce the user context data has been added to the list of available data that can be extracted. The Flagship users have consistently remarked on the value of filtering the Flagship reports based on the user context key (for example user device, geolocation, is a beta user, etc.) to perform analysis so it only made sense that made this data available to be easily extracted.

Want to know more about it?

👉 Consult

🔗Flutter SDK

Flagship is further expanding its collection of available SDKs. We have added compatibility for Flutter SDK.

✨ Dashboard Improvements

Number of use cases activated

We've reworked the Flagship dashboard at the project and use case level. Now, when you see the list of your projects, you can see at a glance the number of use cases that are activated in your environment:

Date format improvement

The display of the activation or deactivation date of a use case has also been made universal:

Delete use case option

And finally, it is now possible to delete a use case directly from the dashboard by using the three small vertical dots present when you hover over it:

Multi-factor authentication is a two-step process for verifying the identity of people who log in to the platform and enables you to secure your account. You can restrict the use of your account by other users by enabling one or both of the 2FA (two-factor authentication) methods. In this case, the users will only be able to access your account using the MFA method you enabled. The Super admin is the only role who can enable MFA on an account.

⚙️ Configuration

To secure your environment, that is to say to compel users to log into your account with the MFA, you can enable one of the two following options:

• The 2FA method by SMS: via a verification code sent in a text message.

• The 2FA method by Application (Google Authenticator, 1password, Authy, and so on): via a verification code sent in an application.

When you enable one 2FA method, users will have to configure the corresponding 2FA in their profile to be able to connect to your account. If they don’t have a 2FA method configured, they will be asked to do so when accessing your account. Otherwise, they won’t be able to log into your account. You can also enable both methods (2FA by SMS and 2FA by Application). In this case, users will be able to access your account if they have configured at least one of the two methods.

For more information, refer to .

Need additional information?

Submit your request at

Always happy to help!

📖 Definition

The Integrations page enables you to create and manage integrations with the third-party tools (DMPs, CDPs, etc.) available on your Flagship account. From there, you can activate integrations in order to retrieve all the audiences you have configured in your third-party tools. You will then be able to use them as targeting keys in the Targeting configuration step and as filters in the reporting of your use cases. To access the integration page, go to Settings > Integrations. It is divided into 3 main sections:

📖 Definition

A Flag (more commonly known as Feature Flagging) is a technique that enables you to remotely modify any system behavior without changing its code. It can be seen as a dynamic variable allowing you to change values at any time. In Flagship, you can configure and manage your Flags.

⚙️ Configuration

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.

Multi-factor authentication is a two-step process for verifying the identity of people who log in to the platform and enables you to secure your profile and account.

⚙️ Configuration

To secure your profile, you can use one of the two following options:

• The 2FA method by SMS: via a verification code sent in a text message.

• The 2FA method by Application (Google Authenticator, 1password, Authy, and so on): via a verification code sent in an application.

Once multi-factor authentication is enabled on your profile, you will be asked to provide your email address and password, as well as a verification code sent via text message (if you enabled 2FA by SMS) or via an application (2FA by Application).\

📖 Definition

The Remote Control API enables you to create credentials with specific rights to let you carry out actions on your account outside of Flagship. This way, you will be able to control your account without having to log in to Flagship.

To access the Remote Control API page, go to Settings > Integration > Remote Control API. It is divided into 2 main sections:

👉 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

Flagship Release Notes: Fall

General Availability

📖 Definition

A Feature Toggle/Flag lets you enable or disable a feature or a group of features depending on a specific audience. It allows you to easily and safely release your features.

⚙️ Configuration

Flagship January release notes 🎉

Flagship New Releases

⚙️Flag configuration:

One unified workflow to rule them all.

To further provide the best user experience in Flagship and maintain consistency, we have improved, streamlined but most importantly unified the flag configuration workflow across all use cases.

Since we care about all users and know that some prefer to configure a flag with a JSON format and others prefer to fill in the name, type and value of their flags, we have created 2 configuration modes: standard and expert so that everyone can follow their preferred path.

Want to know more about it?

👉 Consult the

👉 Consult the

👉 Consult the

👉 Consult the

✅ Status Page and Speed Page release:

More trust and transparency

Have you ever had any doubts that some of the problems might have come from Flagship? With the new Status page you can find out if there is an issue with Flagship by visiting . There you will find all information about Flagship services and the product maintenance we are working on. Do you want to know more about the response time of the decision API? You can check out . You will get an overview of the overall response time in different regions.

🚀Improvement of the platform's performance:

Full speed ahead!

You may have experienced some performance issues in early December on Flagship. Since providing the best performance to our users is one of our top priorities, we quickly identified the reason (too many database calls) and worked on a solution.

Not only were we able to solve this problem by implementing a new Redis cache management system, but we also improved the overall performance of the platform.

Here are the improvements we made:

• We made each API call 30% lighter.

• We made the communication with the database smoother,

• We lightened the impact on the CPUs

• And we implemented a Read Replica so that the queries made by our background processes (CRONs) do not increase the load on the production database.

Feature in the previous release that you may have missed

📅 Scheduler:

Stop worrying that you forget to launch an experiment or a personalization.

Stressed out about forgetting you have an experiment to launch or busy with urgent business and not being able to launch the personalization you spent so much time on? What impact would it have on your business if you forgot about it while other stakeholders thought it was done? How much time and money would you lose by moving on to another task in a hurry to belatedly activate an experience or personalization?

Wouldn't it be great if you could agree with all stakeholders, set a date, and stop thinking about it to focus on other things? Flagship scheduler not only allows you to plan your experience or feature launch but also to be in sync with all your stakeholders and avoid any missteps of a GTM launch. Don't waste time or worry anymore about forgetting to toggle on a use case.

Try it now 🚀

Want to know more about it?

👉 Consult the

The Webhooks page is an overview of all the webhooks you have configured on your Flagship account. This page enables you to trigger alerts depending on the type of actions performed on your account.

📖 Definition

A Webhook is a way for applications/software to send alerts to third-party applications in real time when an event happens. It is configured to send push notifications to a URL (Hook URL) designated by the tier interested in the event. Each event triggering the Webhook URL will have specific parameters (such as the name of the event) and common ones (such as the date and time). For more information on webhooks, refer to the developer portal.

⚙️ Configuration

To access the Webhooks page, go to Settings > Platform Integration > Webhooks tab.

To create a webhook, apply the following steps:

1. Click Create.

2. Choose the event you want to be alerted on.

3. Insert the webhook URL which should receive the alerts.

4. Insert a short description to remember what this webhook is for.