Set up Sendinblue as a destination in RudderStack.
3 minute read
This guide will help you set up Sendinblue as a destination in the RudderStack dashboard. It also lists the configuration settings required to correctly send data from the supported sources to Sendinblue.
In the web device mode integration, that is, using JavaScript SDK as a source, RudderStack loads the Sendinblue native SDK from the https://sibautomation.com/ domain.
Based on your website’s content security policy, you might need to allowlist this domain to load the Sendinblue SDK successfully.
Get started
Once you have confirmed that the source platform supports sending events to Sendinblue, follow these steps:
From your RudderStack dashboard, add a source. Then, from the list of destinations, select Sendinblue.
Assign a name and click Continue.
Connection settings
To successfully configure Sendinblue as a destination, you will need to configure the following settings:
API Key: Enter your Sendinblue API key. Refer to the FAQ section for more information on obtaining the API key.
Client Key: Enter your Sendinblue client key. Refer to the FAQ section for more information on obtaining the client key.
Create contact via Double-opt-in: This setting is applicable only for the cloud mode. You can enable it to create a contact using the DOI flow. If enabled, enter the following settings:
Template ID: Enter the ID of the Double opt-in (DOI) template. Refer to the FAQ section for more information on obtaining the DOI template ID.
Redirection URL: Enter the URL of the web page where the user is redirected after clicking on the verification email.
Send user traits in track call: Enable this setting to send user traits to Sendinblue via the track call. RudderStack updates the contact’s attributes corresponding to their traits in the track call.
Map your traits to Sendinblue contact attributes: Enter the traits in RudderStack’s payload to be mapped to the contact attributes in Sendinblue.
Enter only the key name present in the event’s traits object.
For example, to map context.traits.email to Sendinblue’s EMAIL attribute, specify email in the Rudder payload trait key field and EMAIL in the Sendinblue contact attribute name field.
Client-side Events Filtering: This setting is applicable only for the device mode and lets you specify which events should be blocked or allowed to flow through to Sendinblue. For more information on this setting, refer to the Client-side Events Filtering guide.
This site uses cookies to improve your experience. If you want to learn more about cookies and why we use them, visit our cookie policy. We'll assume you're ok with this, but you can opt-out if you wish
Privacy Overview
This site uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are as essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.