# Using Experience Continuity

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.

| <p>🚩 Heads up</p><p>This feature is compatible with the Decision API V2 only. If you use bucketing and want to benefit from this feature, please contact us.</p> |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |

##

## 🔎 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.\
![Experience\_continuity.png](/files/Tj9IqIMIdTZ2cqLR0Qgc)\
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. Go to your *environment settings* and toggle the feature ON.\
   ![Enable\_exp\_continuity.png](/files/VFxazNfJ4HqCUpm39BBS)\\
2. Integrate the visitor\_id reconciliation into the code of your website following our new SDK method or Decision API workflow. [See the tech documentation](https://developers.flagship.io/docs/concepts/experience-continuity)

| <p>🚩 Heads up</p><p>Enabling this feature when an Experiment is running may affect the results of your report.</p> |
| ------------------------------------------------------------------------------------------------------------------- |

##

**Need additional information?**

Submit your request at <product.feedback@abtasty.com>

Always happy to help!


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.abtasty.com/flagship-deprecated/api-keys-and-settings/using-experience-continuity.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.