Brevo as your sending service
Testimonial Requests Through Brevo SMTP
If your newsletters and receipts already go out through Brevo, your testimonial requests can too. From a paid StoryProof plan, review requests can leave from your own domain through your own SMTP account. This guide covers the Brevo half from Brevo’s docs: an authenticated domain, a sender on it, an SMTP key and the relay settings, and then a test that proves the request really left through Brevo.
- Domain authenticated in Brevo first
- An SMTP key, never an API key
- A test request you inspect yourself
Brevo checklist
Get Brevo ready to carry your requests
Do the Brevo side first, in this order. Items follow Brevo’s developer docs (read) and Brevo help centre articles seen as search summaries on 2026-11-17, because the help centre blocked automated reading.
Ticks stay in your browser. Do not type keys or passwords anywhere on this page.
The problem, solved
Why route requests through Brevo at all
- Problem 1
Customers did not recognise the sender
A request from an unfamiliar address looks like marketing from a stranger, and it is easy to ignore or delete.
How StoryProof solves it
From Pro, review requests can leave from your own domain through your own SMTP account, such as Brevo.
- Problem 2
Our domain is already set up in Brevo
You did the authentication work for newsletters. Sending requests elsewhere throws that work away for the one email you most want opened.
How StoryProof solves it
Point StoryProof at the same Brevo account, so requests use the domain you already authenticated there.
- Problem 3
Reminders need to come from the same place
A first request from your domain and a reminder from somewhere else confuses customers and splits replies.
How StoryProof solves it
From Pro, follow-ups send a reminder after three days and a last email four days later, stopping once the customer leaves a testimonial. Test one reminder through Brevo as well.
- Problem 4
The form should match the email
A request from your domain that opens an unbranded form feels like a hand off to another company.
How StoryProof solves it
Brand settings put your logo and colors on every form, wall and widget, on every plan.
- Problem 5
Who should receive the requests?
Brevo holds your marketing lists, but not everyone on them is a customer worth asking.
How StoryProof solves it
Contacts and smart lists are on every plan in StoryProof, so requests go only to the people you add there.
In StoryProof
Switch your requests over to Brevo
Step 1 of 4
Authenticate the domain in Brevo
Add the Brevo code, DKIM and DMARC records Brevo gives you, and wait for the green ticks on your sender.
Step 2 of 4
Generate an SMTP key
Create a key just for StoryProof on Brevo’s SMTP tab, so you can revoke it without affecting anything else.
Step 3 of 4
Enter the relay in StoryProof
Add the host, port, login, key and From address where your StoryProof settings ask for your own SMTP account.
Step 4 of 4
Send yourself a request
StoryProof sends requests by email only. Send one to your own address, check the headers, then send one to a colleague on a different mail provider.
Before you start
Before you switch
A paid StoryProof plan
Your own email provider starts on Pro.
Brevo steps as of 2026-11-17
The Brevo details follow Brevo’s docs as read or seen in search summaries on 2026-11-17. They have not been followed on a live account by us, and Brevo is rolling out a new domain setup flow.
Brevo’s limits and pricing apply
Sending volume, daily caps and costs on the Brevo side come from your Brevo plan, not from StoryProof.
Unauthenticated domains get rewritten
Brevo’s help says that until a domain is authenticated, it may replace the domain in your From address with its own. Finish authentication before going live.
No Brevo integration beyond SMTP
This page claims only that requests can go through your SMTP account. It does not sync Brevo contacts, lists or campaigns with StoryProof.
FAQ
Questions people ask
Short answers to what usually comes up next.
Is this the same as Sendinblue?
Yes. Sendinblue renamed itself Brevo, and the SMTP relay now lives under Brevo’s SMTP and API settings.
Can I use a Brevo API key instead of an SMTP key?
No. Brevo’s docs say the SMTP relay takes an SMTP key, not an API key.
Which port should I choose?
Start with 587. Brevo lists 2525 as another option and 465 for SSL or TLS. Use whatever your StoryProof settings and network accept.
Will this fix requests landing in spam?
It helps the message look like it comes from you, but filtering is decided by the recipient’s mailbox. The spam page covers the other causes.
Still have a question? Ask the StoryProof team or book a demo.
Ask from the domain customers know
Collect testimonials with StoryProof and send the requests through the Brevo account you already trust.
Sources
- SMTP integration, Brevo developer docs. Checked 2026-11-17.
- Authenticate your domain with Brevo (Brevo code, DKIM, DMARC), Brevo help centre. Checked 2026-11-17.
- Troubleshooting: Issues with Brevo SMTP (login and host), Brevo help centre. Checked 2026-11-17.
Last updated 2026-11-17.