SiteOps.

Connect Brevo to SiteOps

Want to start sending real email today, without a card on file? That is Brevo's pitch, and it is why small teams keep landing on it. Formerly Sendinblue, it is a full platform rather than a bare pipe — contact lists, segments, campaigns and transactional sending in one account, with a free tier that genuinely sends, up to a daily cap.

For SiteOps, Brevo plays two roles. First, it is the way out: SiteOps drafts and schedules emails, and once Brevo is connected the approved ones actually send, from a sender you verified, with sent, opened and clicked counts flowing back. Second, the segments you already maintain in Brevo become pickable audiences — alongside everyone and the cohorts SiteOps builds from your own site's events.

The setup is one API key and one verified sender. The key lives under the account menu, in SMTP & API — Brevo shows it a single time when you generate it. The sender is either an address you confirm by email or, better, a domain you authenticate with a couple of DNS records. Until both the key and a from address exist, scheduled emails wait safely as drafts.

The records Brevo asks for — DKIM plus its verification code

Set it up, step by step

0 of 8 done

    1. Senders, domains & dedicated IPs
    2. Domains
    1. Account menu
    2. SMTP & API
    3. API keys
    1. SMTP & API
    2. API keys
    3. Generate a new API key
  6. The API key's journey — the API keys tab, not the SMTP one
    1. Settings
    2. Brevo
    3. Save

Let an agent do it

An agent with access to your DNS can add Brevo's domain authentication records for you.

Prompt for your agent
Add the Brevo domain authentication records to my DNS.

1. I added <my sending domain> under Senders, domains & dedicated IPs in Brevo, and its authentication screen lists the DNS records to add — a DKIM TXT record (host like mail._domainkey) and a Brevo verification code TXT record. Here they are exactly as displayed: <each record: type, host, value>.
2. Open the DNS zone for the domain at <my DNS host, e.g. Cloudflare or the registrar> and add each record with the exact type, host and value. Watch for the host trap: if the DNS host auto-appends the domain, enter only the prefix (for example mail._domainkey), so the host does not end up doubled.
3. Check each record resolves: dig TXT <host> +short for each entry.
4. Tell me when they resolve so I can press Authenticate in Brevo.

Creating the Brevo account, confirming sender emails, generating the API key and pasting it into SiteOps stay with you.

If something does not work

The key saved but my emails still sit as drafts
The from address is the missing half. Open the Email section in SiteOps settings and set the sender name and address — the address has to be a sender you verified in Brevo. The draft's note says exactly which half the gate is waiting on.
Brevo rejected the key I pasted
Most often it is the SMTP credential instead of an API key — they live on neighbouring tabs of the same page. Go to the account menu, SMTP & API, the API keys tab, and generate a proper key (it starts with xkeysib-).
My send stopped partway through the list
That is the free tier's daily cap doing its job — Brevo pauses sending when the day's allowance runs out and resumes the next day. If your list is regularly bigger than the cap, a paid Brevo plan removes it; nothing needs changing in SiteOps.
My segment does not show up as an audience
SiteOps lists the segments your key can see, refreshed periodically. If a brand-new segment is missing, give it a few minutes and reopen the audience picker. Segments live and stay in Brevo — SiteOps references them by name at send time, so their membership is always current.
My first emails landed in spam
A confirmed single address is the minimum; authenticated DNS is what inboxes respect. Add the DKIM and verification records from the Senders, domains & dedicated IPs screen (the agent prompt above does the pasting), then send steadily and write like a person. Reputation builds over a few weeks.
I connected Brevo and another email provider — which one sends?
Whichever provider the 'Sends go through' picker in SiteOps Settings names. Several mailers can stay connected at once — only the picked one sends, and the rest stay readable, so your Brevo segments remain pickable audiences even when another service does the sending.

Set up once, see everything every morning

Get started