> 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.md).

# Web personalization

Web Personalization adapts website content per visitor with targeted banners and messages, without code.

Web Personalization dynamically adapts website content and UI for individual visitors. Use it to display targeted banners, product recommendations, or tailored messaging. Define rules and filters for specific audiences, then publish changes without code deployments.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FxfaXFGhVrMh167lRodRu%2Fimage.png?alt=media&#x26;token=5f459ab4-6916-430c-a448-f5f6067e0b55" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
This feature lives under **Web Tools → Experiences → Web Personalization**.
{% endhint %}

### Start here (most-used topics)

<table data-view="cards"><thead><tr><th>What you want to do</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td>Understand the dashboard (stop/clone/edit)</td><td><a href="/netmera-user-guide/web-tools/web-personalization/web-personalization-dashboard.md">Web personalization dashboard</a></td></tr><tr><td>Create and publish a new experience</td><td><a href="/netmera-user-guide/web-tools/web-personalization/create-new-experience.md">Create new experience</a></td></tr><tr><td>Configure setup + rules (trigger, changes, filters, schedule)</td><td><a href="/netmera-user-guide/web-tools/web-personalization/create-new-experience/setup-and-rules.md">Setup and rules</a></td></tr><tr><td>Edit the page (CSS/HTML) and publish</td><td><a href="/netmera-user-guide/web-tools/web-personalization/create-new-experience/new-experience.md">New experience</a></td></tr><tr><td>Require an approval before changes go live</td><td><a href="/netmera-user-guide/web-tools/web-personalization/security-review.md">Web personalization security review</a></td></tr></tbody></table>

### Quickstart: publish a personalization experience

{% stepper %}
{% step %}

#### 1) Decide what you will change

Examples: hero banner, CTA text, pricing block, homepage modules.
{% endstep %}

{% step %}

#### 2) Define who should see it

Use filters like Segment, Tag, device type, page URL, time spent, source URL.
{% endstep %}

{% step %}

#### 3) Pick trigger + schedule

Use **page load** for most sites.

Use **continuous** for single-page apps.
{% endstep %}

{% step %}

#### 4) Add changes and edit the page

Select elements on the page and apply CSS/HTML changes.
{% endstep %}

{% step %}

#### 5) Save and publish

Use preview first.

Then publish and monitor impact.

If [Security review](/netmera-user-guide/web-tools/web-personalization/security-review.md) is enabled for your app, **Launch** appears as **Send to Review** and the changes go live only after a Security Reviewer approves them.
{% endstep %}
{% endstepper %}

### Key concepts (fast)

* **Experience**: one personalization variant with its own rules and changes.
* **Filters**: who is eligible (segment/tag/device/page/source/etc).
* **Changes**: what to modify on the page (CSS/HTML edits).
* **Trigger**: when to apply (page load vs continuous).


---

# 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.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.