> 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/qa-a-campaign-on-desktop-with-emotionsai-chrome-extension.md).

# QA a campaign on Desktop with EmotionsAI Chrome Extension

[EmotionsAI Chrome Extension](https://chrome.google.com/webstore/detail/ab-emotions-ai/dabbkpndimencgjjmeajjdpjlcigaoog) enables you to visualize the different variations of your website as different EmotionsAI segments by selecting one of them.

Once you have selected a segment and clicked on the “Apply” button, the page you are on is reloaded and you can verify if the personalization you have setup for this specific segment is well displayed.

Technically speaking, it override the segment defined on your browser.

<img src="/files/VFeHlpawu4oilrBDjw8b" alt="" width="311">


---

# 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.abtasty.com/emotions-ai/using-emotionsai/qa-a-campaign-on-desktop-with-emotionsai-chrome-extension.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.
