Brevo is a marketing platform that businesses use to manage contacts, send email and SMS campaigns and transactional emails, and track the delivery and engagement of their messages.
Hevo uses the Brevo API to replicate the contacts, contact lists, email and SMS campaigns, campaign statistics, templates, products, senders, and email events of your Brevo account to the Destination of your choice. To ingest data, you must provide Hevo with the API key of your Brevo account.
Supported Features
| Feature Name | Supported |
|---|---|
| Capture deletes | Yes |
| History mode | No |
| Custom data (user-configured tables & fields) | No |
| Data blocking (skip objects and fields) | Yes |
| Resync (objects and Pipelines) | Yes |
| API configurable | Yes |
Handling of Deletes
How Hevo captures a deleted record depends on the object:
-
Categories and Product: Brevo continues to return a deleted record and identifies it as deleted by the value true in its is_deleted field. Hevo marks such a record as deleted by setting the value of the metadata column _hevo_marked_deleted to True. The record remains in the Destination with all its data.
-
Contact: Hevo does not capture deletes for this object, so contacts deleted in Brevo remain in the Destination. When Hevo ingests a contact, it replaces the records of the Contact List object for that contact, so a list that the contact no longer belongs to is removed.
-
Transactional Email Event and Inbound Event: Hevo does not capture deletes for these objects.
-
All other objects: Hevo compares the data ingested from the Source with the data present in the Destination in each run. If a record exists in the Destination but is no longer returned by the Source, Hevo marks it as deleted by setting the value of the metadata column _hevo_marked_deleted to True. The record remains in the Destination with all its data. However, if an object no longer has any records in Brevo, for example, if you delete your only email template, Hevo does not mark its previous records as deleted.
Source Considerations
-
Brevo displays the API key only once, when you generate it. If you lose the API key, you must generate a new one in Brevo and update it in the configuration of your Source.
-
Brevo deactivates an API key that is not used for 90 days, and an API key also stops working after its expiry date. If your Pipeline stops ingesting data with an authentication error, generate a new API key and update it in the configuration of your Source.
-
If you block unauthorized IP addresses for your API keys in Brevo, add Hevo’s IP addresses for your region under Security > Authorized IPs in Brevo. Otherwise, Brevo rejects the requests from Hevo.
-
If the eCommerce section is not activated in your Brevo account, Brevo does not return the products and categories, and Hevo cannot ingest the Categories, Product, and Product Category objects.
-
Brevo returns the transactional email events and inbound events only after a delay. Therefore, Hevo ingests the events up to 12 hours before each run.
Limitations
- Hevo does not ingest the CRM data (companies, deals, and tasks), WhatsApp campaigns, conversations, automations, webhooks, or account settings of your Brevo account.





