> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/content-experiences/content-experiences-overview/how-to-set-up-a-content-edit-experience.md).

# How to Set Up a Content Edit Experience

A Content Edit changes copy, images, colors, or other on-page elements using Intelligems' Visual Builder. It's the best fit for smaller, targeted changes (a headline, a button color, a section swap) rather than a full theme or template overhaul.

{% hint style="warning" %}
Doesn't work on headless storefronts. The visual editor needs a live theme to attach to.

On Hydrogen, Remix, or another headless setup? Use the [`@intelligems/headless`](https://headless.intelligems.io/) SDK instead (see Developer Resources > Headless Storefronts).
{% endhint %}

### 1. Create the experience

From the Intelligems app, click **Create New Experience**, and select **Content Edit**.

### 2. Choose: Test or Personalization

* **Running it as a Test?**
  * Fill in a Test Name and Description — internal only, but tests can stay live for weeks, so the more detail here, the more your future self will thank you.
  * Click the **+** button to create a group for each variation (2–5 groups) and name them.
  * Use the slider to set the traffic split for each group.
  * Click **Next Step** when you're done.
  * Note: the more groups you add, the longer it'll take to reach statistical significance.
* **Running it as a Personalization?** Skip groups entirely. You're building one always-on version for your targeted audience.

<figure><img src="https://2052204893-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2SvefuMLsJyJPAcVXeWc%2Fuploads%2F4JAF6NMcZTzsCAjb3LPz%2FPersonalizations%20or%20Tests%20for%20helpcenter.gif?alt=media&amp;token=d7aa9322-6bdd-4566-96ae-d6380eed371b" alt=""><figcaption></figcaption></figure>

### 3. Make your content edits

In the Modifications tab, select **Content Edits**, then [**Visual Builder**](https://docs.intelligems.io/general-features/visual-builder/ai-visual-builder#editing-ai-generated-changes). This opens your live site where you can edit using our AI-powered Visual Builder. Describe the changes you want, and they'll be applied to your site.

<figure><img src="https://2052204893-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2SvefuMLsJyJPAcVXeWc%2Fuploads%2FmvGQWxpRc4d1nwE0t0Lh%2FVisual%20Builder%20content%20edits.gif?alt=media&amp;token=f0f0d338-75ba-4976-b0e3-81d43040fc2f" alt=""><figcaption></figcaption></figure>

You can also make changes manually:

* Click **Select** in the top right of your screen.
* Hover over the page and click any element to select it (it highlights in blue).
* Edit its text, image, or style in the panel that appears.
* Click **Apply** to save each edit, and repeat for any additional elements.
* For more precise targeting, paste a CSS selector directly instead of clicking.

{% hint style="warning" %}
Onsite Edits apply at the selector level, and the same selector can appear on multiple pages. Double-check that your edit doesn't unintentionally show up elsewhere on the site.
{% endhint %}

To move to a different page on your site, click **Navigate** in the top right of your screen.

&#x20;Click **Save** in the top right once you've finished adding all your edits.

### 4. Set targeting (optional)

For a **Test**, a visitor's group is assigned on their first visit and stored via a first-party cookie, so they'll see the same variant on repeat visits during the test.&#x20;

For a **Personalization**, everyone who matches your targeting sees it every time.

Either way, you can narrow who's included in several ways, all under the Audience option unless noted:

* Currency and country targeting, to limit to a single currency and/or list of countries
* UTM parameters
* JavaScript expressions
* Device type (mobile or desktop)
* New vs. returning visitors
* [**Mutually Exclusive Tests**](/general-features/targeting/mutually-exclusive-experiments.md) prevent visitors from being targeted by related experiments at the same time, to avoid interaction effects

You can learn more about targeting [here](https://docs.intelligems.io/content-testing/targeting)!

### 5. Configure analytics

What you configure here depends on which path you chose in step 2:

* **Personalization?** Add any [**Custom Metrics**](https://docs.intelligems.io/analytics/custom-events/using-custom-events-in-experiment-analytics) you want to track, beyond the built-in ones.
* **Test?** Choose your **Key Metrics** and **Primary Metric** to measure against your control group, plus any [**Custom Metrics**](https://docs.intelligems.io/analytics/custom-events/using-custom-events-in-experiment-analytics).

### 6. Preview and activate

Preview your changes on the live site, then activate.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.intelligems.io/content-experiences/content-experiences-overview/how-to-set-up-a-content-edit-experience.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.