> For the complete documentation index, see [llms.txt](https://developer.esw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.esw.com/adobe-commerce-magento/additional-features/ab-tasty-integration.md).

# AB Tasty Integration

AB Tasty Integration lets retailers run A/B tests and personalization campaigns on the storefront. It helps teams test content, layout, and user experience changes without changing core Adobe Commerce code.

### How the integration works

AB Tasty is loaded on the storefront through a JavaScript snippet added to the site head. Once the script is active, AB Tasty can load experiments and personalized experiences in real time.

All campaigns are managed in the AB Tasty platform. Retailers can use it to:

* test layout, messaging, or page content
* personalize experiences by audience segment
* target visitors by geography, device, traffic source, or shopper behavior
* measure campaign performance and conversion impact

### Add the AB Tasty script to Adobe Commerce

To load AB Tasty on the storefront:

1. Log in to Adobe Commerce Admin.
2. Go to **Content → Configuration**.
3. Open the theme you want to edit.
4. In the **HTML Head** section, find **Scripts and Style Sheets**.
5. Paste the AB Tasty JavaScript URL provided by AB Tasty.
6. Save the configuration.

{% hint style="info" %}
The AB Tasty script must load on the storefront before campaigns can run or be validated in QA.
{% endhint %}

### Configure a campaign in AB Tasty

After the script is added, create and manage tests in the AB Tasty dashboard.

A typical setup includes:

1. Select the correct environment.
2. Create a new campaign or test.
3. Set the target URL for the page or site area you want to test.
4. Add the visual or behavioral changes for the variation.
5. Define campaign goals.
6. Configure audience targeting.
7. Allocate traffic between the original and alternative experiences.
8. Compile and publish the campaign.

### Example test flow

One example is an A/B test for the **About Us** page.

In this case, the campaign can:

* target the About Us page URL
* change the page title or another visual element
* split traffic evenly between the original version and the new version
* publish the campaign for QA validation before release

### Use QA Assistant to validate a campaign

AB Tasty QA Assistant can be used to preview the active variation on the storefront before the campaign is released broadly.

With QA Assistant, you can:

* open the original version of the page
* open the alternative version of the page
* verify that the test loads on the intended page
* confirm that targeting and variation changes work as expected

<div data-with-frame="true"><figure><img src="/files/fcX0mLi6sauySxt45hcZ" alt=""><figcaption><p>Original version</p></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="/files/jSoz093BzeAMxKJObEhi" alt=""><figcaption><p>Alternative version</p></figcaption></figure></div>

### Expected result

After setup is complete:

* AB Tasty campaigns load on the storefront
* teams can test and personalize storefront experiences safely
* campaign performance can be measured before permanent rollout


---

# 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://developer.esw.com/adobe-commerce-magento/additional-features/ab-tasty-integration.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.