Store survey scores as Brevo contact attributes
Post-purchase survey answers update the Brevo contact with a score and a comment you can segment a follow-up send on.
New feedback or survey form submitted
Update the Brevo contact with feedback attributes
One-directional. A submission triggers the action — nothing is written back into your form.
A satisfaction survey that lives only in a results dashboard changes nothing. The value sits in the difference between the person who scored you a nine and the person who scored you a four, and in sending each of them something appropriate.
Writing the score onto the Brevo contact turns that difference into a segment. Shops and subscription teams send the survey a week after purchase, then let the score decide whether the next email asks for a review or offers a call.
Setting it up
- 1
Send the survey link from Brevo a set number of days after purchase, so the audience is people who have actually received the thing.
- 2
In Brevo, create a number attribute such as NPS_SCORE, a text attribute for the comment, and a date attribute for when the survey was answered.
- 3
In Zapier, set the New Submission trigger to watch the satisfaction survey form.
- 4
Choose Brevo's create or update contact action matched on Email Address, so answers land on the profile that received the survey.
- 5
Map the 0 to 10 recommendation question into NPS_SCORE, and check Zapier passes it as a number, since Brevo rejects text in a number attribute.
- 6
Map the reason and improvement answers into text attributes, so the comment is readable next to the figure on the profile.
- 7
Build the segments in Brevo — nine and above, six and below — and attach each to its own follow-up email.
- 8
Submit a test response, confirm the score arrives as a number on your own contact, then turn the Zap on.
What maps where
Using the Customer Satisfaction Survey as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Brevo |
|---|---|
| Email Address | Matches the existing Brevo contact so the score lands on one profile |
| Name | FIRSTNAME, kept current on the contact |
| On a scale of 0–10, how likely are you to recommend us to a friend or colleague? | An NPS_SCORE number attribute, the basis for both segments |
| What is the main reason for your score? | A SCORE_REASON text attribute shown next to the number |
| Overall, how satisfied are you with your experience? | A SATISFACTION attribute for a second, coarser segment |
| What could we do better? | An IMPROVEMENT text attribute the product team reads |
Variations worth knowing
Filter in Zapier on a score of nine or ten and add only those contacts to a Brevo list that triggers a review request. Anyone below the threshold never sees the ask, which keeps it away from people mid-complaint.
Detractors deserve a human, not a sequence. Add a second action to the same Zap that emails the account owner whenever the score is six or below, running alongside the Brevo attribute update rather than replacing it.
If something isn't arriving
The attribute was created as text, or the answer arrives with its label attached rather than as a bare figure. Make NPS_SCORE a number attribute in Brevo, and use a Zapier formatter step to strip everything but the digits.
The address someone types is not always the one you emailed. Say in the question label that you want the address used at purchase, and merge the duplicate profiles in Brevo whenever a pair does appear.
Frequently asked questions
Can I chase people who ignore the survey?
Brevo handles that side. Build a workflow that waits a few days, checks whether the score attribute is still empty, and sends one reminder. The form does not chase anyone by itself; it only reports what comes back.
Should I let people answer anonymously?
You can, but this flow needs an email address to find the contact in Brevo. Where anonymity matters more than segmentation, keep that version of the survey out of the Zap and read the answers in responses instead.
Does a new score overwrite the previous one?
Yes. Attributes hold one value, so the latest survey replaces the last. Every response is still kept in the responses list, which means the history stays intact even though Brevo only shows the current figure.
Related automations
- Add newsletter signups to a Brevo list
Every footer signup becomes a Brevo contact in your newsletter list, with the topics they chose already attached.
- Add webinar registrations to a Brevo reminder list
Each registration becomes a Brevo contact on the list for that session, with company and job title already filled in.
- Log support requests on the Brevo contact
A help request creates or updates the Brevo contact and records what was asked, so follow-up email sends from one profile.
- Send gated guide downloads to a Brevo list
The download form adds the reader to a Brevo list with attributes for the asset and the date they asked for it.
- Start a Brevo nurture workflow for demo requests
A demo request creates the Brevo contact, records what the prospect wants to solve, and enters them into your welcome automation.
- Add buyers to a customers list after each order
Each order form submission adds the buyer to a Customers list in Constant Contact for updates and repeat-purchase emails.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free