> 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/account/performance-and-security/how-to-manage-visitor-identity.md). # How to manage visitor identity The [Visitor Identity Management](https://app2.abtasty.com/settings/tracking/visitor-id-management) page allows you to choose how you want to manage the visitor ID. The options are: * Use AB Tasty’s visitor ID management system * Manage the visitor ID on your side (BYOID) ## Bring your own ID (BYOID) settings The Bring your own ID (BYOID) option allows you to manage the visitor ID yourself instead of using AB Tasty visitors ID management system. When you activate BYOID, you will be responsible for generating the visitor ID, storing the visitor ID in a first-party cookie, a JavaScript variable, or local storage, and retrieving the visitor ID from the storage location. You will also be responsible for sharing the visitor ID with AB Tasty so that AB Tasty can track the visitor’s behavior on the website and personalize the website for the visitor. To activate BYOID, select **Manage the visitor ID on your side (BYOID)**

| **NOTE** | Note that as soon as you have saved this setting and refreshed your tag, you will be responsible for sharing the ID everywhere the tag has been implemented. The failure to provide this ID will make the tag unable to execute, display the campaigns and collect data. | | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | Once activated, you can select the three options to manage the visitor ID: - Cookie - JavaScript variable - Local storage | **NOTE** | To make sure the visitor IDs we will collect do not include personal information on your visitors, the AB Tasty tag will automatically hash them before using and collecting them. As a result, the visitor IDs you store will be different from the one AB Tasty collects. | | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ### Cookie You can select this option if you decided to store the visitor IDs in a cookie. In this case, set the cookie name and a pattern to extract the ID from the cookie.\ Note that you must create the cookie beforehand.

### JavaScript variable You can select this option if you decided to store the visitor IDs in a JavaScript variable. In this case, specify the JavaScript variable name which contains the ID.

### Local storage You can select this option if you decided to store the visitor IDs in the local storage. In this case, specify the local storage variable name and pattern to extract the ID from the local storage.

## Migration mode The migration mode allows you to either use the existing visitor ID until AB Tasty’s cookie expires or immediately switch from AB Tasty’s visitor ID management system to your own ID management. * Select **Toggle ON** to keep the existing visitor ID until AB Tasty’s cookie expire. * Select **Toggle OFF** to switch to delete all existing visitor ID and switch to BYOID immediately. | **NOTE** | You can configure your own cookie expiration date from the **Cookie lifespan** section of the [Cookie settings](https://app2.abtasty.com/settings/cookies-privacy/cookies) page. By default, it is set to 13 months. | | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

We recommend using **toggle off** to start a fresh visitor ID tracking. --- # 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/account/performance-and-security/how-to-manage-visitor-identity.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.