> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/feature-experimentation-and-rollout/sdk-and-environments/managing-environments/experience-continuity.md).
# 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
{% stepper %}
{% step %}
#### Enable Experience Continuity
Navigate to **Settings → Feature Experimentation →** [**Environment Settings**](https://app2.abtasty.com/settings/feature-experimentation/environment)**.** \
Enable Experience Continuity.
This applies to all Feature Experimentation campaigns running in the selected environment.
{% endstep %}
{% step %}
#### Implement Visitor ID reconciliation
Implement Visitor ID reconciliation in your code using the SDK or Decision API workflow. **Technical documentation:**
{% endstep %}
{% endstepper %}
{% hint style="warning" %}
**Reporting Impact**
Enabling Experience Continuity on running experiments may affect report results.
{% 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.
* **Cross-device experience**: same variation on all devices after sign-in.
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
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.abtasty.com/feature-experimentation-and-rollout/sdk-and-environments/managing-environments/experience-continuity.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
