Question 1

What can Polytomic write to in Brevo?

Accepted Answer

Contacts, and contacts within a specific list. You can point a sync at contacts generally, or select a list so the sync loads into that list directly, and Polytomic can create a new list and folder for you during setup if you do not have one yet. Write modes are create, update, and update or create. There is no delete mode, so a sync will not remove contacts from your Brevo account. Transactional email and event writes are not supported by this connector despite some documentation suggesting otherwise, which is a documentation gap rather than a hidden capability.

Question 2

How does Polytomic match records to existing Brevo contacts?

Accepted Answer

You can match on the Brevo contact ID, on email, or on an existing text or number custom attribute. When you match on something other than the contact ID, Polytomic first queries Brevo for a contact with that value, resolves the underlying contact ID, and then updates by ID. For list loads the behavior differs slightly: those go through Brevo's bulk import with existing contact updates enabled, so Brevo performs the matching rather than Polytomic resolving each record first. Both approaches produce the upsert behavior you would expect.

Question 3

Can I manage list membership from my data warehouse?

Accepted Answer

Yes, and this is the main reason teams connect Brevo. Beyond syncing into a selected list, the contacts target exposes fields for list IDs to add and list IDs to unlink, so a model can express membership directly. That means a lifecycle segment computed in your data warehouse can move contacts between Brevo lists automatically as people qualify or drop out, which is reverse ETL doing the work instead of someone exporting a CSV every week. Removing a contact from a list is supported; deleting the contact itself is not.

Question 4

Can Polytomic create new Brevo contact attributes?

Accepted Answer

No. Polytomic writes to attributes that already exist in your Brevo account, covering text, number, boolean, date, and enum types, but it cannot create new attribute definitions. The workflow is to add the attribute in Brevo first, after which it appears as a mappable destination field. Calculated attributes are read only within Brevo itself, so those cannot be written from any external system. Email can be used as an identity and set on creation, but is not treated as an updateable field.

Question 5

Why use reverse ETL for Brevo instead of importing a CSV?

Accepted Answer

A CSV import is a snapshot that starts going stale the moment it finishes, and someone has to remember to do it again. Reverse ETL keeps the audience defined where your data actually lives. You write the segment logic once against your data warehouse, and Polytomic keeps Brevo aligned with it on a schedule, adding people as they qualify and updating attributes as they change. It also means marketing and analytics work from the same definition of a customer rather than two divergent ones, which is usually the real problem CSV workflows create.

Brevo

Perfect pairings

Contact sync from anywhere

List membership control

Custom attribute mapping

Example workflows

What you can sync

From your sources

To Brevo

How it works

How to set up

Frequently asked questions

Why teams choose Polytomic

No engineering required

Flexible data modeling

Handles scale automatically

Start syncing your data with Brevo in minutes

More integrations beyond Brevo