# FAQ about EmotionsAI

<details>

<summary>Is there a risk of reducing the website performance when activating EmotionsAI?</summary>

EmotionsAI’s module is loaded asynchronously in AB Tasty’s tag and is based on very light code (18kB). AB Tasty's client-side tag evolves very frequently to add more features and answer more requests, with the aim of never impacting our customers' website performances. The same rule applies to EmotionsAI.\
The module, deployed on several customer accounts already, has no impact on the loading page time once activated, as it is asynchronous.

</details>

<details>

<summary>Does EmotionsAI conform to AB Tasty policies, T&#x26;Cs and GDPR?</summary>

Yes, EmotionsAI is fully compliant with GDPR and with AB Tasty’s policies.

</details>

<details>

<summary>On average on websites, what is the ratio between intuitive and rational profiles?</summary>

On average, we notice 2/3 of intuitives, and 1/3 of rationals on e-commerce websites, but it differs a lot from one industry to another, and it can also differ from one country to another. The best way to know the split for your website is to ask us for it!

</details>

<details>

<summary>Why do we register fewer users on EmotionsAI compared to AB Tasty or other analytics tools?</summary>

We only consider individuals who accept cookies and are scored (after 30 seconds on the site). Therefore, gaps between EmotionsAI report and other analytics reports will be higher on landing pages (home + landing), where we primarily qualify returning visitors.

</details>


---

# Agent Instructions: 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:

```
GET https://docs.abtasty.com/emotions-ai/faq-about-emotionsai.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.