> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/changelog/2026/improvements-and-fixes-september-2026.md). # Improvements and fixes, September 2026 Improvements and bug fixes released in September 2026. *30 September 2026* ## Improved * **Portal:** Added a "does not start with" operator for text conditions in the Targeting builder. * **Portal:** Added a download option to all HEART 2.0 charts, so you can export the data behind each chart as you could in HEART 1.0. * **Portal:** Added a choice of time window to Goals: track a metric since the Goal's start date, or over a rolling 30-day window. * **Portal:** Updated the Goal outcome list and the metrics linked to each outcome, making it easier to choose the right metric when creating a Goal. * **Portal:** Reorganized parts of the Portal navigation: Application attributes now sit under Settings, Content Analytics sits under Intelligence, and Announcement analytics are back in Content Analytics. * **Portal:** Added an Open Editor button to the Portal navigation. * **Portal:** Updated terminology in Surveys: "Choose your audience" is now "Targeting", and the "Surveys" tab is now "Standard". * **Portal:** Improved the HEART AI insights so the overview card always shows a clear message, including when a score has not changed or there is not enough data yet. * **Portal:** Updated the help links and in-product Guides across the Portal so they open the latest documentation. * **Portal:** Updated the list of application categories in property settings. * **Editor:** Updated terminology in the Editor to match the Portal: Segmentation is now Targeting, User segments are now Audiences, and Page segments are now Page Rules. * **Editor:** Made an improvement so that the Editor stays usable while your application shows a modal dialog. * **Editor:** Updated the Guide and Tooltip editors to use tabs instead of expandable sections, matching the Validator editor. * **Editor:** Added the option to select multiple Guides as Actions in a single Contextual Action. * **Editor:** Improved naming in Contextual Actions: element contexts are now named after the element automatically, and names you set manually are no longer overwritten. * **Editor:** Updated links from the Editor to the Portal to match the new Portal navigation. * **Assistant:** Made an improvement so that Tooltips and Validators shown by a Contextual Action now hide when the context no longer applies and reappear when it applies again. * **Other:** Added HEART 2.0 data to the public data export API. ## Fixed * **Portal:** Fixed an issue where analytics did not include events from the last hour of each day. * **Portal:** Fixed an issue where adding a segment filter to HEART metrics switched the view to a different property for users with access to several properties. * **Portal:** Fixed an issue where some HEART 2.0 pages failed to load for properties with large amounts of data. * **Portal:** Fixed multiple issues in HEART 2.0: the Adoption card now applies segment filters to license utilization, Task Success values are rounded, deleted Tasks no longer count toward Efficiency, and metric messages and links are consistent. * **Portal:** Fixed several display issues in HEART 2.0 and Goals, including misaligned score gauges, extra decimal places, and inconsistent icons. * **Portal:** Fixed an issue where Managers could not view CSAT analytics. * **Portal:** Fixed multiple issues in Surveys: the User ID link in survey responses opened a Not found page, the Create Survey button did not offer NPS, and deleting a survey opened its analytics page. * **Portal:** Fixed multiple issues after the navigation update, including broken links on the deployment landing page and the file transfer page, and an unnecessary horizontal scroll bar. * **Portal:** Fixed an issue where Claude was not classified as an AI application in App Discovery. * **Editor:** Fixed an issue where recording a Guide created two steps for a single click. * **Editor:** Fixed an issue where testing a Task in the Editor did not recognize text typed into certain input fields. * **Editor:** Fixed an issue where Editor text fields, such as the Validator AI prompt, could not be typed in on some applications while recording or previewing. * **Editor:** Fixed an issue where the Add Guide and step pickers in the Tooltip settings were cut off and could not be searched or scrolled. * **Editor:** Fixed multiple issues in the Contextual Action builder: Validators showed as "\[deleted]", unpublished Messages could not be added as Actions, and context search, drag and drop, and firing of multiple Contextual Actions did not work as expected. * **Editor:** Fixed several display issues in the Editor, including incorrect icon colors, dropdowns that looked disabled, and long labels overflowing. * **Assistant:** Fixed an issue where Guide steps that rely on a click could not find their target element in Firefox. * **Assistant:** Fixed an issue where certain Page Rule conditions prevented Announcements from being shown. * **Assistant:** Fixed an issue where a Validator linked to a Contextual Action was shown even when the Contextual Action's context was not present. * **Assistant:** Fixed an issue where the AI Assistant returned no knowledge base results for properties created after the knowledge base integration was set up. * **Other:** Fixed multiple backend stability and performance issues, including slower loading of content for end users, errors when removing a language from a property, and errors when copying content. --- # 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.userlane.com/changelog/2026/improvements-and-fixes-september-2026.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.