Skip to content
Book a demoStart free
Connectors

Brevo connector

Set up the Brevo connector in Kaivo: authentication, configuration, the 3 BigQuery tables it syncs, and answers to common questions.

Brevo connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Brevo data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your survey and email data instead of moving it.

Sync your Brevo email data into BigQuery with Kaivo to track campaigns, list hygiene, and audience growth in one place.

CategorySurveys & Email
AuthenticationAPI key
SetupSelf-service
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Brevo account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Authenticate with your API Key.

Field Description
API Key
Your API Key. See here.

|

Kaivo syncs 3 tables from Brevo into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

campaigns (23 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
type STRING
ab_testing BOOL
created_at STRING
footer STRING
header STRING
html_content STRING
id INT64
inline_image_activation BOOL
mirror_active BOOL
modified_at STRING
name STRING
preview_text STRING
reply_to STRING
scheduled_at STRING
send_at_best_time BOOL
share_link STRING
status STRING
subject STRING
tag STRING
test_sent BOOL
to_field STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
contacts (8 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
created_at STRING
email STRING
email_blacklisted BOOL
id INT64
modified_at STRING
sms_blacklisted BOOL
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value JSON
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
templates (14 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
type STRING
created_at STRING
html_content STRING
id INT64
is_active BOOL
modified_at STRING
name STRING
reply_to STRING
subject STRING
tag STRING
test_sent BOOL
to_field STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Brevo supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.

How long does the initial sync take for Brevo?

Section titled “How long does the initial sync take for Brevo?”

It depends on how much history is in your Brevo account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.

Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.

What happens when Brevo’s schema changes?

Section titled “What happens when Brevo’s schema changes?”

New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Brevo, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.

How do I handle GDPR or data deletion requests?

Section titled “How do I handle GDPR or data deletion requests?”

Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Brevo instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Brevo connector in Kaivo and all of its synced data is deleted with it.

Use campaigns status and scheduled_at to follow what you send and when.

Use contacts email_blacklisted and sms_blacklisted to monitor deliverability risk.

Track contacts over time to see how your list grows.

Use templates to document the emails you send.

Once Brevo data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Brevo data.

Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

The premium analytics standard, with native BigQuery integration. Setup guide →

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Connect via Power Query’s BigQuery connector. Setup guide →

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for Brevo connector pricing and plan details.