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

# Content Experiences Overview

A Content Experience changes what visitors see on your site: copy, images, layout, even your entire theme. Every experience starts the same way: you build the change once. From there, you decide whether to run it as a Test (measured against a control group) or a Personalization (always-on for a targeted audience). New to that distinction? See how [Tests and Personalizations](/getting-started/tests-vs.-personalizations.md) work.

### The 5 experience types

| Type                      | What it's for                                |
| ------------------------- | -------------------------------------------- |
| **Content Edits**         | Change headlines, copy, and on-page elements |
| **Redirects**             | Send traffic to a different URL by audience  |
| **Styles and Javascript** | Inject custom CSS and JS safely              |
| **Theme Change**          | Swap the live theme for a variant            |
| **Template Change**       | Test alternate page templates                |

They can also be used in conjunction with one another. One experience can carry a Content Edit and a Styles & Javascript change together.

{% hint style="info" %}
Content is included in every Intelligems plan, so all five types are available to you no matter which other modules you have.
{% endhint %}

Each type has its own setup guide below, covering both the Test and Personalization path in one place:

* [How to Set Up a Content Edit](/content-experiences/content-experiences-overview/how-to-set-up-a-content-edit-experience.md)
* [How to Set Up a Redirect ](/content-experiences/content-experiences-overview/how-to-set-up-a-redirect-experience.md)
* [How to Set Up a Styles & JavaScript ](/content-experiences/content-experiences-overview/how-to-set-up-a-styles-and-javascript-experience.md)
* [How to Set Up a Theme Change Experience](/content-experiences/content-experiences-overview/how-to-set-up-a-theme-change-experience.md)
* [How to Set Up a Template Change Experience](/content-experiences/content-experiences-overview/how-to-set-up-a-template-change.md)

Once you've built one, the [QA Checklist](/content-experiences/content-test-qa-checklist.md) covers what to check before you start, and the [Content Experiences FAQs](/content-experiences/content-testing-faqs.md) answer the questions that come up most. For test ideas, see [Content Test Common Use Cases](/content-experiences/content-experiences-overview/content-test-common-use-cases.md) or the full [capability list](/what-you-can-test.md).


---

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