> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/emotions-ai/using-emotionsai/target-emotionsai-segments.md).

# Target EmotionsAI segments

This documentation will show you how to get the best from the emotional analysis by acting on the EmotionsAI segment in the targeting of your campaigns.

Once your EmotionsAI module is activated, creating a campaign targeting one or several of the EmotionsAI segments is simple: whether you create a web experiment or a personalization, the targeting step is where you can define the audience that sees your campaign. Like for any other campaign, you simply have to define the audience you want to target and select the segments when defining the targeting.

From the segment builder, you can retrieve EmotionsAI segments in the `BEHAVIOR` category. You can then simply follow the guidelines to create the segment of your choice.

![](https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2Fgit-blob-6ffa015cef5e8281f0d9c8a9a26c92abf85f7da1%2F728a9f6318ef7365523fea8d91e9279b.png?alt=media)

For more details, you can refer to the[ EmotionsAI criterion article](/assets-library/creating-and-managing-segments/list-of-segment-criteria/emotionsai-criterion.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.abtasty.com/emotions-ai/using-emotionsai/target-emotionsai-segments.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.