> 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/salesforce-commerce-cloud/salesforce-commerce-cloud/checkout-integration/abtasty-integration.md).

# ABTasty Integration

AB Tasty is a tool used to run A/A, A/B, and other types of tests on the storefront. It offers several advantages over the default A/B testing provided by Salesforce Commerce Cloud (SFCC).

## Advantages

* **Comprehensive and Flexible**: AB Tasty offers a more robust and flexible platform for running experiments and personalization
* **Extensive Test Options**: It supports a wide variety of test types, including **multivariate** and **multipage** tests, enabling more complex and in-depth experimentation.
* **User-Friendly Interface**: With an intuitive interface and advanced targeting capabilities, AB Tasty makes it easy to create and manage campaigns based on user behavior, demographics, and other key criteria.
* **In-Depth Analytics**: AB Tasty provides powerful analytics and reporting tools that deliver actionable insights into user behavior, empowering retailers to make data-driven decisions and continuously optimize the site experience.
* **Centralized Reporting**: While SFCC’s native A/B testing reports are limited to the SFCC instance, AB Tasty allows plugin developers to access centralized test data across environments.

Retailers can define and manage A/B tests and personalization campaigns **directly within the AB Tasty platform**. Once configured, tests and campaigns are seamlessly applied to the **SFCC storefront**, enabling:

* Dynamic content adjustments
* User experience optimizations

## SFCC Configuration

The custom site preference `ESW AB Tasty Script Path` in the **ESW Retailer Display Configuration** is used to define the **URL path for the AB Tasty script**. The cartridge injects the below script in the header so that AB tasty script is enabled if configured.

![](/files/a68eacdcd2df566ec66b297b81f499f927e63611)

### URL Script

ESW AB Tasty Script Path in the ESW Retailer Display Configuration.

## Testing

### AB Tasty Configuration — Example Tests

#### Test A – Default (Control Group)

Display Disabled Checkout Button incase restricted products are in cart (Default)

#### Test B – Variant

Hide Checkout Button incase restricted products are in cart.

Below are the configuration steps for one of the tests:

{% stepper %}
{% step %}

### Create Tests

Select the environment in the AB tasty platform and create the tests

![](/files/11612e89ecc6b670630706586897119c91d0c1eb)

Display/hide checkout button
{% endstep %}

{% step %}

### Configure environment

Ensure the URL for the correct environment is configured

![](/files/8e8b4d18a6bafc5421b147574fac4e62c190d11d)

Display/hide checkout button
{% endstep %}

{% step %}

### Add Code Changes

Add code changes for the AB test. In this case, the code logic to hide button was added incase product restriction message is present on the storefront cart page.

![](/files/24301839c8de59d58a9771e6684b0b4b794954ed)

Display/hide checkout button
{% endstep %}

{% step %}

### Add Goals and Targeting URL

* Add Goals and then add Targeting URL.
* Ensure the Pages where the test will be displayed is a generic site URL to ensure that the test loads.

![](/files/0ea4f6ce6a621b9c3a29a86f0fb3181c0aee6b40)

Display/hide checkout button
{% endstep %}

{% step %}

### Allocate Traffic

In this example, the 50% of the traffic is allocated to Hide the checkout button and 50% is allocated to disable the button which is the original version.

![](/files/1a9bb61e693b4c48cae5c2a037dc0cfaaa70f52a)

Display/hide checkout button
{% endstep %}

{% step %}

### Publish

Compile and click on `Open QA Assistant` to publish live

![](/files/19906478c62fb32801875dbd5f6c1afe39d67d3b)

Display/hide checkout button

![](/files/4bf85991ba1ef2e77f4b91617f19bca47f1a0fe3)
{% endstep %}
{% endstepper %}

### Using QA Assistant to check variation of campaign

Once configuration and test setup are complete, and the AB Tasty script is successfully loaded, the **storefront will open with the AB Tasty QA Assistant** activated.

![](/files/c4cd8ca913a949b0f7db84315f676f018694c768)

storefront ospen with AB Tasty QA Assistant

To test this configuration, add the product to the basket, then navigate to **Business Manager > Merchant Tools > Products** and set the `ESW List of Countries Where Product Is Restricted` to match the country selected on the storefront.

![](/files/8fc3950893156c134050b901a27eedb96cd2a4d1)

ESW List of Countries Where Product Is Restricted

Once completed, you can view both test versions on the storefront by using the `Variation/Experience` dropdown in the QA Assistant.

## Results

Variation

{% columns %}
{% column %}
![](/files/ec26557afdb9bbbcc61e1dc3c5e8f7c2eec405aa)

Verison A
{% endcolumn %}

{% column %}
![](/files/94e7b54c61fb74a69d8d869914bf75c7ee72e076)

Version B
{% endcolumn %}
{% endcolumns %}


---

# 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/salesforce-commerce-cloud/salesforce-commerce-cloud/checkout-integration/abtasty-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.