Brevo tag for server Google tag manager

Brevo (formerly Sendinblue) is an e-mail and SMS platform with an API for contacts. If your sign-up form is custom, or you want a sign-up to feed Brevo and your ad platforms at once, a server container can do the Brevo part safely. This page shows the pattern. Check Brevo's API documentation for the current endpoints. It parallels Mailchimp from a server container.

What you need

• A Brevo API key.
• The ID of the list to add contacts to.
• A sign-up event that carries the e-mail and a consent flag.

Try it

Works with your stack

Grab a logo and throw it. These are the tools Open Tracked already talks to.

Grab one. Throw it.

The request

const sendHttpRequest = require("sendHttpRequest");
const JSON = require("JSON");
const getEventData = require("getEventData");

sendHttpRequest("https://api.brevo.com/v3/contacts", (statusCode) => {
  (statusCode === 201 || statusCode === 204) ? data.gtmOnSuccess() : data.gtmOnFailure();
}, {
  method: "POST",
  headers: {
    "api-key": data.apiKey,
    "Content-Type": "application/json",
    "Accept": "application/json"
  },
  timeout: 4000
}, JSON.stringify({
  email: data.email,
  attributes: { FIRSTNAME: data.firstName, SOURCE: data.source },
  listIds: [data.listId],
  updateEnabled: true
}));

A new contact returns 201, and an update with updateEnabled returns 204. Allow https://api.brevo.com/* in the template permissions.

Consent and opt-in

• Trigger only when the visitor ticked a marketing consent box.
• For double opt-in, use Brevo's double opt-in flow so the contact confirms by e-mail.
• Store the consent source and date in an attribute.
• Never re-subscribe someone who unsubscribed.

For online stores

Orders from your store, back to the ad that earned them

Your store sends the order once. Open Tracked passes it on to each ad platform, cleaned and deduplicated.

Open Trackedorder tracked

+1 order

Errors

Test

1. Send a test sign-up in server Preview with a safe address.
2. Check the tag status and response.
3. Check the contact and its attributes in Brevo.
4. Send the same address again: it should update, not fail.

A realistic example

A publisher has a newsletter sign-up form built into its theme, and wants sign-ups to reach Brevo, Meta and its own database without exposing a key in the page. It sends one sign_up event to its tagging server with the e-mail, the consent flag and a source. The container checks the flag, adds the contact to Brevo with the source as an attribute, and sends a hashed copy to Meta for audience building. A month later the team compares sign-ups by source in Brevo and finds that the in-article form brings three times as many as the footer form. One event now feeds three systems, and the Brevo key is stored where only the server can read it. That is the real benefit of doing it in the container.

Keep it healthy

Check the tag's responses in the logs after launch. A change in an attribute name in Brevo, or a revoked key, will show up as errors. Put a weekly reminder in the calendar to compare the number of sign-ups in your site's analytics with the number of new contacts in Brevo. A gap means something is failing quietly.

Frequently asked questions

Fix your tracking at the source

Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.

Start freeMore in Integrations →

Written by

The Open Tracked team

We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?

Write to us Read the docs