> 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/recommendations-and-merchandising/how-tos/how-to-deploy-a-strategy.md).

# How to deploy a strategy

When publishing a strategy, integration depends on the **channel** where recommendations or merchandising will be displayed.

\
The three main use cases are:

1. [Recommendations on Web](/recommendations-and-merchandising/how-tos/how-to-deploy-a-strategy/how-to-deploy-a-recommendation-strategy-on-web.md)
2. [Merchandising on Web](/recommendations-and-merchandising/how-tos/how-to-deploy-a-strategy/how-to-deploy-a-merchandising-on-web.md)
3. [Recommendations in Emails](/recommendations-and-merchandising/how-tos/how-to-deploy-a-strategy/how-to-deploy-a-recommendation-strategy-on-web/how-to-use-recommendations-in-emails-campaign.md)

### Recommendation Banner Integration Options

Recommendations & Merchandising offers several ways to deploy your recommendation banners depending on your technical setup and level of customization.\
Choose the method that best fits your workflow from visual widgets to fully headless integrations.

***

#### **1°/ Using a Custom Widget (no-code / low-code)**

Deploy your recommendation banner directly through a **Custom Widget** in the AB Tasty platform.\
This approach requires no code and allows marketing or e-merch teams to easily manage and update banners through the visual editor.

→ Learn more in the detailed guide: **Deploying a Recommendations Banner Custom Widget :**

{% embed url="<https://app.gitbook.com/o/iFKI1JaxSfPoiGt4tT2k/s/6Yw9IRJ6KbbucQPwZUCZ/~/changes/322/recommendations-and-merchandising-1/getting-started/recommendations/publishing-a-recommendation/dynamic-widget>" %}

***

#### **2°/ Using the Tag + Custom JavaScript (front-end integration)**

For more control over the design or placement, you can use the **AB Tasty unified tag** with **custom JavaScript**.\
This setup lets you retrieve and display recommendations dynamically on your site, while maintaining flexibility on the rendering logic.

→ Learn more in the detailed guide: **Recommendation banner with tag and custom JS :**&#x20;

***

#### **3°/ Using the API (headless / advanced integration)**

For full control and server-side rendering, you can integrate recommendations using the **Recommendations API**.\
This method is ideal for headless architectures or when you need to fetch and display recommendation data within your own components or CMS templates.

→ Learn more in the detailed guide: **Retrieving Recommendations via API**

{% embed url="<https://app.gitbook.com/o/iFKI1JaxSfPoiGt4tT2k/s/6Yw9IRJ6KbbucQPwZUCZ/~/changes/322/recommendations-and-merchandising-1/getting-started/recommendations/publishing-a-recommendation/api>" %}


---

# 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/recommendations-and-merchandising/how-tos/how-to-deploy-a-strategy.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.