2FA |
Two-step process for verifying the identity of people who log into the platform and for securing your profile. |
A/B Test / Experiment |
Type of use case that lets you test a simple or complex hypothesis. Users are subjected to one of several alternative versions of a page, element, or workflow in order to identify the best-performing variation. |
Automatic rollback | Option that 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, and therefore your business and conversion rate. |
Backup codes | Codes generated after enabling a 2FA method that you can store in a safe location in case you forget or lose your phone. |
Boolean |
Type of variable with a value of either true or false. |
Chance to win | Likelyhood of winning more if you put the variation into production. Calculation is based on the Bayesian confidence interval of the uplift. |
Conversion rate | Number of visitors that reach a desired goal (a conversion) out of the total number of visitors. |
Custom ID | Unique value that lets you request the flags of a specific use case. |
Dashboard | Overview of your projects and all the use cases (features, experimentations) that you are currently managing. |
Decision API |
Managed REST API which allows your developers to communicate with our Flagship product. It will return flags and the associated values that you want to display to your users. |
Deployment | Step that enables you to plan your progressive rollout by configuring each due date and percentage of traffic that will see your feature. |
Dynamic allocation |
Option that automatically sends more traffic towards the best-performing variation based on a specific KPI (e.g. conversion rate, transaction rate, etc.). |
Dynamic variable (or Remote variable) | Container for some code (Feature flag, Toggle, CSS, Text, any values, etc.). |
Environment ID | Identifier of your current environment (prod/preprod). It must be sent when you are communicating with the Decision API/SDKs. |
Feature Flag |
Remote variable / Dynamic variable you can play with remotely. From the Flagship platform, you can play with all the flags wrapping your feature. |
Feature Toggle | Feature flag containing additional string or integer parameters (ON with quota of 500; ON with version number 2.1; etc.). |
Feature |
New functionality within a product to be deployed to users. |
Feature management | Method used by development teams to deliver faster and take on more development cycles. It allows engineering teams to continuously deploy code and empowers business teams with control over features so they can manage their customer’s experience. |
Feature toggle | Synonym of Feature Flag. |
Flag Key | Variable present on your code that you want to act on with a specific value (Boolean, integer, string). |
KPI | Key Performance Indicator, which will prove that your team brings ROI to your company. |
MFA Method | Multi-factor authentication that allows you to protect your account. |
Panic mode | Button in the settings that enables you to disable every live feature of your account, especially if you are dealing with a major issue. |
Persona | Typology of users you want to address. |
Personalization | Type of feature which enables you to modify the content of your website or application, either for the entire traffic or for a specific audience. |
Primary KPI | KPI that serves as a point of reference for the entire use case to determine whether your use case is effective or not. |
Progressive Rollout (or Progressive Deployment) | Feature that enables you to assign your users to your new feature step by step, with a Rollback KPI. |
Projects | Series of features that you need to experiment and manage to reach a specific outcome. |
Report | Analysis interface available for each feature, which presents the visits, actions, and behavior of visitors allocated to the feature. Each report includes a list of KPIs and indicators which enable you to determine the winning version of a test or the performance of a feature. |
Rollback | Action carried out to completely disable the feature and return to the previous behavior of your website/application. |
Rollback KPI | Metric you want to track in case your new feature negatively impacts your main objective. |
Scenarios |
Step that enables you to set your targeting users and your personalization/feature configuration. |
SDK (Software Development Kit) | Easy way to develop in a specific language. This helps you save time as all the functions you need are pre-coded. |
Secondary KPI | KPI which will probably and indirectly be impacted by your use case. |
Standard allocation | Option that allows you to manually manage your user allocation on each variation of your feature. |
Summary | Last step of each created use case that allows you to get an overview of your experimentation information. |
Targeting | Feature configuration step. Enables you to specify the different targeting criteria of the audience which the modifications shall apply to. |
Targeting key | Variable whose value can be used as a targeting criterion. |
Uplift | Improvement made in comparison to the reference variation with the Bayesian interval. |
Use case | Template applied to a feature (i.e.: an experiment use case applied to an algorithm feature). |
User context | Context that you get from your user, shared to Flagship. It allows you to set different types of users (VIP, New, mobile user, etc.) which will increase the effectiveness of your feature management. Used for targeting keys and reporting filters. |
User ID | Unique user ID (defined by you) that you send to the platform via the Decision API/SDKs. |
Variation | Variant of the original version of your experimentation feature. The effectiveness of the variation is measured in relation to the original version, based on previously selected and configured KPIs. |