> 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/2024/improvements-and-fixes-august-2024.md).

# Improvements and fixes, August 2024

Improvements and bug fixes released in August 2024.

*31 August 2024*

## Improved

* **Portal:** Added Tooltips and Tags to the usage section of Segments for a complete overview of where segments are being used.
* **Portal:** Added an end date error to Messages when the end date is configured sooner than the start date.
* **Portal:** For customers who do not wish to show user-identifiable information: removed "time spent per page" (Engagement) and "pages your users visited" (Adoption) tables, and hidden the user on the error log table.
* **Other:** Added the ability to temporarily remove the Userlane snippet from the underlying application to aid in debugging.

## Fixed

* **Portal:** Fixed an issue where Surveys could be created with an end date set before the start date.
* **Portal:** Guarded the Tooltips analytics page so it is not accessible when the Tooltips feature is disabled.
* **Portal:** Fixed the privacy and terms link in the login pages.
* **Portal:** Fixed an issue where company attribute titles could not be edited when the attribute was in use.
* **Editor:** Fixed an issue in the new Browser Extension that prevented RegEx from being generated correctly via AI.
* **Editor:** Fixed an issue where Tooltip titles could not be edited in the Editor.


---

# 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/2024/improvements-and-fixes-august-2024.md?ask=<question>&goal=<user_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.