> 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/account/tag-integration/what-is-the-ab-tasty-tag.md).

# What is the AB Tasty Tag?

The AB Tasty Tag is a lightweight JavaScript snippet that enables dynamic experimentation, personalization, and data tracking across your website. It acts as the entry point for all AB Tasty features, ensuring experiments are delivered efficiently and data is collected reliably.

#### Key Use Cases

The Tag is used for client-side web experimentation and personalizations: 

* Display A/B tests and personalization campaigns
* Collect behavioral and performance data
* Integrate with your analytics or consent management tools

#### Architecture Overview

The tag fetch configuration and experience data. Once initialized, it can apply variations, record metrics, and send events in real time.

{% hint style="info" %}
AB Tasty also provides a [transaction Tag](/account/how-to-implement-the-transaction-tag.md)  that you can install to collect further insights on the transactions made on your website
{% endhint %}


---

# 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/account/tag-integration/what-is-the-ab-tasty-tag.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.