> 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/usage-of-emotionsai-in-some-push-integrations.md).

# Usage of EmotionsAI in some Push integrations

This documentation will explain to you the basics of pushing the EmotionsAI segments in diverse integrations setup.

AB Tasty gives you the possibility to export the EmotionsAI audience of the visitors by the time we push the campaign hit to your third-party tool. With this information, you will be able to segment all visitors exposed to an AB Tasty campaign. 

This is currently part of an EA program. Please contact your CSM to benefit from it.

To benefit from EmotionsAI, you must activate the feature from your AB tasty account [here](https://app2.abtasty.com/settings/emotion-ai). 

Without this activation, we won't be able to send the EmotionsAI audience to your third-party tool. For more information on how to activate EmotionsAI, please contact your CSM. 

EmotionsAI can now be used in the following integrations:

* [Google Analytics 4](broken://pages/SFxaqM7U8cveSyUzZ5bM#emotionsai)
* [AT Internet](/integrations/push-integrations/at-internet-smart-tag.md#emotionsai)
* [Piano Analytics](/integrations/push-integrations/piano-analytics.md#your_anchor_name)


---

# 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/usage-of-emotionsai-in-some-push-integrations.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.