> 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/web-personalization/create-new-experience.md).

# Create new experience

Publish a new web personalization experience from Web Tools: name it, set filters and rules, and choose which page elements to change.

{% hint style="info" %}
**Quick Steps Guidelines**

Go to your Netmera Panel and click:

1. Go to the **Web Personalization** page in the Web Tools section.
2. Click on the "**Publish a New Experience**" button.
3. Give your experience a **name and decide on filters** and complete the information in [setup-and-rules](/netmera-user-guide/web-tools/web-personalization/create-new-experience/setup-and-rules.md).
4. Click on "**Add Changes**" in Rules / Changes section.
5. **Customize your new content** to make sure it looks the way you want it to.
6. Click **Save** and **Done,** and the changes **will directly apply to your web page.**
   {% endhint %}

{% hint style="warning" %}
If [Security review](/netmera-user-guide/web-tools/web-personalization/security-review.md) is enabled for your app, step 6 works differently: **Launch** appears as **Send to Review**, a version note is requested, and the changes reach the site only after a Security Reviewer approves them.
{% endhint %}

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td></td><td><a data-mention href="/netmera-user-guide/web-tools/web-personalization/create-new-experience/setup-and-rules.md">Setup and rules</a></td><td></td></tr><tr><td></td><td><a data-mention href="/netmera-user-guide/web-tools/web-personalization/create-new-experience/new-experience.md">New experience</a></td><td></td></tr></tbody></table>


---

# 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/web-personalization/create-new-experience.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.