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
  • Selecting an existing KPI
  • Creating a KPI
  • ๐Ÿ’ก Use case

Was this helpful?

Edit on GitLab
Export as PDF
  1. Steps configuration

Configuring KPIs

๐Ÿ“– 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.

โš™๏ธ Configuration

You can either select an existing KPI or create one if it doesnโ€™t exist, among the 4 types of KPIs available: - Transaction - Event - Pageview (on Web/Server) - Screenview (on APP/Server)

โญ Good to know

For Screenview and Pageview KPIs, the reporting displays the access rate of a page (Pageview) or screen (Screenview).

Selecting an existing KPI

You can select a KPI you have previously sent to the data collection.

To do so, select the type of KPI from the first drop-down list and directly select the existing KPI in the โ€˜Existingโ€™ field or enter the first letters of the KPI.

Creating a KPI

You can also create a KPI from scratch, i.e. a KPI you havenโ€™t sent to the data collection beforehand.

To do so, select the type of KPI from the first drop-down list and enter the name you want to give your KPI in the Add new field. Click + and choose a sub-KPI.

Next, when coding an Event or Transaction KPI, you must enter the exact same name as the one you created manually in Flagship.

๐Ÿšฉ Heads up

๐Ÿ’ก Use case

For example, letโ€™s say you are running an experimentation to test two different algorithms on the search feature of your website.

You may want to track the access rate to the product page as a primary KPI as well as the number of clicks on the Add to cart CTA as a secondary KPI.

To do so, apply the following steps:

  1. In the Choose metrics to follow section of the Basic information step, select Pageview from the first drop-down list.

  2. Enter Access rate as a name for the KPI, select is regular expression from the operators list and enter a value (for example: .*\/product\/[a-z0-9]{5}.html).

  3. In the secondary KPI section, select Event from the first drop-down list and enter Clicks on Add to cart as a new KPI.

  4. Select Conversion rate as a sub-KPI.

Need additional information?

Submit your request at product.feedback@abtasty.com

Always happy to help!

Previous[Troubleshooting] How to target a large number of users at the same time?NextUsing the automatic rollback option

Last updated 2 days ago

Was this helpful?

We recommend implementing the analytics part of Flagship as described in the (following your integration type (SDK/API)) before the KPI(s) of your feature.

All conversions displayed in the reporting were made after being assigned to a flag. To be assigned to a flag, follow the activation part of the / you are currently using.

๐Ÿ‘‰
developer documentation
Decision API
SDK