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
  • ๐Ÿ”Ž Behavior
  • Cross-Session Experience
  • Cross-Device Experience
  • โš™๏ธConfiguration

Was this helpful?

Edit on GitLab
Export as PDF
  1. API keys & Settings

Using Experience Continuity

PreviousActing on your account remotelyNextvisitor experiment option

Last updated 2 days ago

Was this helpful?

Experience Continuity is a feature that enables your users to keep the same experience across devices and sessions. When a user changes device or signs into their account, Flagship is able to retrieve their visitorID and to assign them the same variation so that their experience on the website is the same.

๐Ÿšฉ Heads up

This feature is compatible with the Decision API V2 only. If you use bucketing and want to benefit from this feature, please contact us.

๐Ÿ”Ž Behavior

Experience Continuity enables you to provide your users with a Cross-Session and a Cross-Device experience.

Cross-Session Experience

This feature guarantees continuity between your users' sessions. That is to say that your users will see the same variation across their different sessions on your website. For example, letโ€™s say a user visits your website for the first time as an anonymous (without being logged into your website), they are automatically assigned to a variationID corresponding to a variation (variation 1 of your test, for example). Then, they log into your website on the same browser. With the Experience Continuity enabled, Flagship is able to assign the user the same visitorID and thus, they see the same variation (variation 1). Their experience on your website wonโ€™t be affected by the different sessions. Without the Experience continuity feature, the user may see the same variation or another one.

Cross-Device Experience

This feature enables your users to ensure a Cross-Device Experience, meaning that they will have the exact same experience when browsing on two (or more) different devices. For example, letโ€™s take the exact same user as in the previous example. They log in on a desktop device > assigned to a variationID corresponding to a variation (variation 1 for example). A few minutes later, they log in on their mobile phone. Flagship understands that this visitorID has already seen a variation and the user will be assigned the same variation (variation 1). Their experience on your website wonโ€™t be affected by the device change. Based on those two behaviors, a same user browsing on two different devices will be counted as a unique user in our report, and all the conversions they make will be linked to this specific user. Based on the above diagram, the results in the reporting of your feature will be the following:

In unique visitors:

Variation 1

Variation 2

๐Ÿ‘ค Visitors

1

1

๐Ÿ“ˆ Conversions

1

1

๐Ÿ’ต Transactions

1

0

In multiple sessions:

Variation 1

Variation 2

๐Ÿ”’ Sessions

3

1

๐Ÿ“ˆ Conversions

3

1

๐Ÿ’ต Transactions

2

0

โš™๏ธConfiguration

To enable the Experience Continuity feature, apply the following steps:

  1. Integrate the visitor_id reconciliation into the code of your website following our new SDK method or Decision API workflow. See the tech documentation

๐Ÿšฉ Heads up

Enabling this feature when an Experiment is running may affect the results of your report.

Need additional information?

Submit your request at product.feedback@abtasty.com

Always happy to help!

Go to your environment settings and toggle the feature ON.

๐Ÿ‘‰