> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/web-tools.md).

# Web tools

- [Web personalization](https://user.netmera.com/netmera-user-guide/web-tools/web-personalization.md): Web Personalization adapts website content per visitor with targeted banners and messages, without code.
- [Web personalization dashboard](https://user.netmera.com/netmera-user-guide/web-tools/web-personalization/web-personalization-dashboard.md): Manage web personalization experiences and show different page content to different user groups.
- [Create new experience](https://user.netmera.com/netmera-user-guide/web-tools/web-personalization/create-new-experience.md): Publish a new web personalization experience from Web Tools: name it, set filters and rules, and choose which page elements to change.
- [Setup and rules](https://user.netmera.com/netmera-user-guide/web-tools/web-personalization/create-new-experience/setup-and-rules.md): Set up a web personalization experience name and the rules that decide who sees it and where.
- [New experience](https://user.netmera.com/netmera-user-guide/web-tools/web-personalization/create-new-experience/new-experience.md): Edit website elements for a web personalization experience with CSS, dimension, background, layout, typography, border and HTML options, then publish.
- [Web personalization security review](https://user.netmera.com/netmera-user-guide/web-tools/web-personalization/security-review.md): Web personalization security review requires an authorized reviewer to approve versions before launch.
- [Tag manager](https://user.netmera.com/netmera-user-guide/web-tools/tag-manager.md): Deploy tracking tags and website scripts with Tag Manager without code releases: configure tags, triggers and variables, then preview and publish.
- [Tag manager workspace](https://user.netmera.com/netmera-user-guide/web-tools/tag-manager/workspace.md): The Tag Manager workspace holds the tags, triggers and variables that capture website interactions.
- [Tags](https://user.netmera.com/netmera-user-guide/web-tools/tag-manager/workspace/tags.md): Create Tag Manager tags that define what happens on a site, such as logging an event, updating a profile or running custom code, then attach triggers.
- [Triggers](https://user.netmera.com/netmera-user-guide/web-tools/tag-manager/workspace/triggers.md): Reference for Tag Manager triggers that define when tags run, such as page views, clicks and custom conditions.
- [Variables](https://user.netmera.com/netmera-user-guide/web-tools/tag-manager/workspace/variables.md): Create Tag Manager variables that supply dynamic values like page URL, click text or user attributes to triggers, and import built-in variables.
- [Version history](https://user.netmera.com/netmera-user-guide/web-tools/tag-manager/version-history.md): Tag Manager Version History records each published workspace version with its changes, author and date.
- [Tag manager security review](https://user.netmera.com/netmera-user-guide/web-tools/tag-manager/security-review.md): Tag Manager security review requires a second authorized user to approve a version before publishing.


---

# 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://user.netmera.com/netmera-user-guide/web-tools.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.