> 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/web-personalization-dashboard.md).

# Web personalization dashboard

Manage web personalization experiences and show different page content to different user groups.

**Web Tools > Experiences > Web Personalization**

Web Personalization lets you configure **segments and tags** and use them to display different web page content for different user groups. You can define the content shown to each group and publish the changes without a code deployment.

{% hint style="info" %}
**Example:**

With Web Personalization, you can create different homepage experiences for different segments. For example, if you have segments such as "New Visitors," "Returning Customers," or "High-Value Customers," you can configure homepage content for each segment, including product recommendations, offers, or personalized greetings.
{% endhint %}

To access the web personalization creation menu, navigate to the Web Tools category and find "Experiences". This section contains five functions for configuring web pages for specific user segments and delivering personalized content.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2F6dt8r11wT5gsKET5Dru9%2FScreenshot%202023-08-01%20at%2015.49.00.png?alt=media&#x26;token=807da706-81e7-4a2f-a1ac-e0723f48e610" alt=""><figcaption><p>Web Tools > Experiences > Web Personalization</p></figcaption></figure>

## Web Personalization Page Functions

Web Personalization Page has 5 functions: **experience summary, stop an experience, clone, edit, and create a new personalization experience**.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FxZNtFpTw0T7mBkCPSQOG%2Fimage.png?alt=media&#x26;token=2e7e6089-c0fb-4554-bc94-d44460a0644c" alt=""><figcaption></figcaption></figure>

### Experience Summary

Click an existing experience to view its summary and make adjustments as needed.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FcHcrdUDWsGLc5684dymW%2Fimage.png?alt=media&#x26;token=c54072c9-dc54-4a36-9cdd-fd0693521cde" alt=""><figcaption></figcaption></figure>

### Stop an Experience

To stop a running experience, click the **stop** icon in the Actions section.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2F1O5lj1brnyq9sDfQzi9N%2Fimage.png?alt=media&#x26;token=92fc7fe5-2f54-4cf2-9713-fd0f7eb49fdb" alt=""><figcaption></figcaption></figure>

### Clone an Experience

You can **clone** a running experience by clicking the clone icon in the Actions section.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FXz45k5filuwhkIlWgvVA%2Fimage.png?alt=media&#x26;token=527de0b0-e13c-4f34-b775-737a8612a413" alt=""><figcaption></figcaption></figure>

### Edit an Experience

For experiences you have already stopped, you can click the **edit** icon to make changes. Editing is only applicable to stopped experiences. To edit a live experience, you must first stop it.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FdVc2UD2o54zQK31kiXtz%2Fimage.png?alt=media&#x26;token=5e69eb19-4835-449f-8452-bbec81a57651" alt=""><figcaption></figcaption></figure>

### Create a New Experience

To create a new experience, click the **"Publish New Personalization Experience"** button in the upper right.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FiaxX8lrF7tTrzKki4erd%2Fimage.png?alt=media&#x26;token=31a9cd0f-7709-4cd2-9666-53db369fd276" alt=""><figcaption></figcaption></figure>

## When security review is enabled

If [Security review](/netmera-user-guide/web-tools/web-personalization/security-review.md) is enabled for your app, the dashboard gains a **Version History** table and experiences carry an approval status.

### Version History

Version History lists every container version published from this panel, with its status and the actions available on it.

| Status             | Meaning                                                 | Available actions                       |
| ------------------ | ------------------------------------------------------- | --------------------------------------- |
| **Waiting Review** | Submitted and waiting for a Security Reviewer decision. | Review Actions (Security Reviewer only) |
| **Live**           | Approved and published to the site.                     | Stop                                    |
| **Rejected**       | Reviewed and declined.                                  | Archive, delete                         |
| **Past**           | Previously live, replaced by a newer approved version.  | Archive, delete                         |

### Experience statuses

Experiences in the workspace table reflect where they stand in the approval flow:

* **In review** – submitted and waiting for a decision. No actions are available while it waits.
* **Published** – approved and live. Copy and stop actions are available.
* **Draft** – rejected, or not yet submitted. Edit, delete, and archive actions are available, and the experience can be sent to review again by any user with access.


---

# 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/web-personalization-dashboard.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.