> 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/general-features/atlas-ai/atlas-experience-agent/faqs.md).

# FAQs

**What does the Atlas Experience Agent do?**

It generates a configured experience from a written description: type, groups, allocation, targeting, analytics, and content modifications.

**What experience types can it create?**

Onsite edits, theme tests, template tests, URL redirects, and JavaScript/CSS. Offers, checkout, post-purchase, price, and shipping experience types are not yet supported.

**What happens when an unsupported experience type is requested?**

Atlas states that the type is not supported and guides you through the setup process.

**Does it create a test or a personalization?**

Either, based on the description provided. Atlas requests clarification when the type is not specified, and the selection can be changed during the conversation.

**Can it configure targeting?**

Yes: common, advanced, custom, page-level, and mutual exclusion targeting.

**Can it create a new custom event?**

No. It can attach existing custom events but cannot create new ones.

**Does Atlas activate experiences automatically?**

No. Activation is a manual step.


---

# 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/general-features/atlas-ai/atlas-experience-agent/faqs.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.
