# Experience Continuity

**Experience Continuity** maintains consistent user experiences across sessions and devices.

When users switch devices or sign-in, Feature Experimentation and Rollout reconciles visitor IDs to ensure they receive the same variation every time.  

{% hint style="info" %}
**Decision API only**

Experience Continuity is available with **Decision API V2** only. If you're using bucketing-based implementation and want to enable this feature, please contact us.
{% endhint %}

### Experience Continuity configuration 

<figure><img src="/files/KzSGO6tWcjKFRQRsl1Gd" alt=""><figcaption></figcaption></figure>

{% stepper %}
{% step %}

#### Enable Experience Continuity

Navigate to **Settings → Feature Experimentation →** [**Environment Settings**](https://app2.abtasty.com/settings/feature-experimentation/environment)**.** \
Enable Experience Continuity.&#x20;

This applies to all Feature Experimentation campaigns running in the selected environment.
{% endstep %}

{% step %}

#### Implement Visitor ID reconciliation&#x20;

Implement Visitor ID reconciliation in your code using the SDK or Decision API workflow. **Technical documentation:** <https://developers.flagship.io/docs/concepts/experience-continuity>
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Reporting Impact**

Enabling Experience Continuity on running experiments may affect report results.&#x20;
{% endhint %}

### Cross-session & cross-device behavior

Enabling Experience Continuity ensures users see the **same variation across sessions and devices** when their visitor ID is reconciled.

* **Cross-session experience**:  same variation across multiple sessions.&#x20;
* **Cross-device experience**: same variation on all devices after sign-in.&#x20;

As a result:

* Users browsing across multiple sessions or devices count as **one unique visitor** in reports
* All conversions are attributed to this unique visitor

Without Experience Continuity enabled, users may be reassigned to a different variation when starting a new session or switching devices.


---

# 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/feature-experimentation-and-rollout/sdk-and-environments/managing-environments/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.