> 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/commerce/recommendations/how-to-configure-your-email-integration/how-to-configure-brevo-integration.md).
# How to configure Brevo integration
Integrating Brevo with AB Tasty Recommendation and Merchandising
{% stepper %}
{% step %}
### Connect Brevo
1. In your Brevo account, generate an API Key**: SMTP & API > API Keys**, and copy it
1. In your AB Tasty account, go to **Settings > Integrations > Brevo**.
2. Paste the API key from Brevo into the API key field and click **Connect Brevo**.
{% endstep %}
{% step %}
### Allow AB Tasty IPs on Brevo
To allow AB Tasty to retrieve your Brevo contact attributes, make sure the following IP addresses are in your Acceptlist in your Brevo account or firewall settings:
* `130.211.64.215`
* `34.79.119.76`
* `35.240.71.177`
If these IPs are not authorized, the list of contact attributes may appear empty even though the integration is set up correctly.
{% endstep %}
{% step %}
### Deploy a recommendation in your email
Now you can [deploy a recommendation in Brevo](/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/how-to-deploy-recommendation-with-brevo.md).
{% endstep %}
{% endstepper %}
{% hint style="info" %}
For more personalization, you can create repeated variables so your emails feel like real one-to-one conversations. 🔗 [Learn more about Dynamic Content in Brevo](https://editor-beta.brevo.com/editor/newsletters/46#:~:text=Faites%20une%20liste,le%20contenu%20dynamique)
{% 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 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/commerce/recommendations/how-to-configure-your-email-integration/how-to-configure-brevo-integration.md?ask=&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.
