> For the complete documentation index, see [llms.txt](https://emailpref.gitbook.io/emailpref-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://emailpref.gitbook.io/emailpref-documentation/integrations/brevo/prerequisites.md).

# Prerequisites:

Before you dive into integrating Emailpref with Brevo, there are a few essential prerequisites you'll need to have in place:

[**Brevo Account:** ](https://account-app.brevo.com/account/login)To create a successful integration, you must have an active Brevo account. This account serves as the foundation for your email marketing campaigns and will be essential for configuring the integration with Emailpref.

{% embed url="<https://account-app.brevo.com/account/login>" %}

[**Emailpref Account:**](https://app.emailpref.com/) Similarly, you'll need to have an Emailpref account set up and ready to go. If you haven't already, visit Emailpref's website to sign up and gain access to the powerful preference page management capabilities that Emailpref offers.

Having both a Brevo account and an Emailpref account will ensure a smooth and seamless integration process, enabling you to take full advantage of the enhanced subscriber management features Emailpref brings to your Brevo campaigns.


---

# 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://emailpref.gitbook.io/emailpref-documentation/integrations/brevo/prerequisites.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.