01
True cost per signup
Join spend with signups from your own database instead of trusting platform-reported conversions.
CPA by campaign
Marketing
Brevo + Kimo
Email & SMS campaigns and contacts. Pull spend, reach and conversions into one model and see which campaigns actually turn into revenue.
- Auth
- API key
- Sync
- Hourly
- Setup
- ≈ 3 min
Live demo workspace with fictional data · no signup, no credentials needed
kimo / connectors / brevoSyncing
Sync loghourly
- Succeeded:campaigns+1,212 rowsnow
- Succeeded:conversions+431 rows2m ago
- Succeeded:campaign_stats_daily+2,050 rows4m ago
- Succeeded:campaigns+1,269 rows6m ago
Rows synced · 30 days
124.2M
Workspaces
20%
What you can do
What teams build with Brevo
Brevo on its own answers half the question. Joined with the rest of your stack in Kimo, it answers the other half.
02
Blended ROAS, every morning
One number across every ad network, with the same attribution window for all of them.
ROAS · 7-day window
03
Spend anomaly alerts
Get pinged when a campaign burns budget 2× faster than its trailing average.
Alert → Slack
Objects & tables
Exactly what gets synced
Kimo maps Brevo into clean, typed tables with primary keys and incremental cursors, so syncs stay fast and joins just work.
3 tables · 14 fields
Tables
campaigns
Incremental≈ 82,600 rows| Field | Type | Notes |
|---|---|---|
| campaign_id | id | Primary key |
| name | string | |
| status | enum | Low-cardinality dimension |
| budget | decimal | Measure |
| start_date | date | Incremental cursor |
Custom fields and extra objects are discovered automatically on each sync. Row counts are illustrative.
Sample model
From raw Brevo tables to a certified metric
A starter model Kimo suggests the moment Brevo is connected. Every join is editable.
Brevo · Paid acquisition
Spend and clicks joined with signups and revenue on UTM campaign and date.
- Brevocampaigns
- Google Analytics 4sessions
- PostgreSQLusers
Model
utm_campaign · date
Measuresspendsignups
Ad spend · last 30 days
$2.2K+4.7% wk/wk
Fictional data · hover the chart for daily values
Setup
Connect Brevo in 3 min
No engineers, no pipelines to maintain. Kimo asks for the minimum access it needs and tells you exactly what it will read.
- 1
Create a read-only key in Brevo
Use a dedicated key scoped to read access, so it can be rotated independently.
- 2
Paste it into Kimo
Keys are encrypted with a per-workspace key and never shown again.
- 3
Choose streams
Pick which objects to sync, starting with campaigns.
- 4
Validate and sync
Kimo tests the key, backfills history and keeps it fresh (hourly).
Read-only, encrypted, revocable. Credentials are encrypted with a per-workspace key, never logged, and can be rotated without breaking your models.
Connect Brevo
Step 2 of 3 · Kimo demo workspace
- Reaching host
- Authenticating
- Reading schema
Read-only access
Illustration only · placeholder values, never real secrets
Works great with
Pair Brevo with the rest of your stack
Kimo suggests these joins automatically when both sources are connected.
FAQ
Brevo questions, answered
By default Kimo syncs Brevo hourly. You can change the schedule per table, or trigger a sync manually from the connector page.
Brevo · API key · Hourly
See your Brevo data in Kimo in 3 min.
Try it on the live demo workspace first, then connect your own account when you are ready.
