What a configuration could hand over
Three things have to happen the moment a configuration is submitted: confirm to the customer, alert the salesperson, and create a contact for later. Brevo does all three, so this needs neither three tools nor three connections.
Transactional email
The customer's confirmation could go out as a transactional email from a Brevo template, with the configurator filling in dimensions, price and the 3D preview link as parameters.
Contact and attributes
The customer could be created as a contact with attributes for product and price tier, which you set up in Brevo beforehand.
Lists
Depending on the consent given, the contact could be added to a campaign list or kept out of it.
CRM deals
If you also use Brevo as a CRM, the enquiry could become a deal in a chosen pipeline and stage, valued from the configurator and linked to the contact.
What we need to connect it
Access would use a v3 API key in the api-key header; you create the key under SMTP & API in the settings and it is shown only once.
The sending domain has to be authenticated in Brevo with DKIM and DMARC records, otherwise Brevo replaces the domain in the sender address with its own.
You prepare the contact attributes and the confirmation template in Brevo, and we supply the list of parameters it can receive.
For testing we use a separate list and test addresses, so trial contacts stay apart from live ones.
Worth deciding up front
- An enquiry confirmation is a transactional message and can go to a contact without marketing consent. Adding them to campaigns is governed by consent separately.
- Attributes must exist in Brevo before anything is written, and Brevo silently drops a value of the wrong type, such as text in a date field. Types are therefore aligned in the mapping.
- If a contact with the same email already exists, we agree whether its attributes are updated or left as they are.
Questions about this connection
Can the confirmation look like our other emails?
You would design the template in Brevo's editor so it looks like your other emails, and the configurator would only fill in the data from the configuration.
Where would the data be processed?
Brevo is a European company; check the processing terms in its data processing agreement. Which configuration data goes to Brevo is decided according to your consents.
Other integrations
Put Brevo to work in your sales.
Tell us what you sell and how an enquiry is handled today. On the demo you will see the configurator, and we will go through which data could flow from it into your system.