Mailchimp Transactional setup
Testimonial Requests on Mailchimp Transactional
StoryProof lists Mailchimp among the email providers you can send review requests through. Mailchimp is two products, though. Its marketing plans send campaigns to an audience; one email to one customer, sent by another app, is the job of Mailchimp Transactional, the paid add-on once called Mandrill, which offers SMTP and an API. This page assumes Transactional, explains why, and covers its domain checks, which are stricter than most.
- Which Mailchimp product carries one-to-one requests
- DKIM, DMARC and ownership: all three are required
- The SMTP login Mailchimp Transactional expects
Transactional checklist
Get Mailchimp Transactional ready for StoryProof
Start by confirming the product question in your StoryProof settings, then work through Mailchimp. Transactional will not send at all until the domain passes every check, so test before the first real request.
Ticks stay in your browser. Nothing is saved or sent.
The problem, solved
The Mailchimp confusion, and what StoryProof does
- Problem 1
We already pay for Mailchimp
A marketing plan sends campaigns to an audience. It is not built to carry one request, to one customer, triggered by another app.
How StoryProof solves it
From Pro, StoryProof can send review requests through your own Mailchimp account. For one-to-one sending, Mailchimp’s product is Transactional, so expect to add it.
- Problem 2
Our customers are in a Mailchimp audience
People expect StoryProof to read the audience and pick who to ask.
How StoryProof solves it
Contacts and smart lists are on every plan in StoryProof, so requests go to people you have added there. Nothing here claims an audience sync with Mailchimp.
- Problem 3
Messages rejected as unsigned
Transactional refuses to send from a domain without valid DKIM and a DMARC policy, so a half-finished setup sends nothing at all.
How StoryProof solves it
Run StoryProof’s first request to yourself only after all three domain checks are green. The checklist above lists them.
- Problem 4
The form looks nothing like our emails
Mailchimp campaigns carry your brand. A plain request form feels like a different company.
How StoryProof solves it
Brand settings put your logo and colors on every form, wall and widget, on every plan.
- Problem 5
We built reminders as a Mailchimp journey
A separate reminder sequence in Mailchimp keeps going after the customer has already answered.
How StoryProof solves it
From Pro, StoryProof’s follow-ups send two reminders and stop once the customer leaves a testimonial. Requests themselves are email only, with no SMS.
Two Mailchimp products, two jobs
In StoryProof
Set it up
Step 1 of 5
Confirm what StoryProof asks for
Open the email provider options in your StoryProof settings and note what the Mailchimp choice needs before you buy the add-on.
Step 2 of 5
Add Mailchimp Transactional
Purchase the add-on and a block of emails from your Mailchimp account.
Step 3 of 5
Add and authenticate the domain
In Transactional go to Settings, Domains and add yours. Publish the two DKIM CNAMEs and a DMARC record, verify ownership, then run Test DNS Settings.
Step 4 of 5
Create the key and connect
Create an API key for StoryProof and enter it, or the SMTP login built from it, where StoryProof asks.
Step 5 of 5
Send a request to yourself
Check it arrives from your domain, then open the form and check your logo and colors are there.
Before you start
Read these first
Which Mailchimp is not stated by StoryProof
StoryProof’s plan list says "Mailchimp" without naming the product. This page assumes Transactional because it is Mailchimp’s SMTP and API sending service. Confirm in your settings.
Extra cost on the Mailchimp side
Transactional is a paid add-on billed by Mailchimp in email blocks, on top of a Standard or higher plan and on top of your StoryProof plan.
No audience sync claimed
Nothing here says StoryProof reads Mailchimp audiences or writes back to them.
Stricter domain rules
Without DKIM, a DMARC policy and ownership verification, Transactional will not send from the domain at all.
Steps follow Mailchimp’s docs
The Mailchimp steps follow its documentation as read on 2026-11-17 and have not been clicked through on a live account.
FAQ
Questions people ask
Short answers to what usually comes up next.
Is Mandrill the same thing?
Mandrill is the earlier name of Mailchimp Transactional, and its SMTP host still carries the mandrillapp.com name.
Can I skip the add-on and use my normal plan?
Not for one-to-one sending from another app, as far as Mailchimp’s docs describe. Check your StoryProof settings in case the Mailchimp option works differently.
What username does the SMTP login want?
Mailchimp says any string works because it is not used for authentication; it suggests the account’s primary contact email. The API key is the password.
Does Mailchimp Transactional check SPF?
Its domain page asks for DKIM, DMARC and ownership verification. The page we read does not mention an SPF record.
Still have a question? Ask the StoryProof team or book a demo.
Keep requests on your Mailchimp domain
Collect testimonials in StoryProof with requests that leave from your own domain through Mailchimp Transactional.
Sources
- Add or remove Transactional Email, Mailchimp Help. Checked 2026-11-17.
- Authentication and delivery, Mailchimp Transactional Developer Docs. Checked 2026-11-17.
- Mailchimp Transactional, Mailchimp Developer. Checked 2026-11-17.
- SMTP integration, Mailchimp Transactional Developer Docs. Checked 2026-11-17.
Last updated 2026-11-17.