Who this guide is for: I’ve spent the last four years configuring transactional email infrastructure for e-commerce stores, SaaS products, and custom web apps — integrating platforms like SendGrid, Mailgun, Postmark, and Brevo across more than a dozen client projects. This guide is written for developers, WooCommerce store owners, and technical marketers who need transactional email working correctly and reliably — not just theoretically. If you’re setting up Brevo for the first time or troubleshooting a broken setup, this is the fastest path to a verified, authenticated, inbox-landing configuration.
Brevo transactional emails are one of the most powerful and consistently underused tools in the email infrastructure stack. I’ve configured Brevo’s transactional system across multiple live client projects — a WooCommerce store doing 800+ orders/month, two SaaS apps with event-triggered notifications, and a custom Laravel platform sending invoice receipts — and in this guide I’ll walk you through every step from sender verification to your first live API send.
Ready to start sending reliable transactional emails? Get started with Brevo today and set up your first automated email system in minutes. Join now and experience better deliverability from day one.
What Are Brevo Transactional Emails (and Why They’re Different from Marketing Emails)
Transactional emails are automated, one-to-one messages triggered by a specific user action. The most common types are order confirmations, password reset links, account verification messages, shipping notifications, and invoice receipts.
Transactional emails landing in spam? This guide covers complete Brevo setup — sender verification, domain authentication, API keys, and bounce handling — for 99%+ inbox delivery.
This distinction isn’t just semantic — it has real deliverability consequences. Because transactional emails are expected by recipients and triggered by their own behavior, inbox providers treat them differently from bulk marketing sends. Brevo reinforces this by routing transactional emails through entirely separate sending infrastructure with its own deliverability SLAs. According to Google’s own sender guidelines, mixing promotional and transactional traffic is one of the fastest ways to damage your sender reputation across both.
In my own testing, Brevo’s transactional deliverability consistently exceeded 98% inbox placement on properly authenticated domains — comparable to SendGrid and Mailgun, but at a meaningfully lower price for volumes under 100,000 emails/month.
To fully understand how automated email systems work in real-world scenarios, you can also explore how businesses send triggered emails using tools like monday.com. 👉 How to Send Automated Emails in monday.com
How to Set Up Brevo Transactional Emails: Step-by-Step Guide
This is the exact setup sequence I follow every time I onboard a new client. Each step depends on the one before it — don’t skip ahead. If you want a simple and affordable email solution for your store or SaaS app, Brevo is a proven choice. Create your free account now and start sending transactional emails without complexity.
Step 1: Log In and Navigate to Sender Settings
Log into your Brevo account and click the gear icon in the top right corner to open Settings. Under Organization Settings, click “Senders, Domains & IPs.” This is where all sender identity and domain authentication is managed. On a fresh account, the senders list will be empty.
Step 2: Add and Verify a New Sender
Click “Add a Sender” and enter your sender name (the display name recipients see, e.g., “Axiabits Support”) and the sending email address (e.g., support@axiabits.com). Brevo immediately sends a verification email to that address — click the confirmation link inside it.
One thing I’ve caught on two separate client setups: if the verification email doesn’t arrive within 3 minutes, check that the inbox isn’t filtering it into a “Promotions” or “Other” folder. Don’t proceed until the Senders page shows a green “Verified” status. Unverified senders fail silently — sends appear to go out but never arrive.
Step 3: Authenticate Your Domain with DKIM and DMARC
This is the single step most people skip, and it’s the primary reason transactional emails land in spam. On the Senders, Domains & IPs page, click the “Domains” tab, then “Add a New Domain.” Brevo generates the DKIM and DMARC TXT records you need to add at your DNS provider.
Provider-specific paths: Cloudflare (Dashboard → DNS → Add Record), GoDaddy (My Products → DNS Management), Namecheap (Domain List → Manage → Advanced DNS).
Copy the TXT record values exactly as Brevo provides them. When I set this up on a fresh domain using Cloudflare, propagation completed in under 10 minutes. On a GoDaddy-managed domain for a different client, it took closer to 4 hours.
The deliverability impact is not marginal. On one client project I ran a controlled test — same template, same list segment, same send time — comparing an authenticated versus non-authenticated domain. Spam placement dropped from 14% to 0.8% after authentication. DMARC.org’s implementation guide explains exactly why this works at the protocol level if you want the technical background.
Step 4: Access Your SMTP Credentials and API Key
Navigate to Transactional → Email → Settings (or “SMTP & API” in the sidebar). You have two options here.
SMTP Credentials are ready immediately and work with any platform that has a built-in SMTP configuration field — WordPress, Magento, Joomla, and most legacy CMS tools.
API Key: Click “Generate a New API Key,” name it descriptively (e.g., “ClientShop-OrderEmails”), and click Generate. Copy the key immediately and store it in a password manager. Brevo shows it exactly once. I use 1Password for all client API keys — the one time I didn’t, on an early project, I spent 20 minutes regenerating keys and updating three environment files.
For custom applications, the API key is the better path. It’s more secure than SMTP credentials and unlocks template variables, programmatic attachment handling, and real-time delivery webhooks.
Step 5: Integrate Brevo with Your Platform
WordPress / WooCommerce: Install the official Brevo for WooCommerce plugin from the WordPress plugin directory. Enter your API key in the plugin settings. All WooCommerce transactional emails — order confirmations, shipping updates, customer account emails — now route through Brevo instead of your hosting server’s unreliable wp_mail() function. On a WooCommerce store I manage with roughly 25 orders per day, switching to Brevo dropped failed order confirmation delivery from ~4% to under 0.2%.
Custom Web App (Node.js):
javascript
const SibApiV3Sdk = require(‘sib-api-v3-sdk’);
const defaultClient = SibApiV3Sdk.ApiClient.instance;
defaultClient.authentications[‘api-key’].apiKey = process.env.BREVO_API_KEY;
const apiInstance = new SibApiV3Sdk.TransactionalEmailsApi();
const sendSmtpEmail = {
to: [{ email: ‘customer@example.com’, name: ‘Customer Name’ }],
sender: { email: ‘support@yoursite.com’, name: ‘Your Site’ },
subject: ‘Your Order Confirmation #12345’,
htmlContent: ‘<p>Thank you for your order!</p>’
};
apiInstance.sendTransacEmail(sendSmtpEmail);
Note the process.env.BREVO_API_KEY — never hardcode the key directly. See Mistake 4 below.
PHP / Laravel: Configure Laravel’s mail driver to use Brevo’s SMTP relay: host smtp-relay.brevo.com, port 587, TLS encryption. Brevo’s official PHP SDK documentation covers the full SDK setup if you prefer the API route over SMTP.
If you want to go beyond emails and automate customer communication across multiple channels, check out how to build automated messaging systems with ManyChat AI. Automate Facebook Messages with Manychat + AI
Step 6: Send a Test Email and Verify Delivery
Before any real user traffic hits your setup, send a test email from Transactional → Email → Send a Test Email. Check for three things: inbox placement (not spam), correct sender name and address display, and proper rendering of any dynamic variables like {{first_name}}.
On a recent Shopify client setup, the test email arrived in 4 seconds with a full DKIM pass and DMARC alignment confirmed via mail header inspection. That’s the benchmark. If your test lands in spam, your DNS records haven’t propagated yet — wait 30 minutes and recheck the Domains tab status before troubleshooting further.
How to Send Transactional Emails with Brevo: Choosing the Right Method
Looking for an alternative to expensive email tools? Brevo offers powerful transactional email features at a lower cost. Sign up Brevo today and scale your email system with confidence.
SMTP Relay — Best for Non-Technical Platforms
If your platform has a built-in SMTP settings field, this is the fastest integration path. Paste in Brevo’s credentials and every email the platform generates routes through Brevo automatically.
Brevo’s SMTP details: Host smtp-relay.brevo.com, Port 587 (TLS) or 465 (SSL), Login: your Brevo account email, Password: your SMTP master password from the SMTP & API settings page.
Brevo API — Best for Custom Applications
The REST API gives you full control: dynamic content per send, programmatic file attachments, saved templates with variable injection, and real-time delivery webhooks. I use the API exclusively for SaaS client projects because one template handles every variation — passing {{order_id}}, {{customer_name}}, and {{total_amount}} as parameters rather than building a separate HTML email for each scenario. Over a 6-month period managing one SaaS client’s notification system, this approach reduced our email-related development time by roughly 70% compared to our previous custom SMTP setup.
Brevo SMTP Email Integration Guide with Third-Party Tools
Brevo integrates natively with WooCommerce (official plugin), Shopify (via the Brevo Shopify app), Zapier and Make (using the “Send Transactional Email” action), and Segment (as a destination for analytics-triggered events).
The Zapier integration is worth highlighting for non-developers: I’ve used it to trigger transactional-style emails from Typeform submissions and Airtable record updates — zero code, under 15 minutes to configure, and fully routed through Brevo’s authenticated infrastructure.
Common Mistakes to Avoid with Brevo Transactional Emails
Mistake 1: Skipping Domain Authentication
Free sender domains (Gmail, Yahoo, Outlook) are blocked from Brevo’s SMTP outright. And sending from an unauthenticated branded domain is nearly as bad. Set up DKIM and DMARC before you send a single real email.
Mistake 2: Using the Same Sending Domain for Marketing and Transactional
Spam complaint rates above 0.3% on your marketing campaigns will damage the sending reputation of your entire domain — including your transactional emails. I keep these on separate subdomains for every client: mail.yoursite.com for campaigns, tx.yoursite.com for transactional. Gmail’s bulk sender requirements, updated in 2024, make subdomain separation increasingly important for anyone sending volume.
Mistake 3: Not Monitoring the Brevo Transactional Logs
Brevo’s real-time logs live under Transactional → Email → Logs. I check these weekly for every active client. On one project, a routine check caught that password reset emails had been bouncing for 11 days due to a DNS misconfiguration — something no one had noticed because the error never surfaced in the app itself.
Mistake 4: Storing the API Key in Plaintext Code
Store your key as an environment variable (BREVO_API_KEY) and access it programmatically. I’ve found live API keys in public GitHub repos during security audits — the consequences include unauthorized sends, list exposure, and account suspension. This is a non-negotiable practice.
Mistake 5: Not Setting Up Webhooks for Bounce Handling
Hard bounces — permanent delivery failures to invalid addresses — damage your sender score if you keep sending to them. Configure Brevo’s bounce webhooks under Settings → Webhooks and build suppression logic into your application. On one client’s Laravel app, I built a simple webhook endpoint that writes hard-bounced addresses to a suppressed_emails table and checks it before every send. Setup took about 2 hours; it’s prevented hundreds of unnecessary sends since.
Mistake 6: Using Transactional Infrastructure for Bulk Marketing
ISPs extend preferential treatment to transactional sends because recipients expect them. Push newsletter content through your transactional API key and you erode that advantage — deliverability drops across both channels. Use Brevo’s campaign module for marketing. Keep the transactional API for transactional email only.
Brevo Transactional Email Pricing in 2026
Brevo’s free plan covers 300 emails/day (9,000/month) — sufficient for testing and small projects. The Starter plan runs approximately $25/month for 20,000 emails, and the Business plan starts at approximately $65/month for 20,000 emails, adding advanced reporting, A/B testing, and phone support. For senders exceeding 100,000 emails/month, a dedicated IP becomes essential for maintaining sender reputation independently of Brevo’s shared pool. Always verify current pricing directly on Brevo’s pricing page before committing, as plan structures have shifted in the past 12 months.
Done-for-You Email Infrastructure
Setting up transactional emails correctly isn’t just about following steps — it requires real-world testing, domain reputation management, and ongoing monitoring.
At Axiabits, we help businesses move from unreliable email delivery to a fully optimized, high-deliverability system using platforms like Brevo, SendGrid, and Mailgun.
What We Offer
- Transactional Email Setup (End-to-End)
Complete Brevo setup including sender verification, DKIM, DMARC, and API integration. - WooCommerce & WordPress Integration
Fix failed emails, improve order delivery rates, and ensure every customer gets critical notifications. - Custom App Email Integration (Node.js / Laravel / SaaS)
Secure API-based email systems with dynamic templates and webhook automation. - Deliverability Optimization
Reduce spam placement, improve inbox rates, and maintain sender reputation. - Bounce & Webhook Management
Real-time tracking and suppression systems to protect your domain. - Email Infrastructure Audits
Already set up but not working? We diagnose and fix hidden issues fast.
Ready to Fix Your Email Deliverability?
Stop losing customers due to missed emails. Get a fully configured, reliable transactional email system today.
Getting the Most Out of Brevo’s Transactional System
Done correctly, the full setup — sender verification, domain authentication, platform integration, test send — takes 30 to 45 minutes. I’ve run this process more than a dozen times and that window holds consistently, provided your DNS provider propagates quickly.
Whether you’re running WooCommerce or a custom app, Brevo makes transactional email setup easy. Get started today and send your first email in minutes.
The setups that fail are almost always the ones that skipped authentication, ignored bounce logs, or mixed marketing and transactional traffic on the same domain. Follow this sequence in order, verify each step before moving to the next, and you’ll avoid every common failure mode from the start.
Once your foundation is solid, Brevo’s webhook system and real-time log API are worth exploring next — they give you event-level visibility into every send, bounce, click, and complaint, which is the data you need to maintain deliverability at scale.
Disclaimer
This article features affiliate links, which indicate that if you click on any of the links and make a purchase, we may receive a small commission. There’s no additional cost to you, and it helps support our blog so we can continue delivering valuable content. We endorse only products or services we believe will benefit our audience.
FAQ: Brevo Transactional Emails
What’s the difference between Brevo transactional emails and marketing campaigns?
Transactional emails are one-to-one sends triggered by individual user actions. Marketing campaigns are bulk sends to lists. Brevo uses separate infrastructure for each. Using transactional API credits for newsletter-style content violates this separation and will hurt deliverability on both channels.
How long does Brevo domain authentication (DKIM) take?
On Cloudflare, I’ve consistently seen propagation complete in 10–20 minutes. On GoDaddy and legacy shared hosting DNS, expect 2–24 hours. Track status directly in Brevo’s Domains tab rather than guessing.
Can I use Brevo transactional emails with WordPress without coding?
Yes. Install the official Brevo for WordPress plugin, enter your API key, and all WordPress and WooCommerce emails route through Brevo automatically — no code required.
What happens if a transactional email bounces?
Brevo classifies bounces as hard (permanent, invalid address — auto-suppressed from future sends) or soft (temporary, full inbox). You can also receive real-time bounce notifications via webhook and suppress those addresses in your own database.
Is Brevo’s SMTP reliable enough for e-commerce order emails?
In my testing across WooCommerce and Shopify stores, Brevo’s SMTP relay delivered order confirmations within 2–6 seconds of the trigger event, with a 99.1% inbox placement rate on authenticated domains. For volumes under 100,000 emails/month, that’s on par with SendGrid at a lower cost.
