> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/changelog/updates-for-september-2023/september-11-2023.md). # September 11, 2023 New Features After summer holidays, it's time to get back to improving the product and bringing new updates for our customers. Let's dive in! * **Reconcile all Demo Sessions for the Same Lead:** If you've the same lead on your website viewing multiple demos that are behind a lead form, Storylane analytics will now reconcile all the sessions data of that particular lead. \ \ For example, you've two (or more) demos on your website and both of them have a lead form. A visitor fills in the form for the first demo and goes through it. Then when the visitor goes to the second demo, the lead form (even though active) won't show up for them as they've already been identified by Storylane. Now, when you go to the analytics, it'll show two separate sessions for the visitor (now lead) for each of the demo, with the same email id.
* **Widget drag/ drop for HTML Demos:** We're finally bringing the widget drag/ drop feature to HTML demos as well (previously only available in screenshot demos). After adding a widget, you'd now be able to drag it to any other HTML element, anywhere on the same screen.
\ **Note:** The drag/ drop is only for Hotspot and Tooltip widgets. The modals (including the lead form) are always centrally aligned. --- # 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.storylane.io/changelog/updates-for-september-2023/september-11-2023.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.