> 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/how-to-deploy-a-recommendation-strategy-on-web/low-code-deployment-using-a-custom-widget.md).

# Low-code deployment using a Custom Widget

#### Prerequisite :

* **Have AB Tasty tag**. \
  To verify that you have successfully installed it on your website, open your console and type with remplace RECO\_ID with one of your **recommendation IDs** (available in your Recommendations list) :&#x20;

  ```
  recos.reco(RECO_ID)
  ```

  This command returns a **Promise** that resolves with a product list, confirming that the tag is correctly loaded and the required data is available on the page. Else contact your CSM.

{% stepper %}
{% step %}

#### **Configure and Add the Custom Widget**

Your AB Tasty team will provide you with a **Custom Widget** configured for your recommendations.

1. Go to your AB Tasty campaign editor.
2. Add the provided **Custom Widget** to your campaign.
3. Link it to the corresponding `RECO_ID` to display your recommendation banner.
   {% endstep %}
   {% endstepper %}

Your recommendation banner is now live using the **Custom Widget** and the **Recommendation Tag**.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.abtasty.com/recommendations-and-merchandising/how-tos/how-to-deploy-a-strategy/how-to-deploy-a-recommendation-strategy-on-web/low-code-deployment-using-a-custom-widget.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
