> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/hablla/settings/connections-and-integrations/webchat/how-to-find-the-id-generated-by-webchat-in-the-browser.md).
# How to find the ID generated by Webchat in the browser
Find the ID generated by Webchat in the browser's Local Storage and understand how it keeps conversations persistent and recognizes the user.
If your webchat search mode setting is automatic, you can check the **ID** generated by Webchat using the **developer tools.** After opening the Developer Tools window, you can navigate to the tab where the data from the **Local Storage** of your browser is stored to access the ID generated by your Webchat.
\
If you use the browser **Google Chrome**, you can access Local Storage through this path:
1. Press F12 on your webchat test screen
2. Find in the top menu and click on the tab **Application**.
3. Access the option in the left side menu **Local Storage**.
#### Conversation Persistence
It is through this ID generated by Webchat that the persistence of your user's conversations (the lead or customer who contacts you) is maintained. As long as the ID is saved in the user's browser Local Storage, it will always be recognized.
If the ID is updated or removed, the system will create a new identifier for this user and a **new person** may be created.
---
# 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.hablla.com/hablla-docs-en/hablla/settings/connections-and-integrations/webchat/how-to-find-the-id-generated-by-webchat-in-the-browser.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.
