Newsletter Sendinblue - WordPress Plugin

How to Set Up Newsletter Sendinblue to Deliver Newsletters Through Brevo

Newsletter Sendinblue is the bridge between The Newsletter Plugin in WordPress and the Brevo service, formerly known as Sendinblue. This guide does not cover email marketing in general. Instead, it focuses on the practical side of this specific delivery integration: what to prepare before installation, where to get the key, why a verified sender matters, how to run a test send, how to validate the result, and how to tell the difference between a plugin issue and a problem with the domain, API, or mail service.

This article is intended for a site owner, editor, webmaster, or administrator who already uses WordPress and wants Newsletter to send mail through an external delivery service instead of standard hosting email. That approach is especially useful when the site has subscribers, segments, regular campaigns, emails with personalized links, and a need to handle bounced addresses properly.

It is important to understand the product's role: Newsletter Sendinblue does not replace Newsletter itself, and it does not turn WordPress into a full Brevo interface. It solves a narrower problem - it passes emails created in Newsletter to Brevo through a delivery integration. Because of that, you need to validate the entire chain: WordPress, the main Newsletter plugin, the sender identity, the API key, Brevo account limits, DNS authentication, and the test email.

What this integration actually does

A standard WordPress installation can send system emails, but bulk mailing is a different workload. In a newsletter workflow, it is not enough to trigger the send function. You also need to make sure the email reaches every subscriber, does not hit hosting limits, does not lose personalized links, does not keep sending to invalid addresses, and gives you enough visibility to see where something failed. That is why Newsletter Sendinblue should be treated as a transport layer for newsletters, not as an email designer or a signup form.

The Newsletter Plugin stores subscribers, lists, statuses, forms, the email editor, targeting rules, and service links. When Newsletter sends a campaign, it has to generate a separate email for each subscriber, because those emails may include individual unsubscribe links, profile links, click tracking, and confirmation actions. The Brevo integration is there so those personalized emails go out through an external delivery service instead of your hosting provider's mail limits.

This leads to the main practical conclusion: a successful Newsletter Sendinblue setup is not proven by activating the plugin, but by completing a full end-to-end test from the sender identity to the inbox. If the key is entered but the sender is not verified, the email may never go out. If the sender is verified but the domain is not authenticated, deliverability may suffer. If the email is delivered but the links lead to the homepage without performing any action, the issue may be cache behavior or the way Newsletter service links are formatted.

What stays inside WordPress

Everything related to newsletter management stays in WordPress: subscribers, lists, forms, the editor, test subscribers, address statuses, targeting, email copy, and the logic behind service links. That is convenient if your team already works in the admin dashboard and does not want to move the entire process into a separate service. But convenience does not remove the need for discipline: subscriber lists still need cleanup, test emails still need to go out before a campaign, and access to Newsletter admin screens should be limited to roles that actually need to work with email campaigns.

What Brevo handles

In this setup, Brevo is responsible for delivery through its API and service infrastructure. That matters for Newsletter because the integration does not use the Campaign API. It uses transactional delivery, where each email is sent as an individual personalized message. That is why this guide discusses the verified sender, the API key, domain authentication, account limits, and delivery reports. These are not decorative settings - without them, it is hard to understand why an email was or was not delivered.

Who Newsletter Sendinblue is for, and when a different path makes more sense

This integration is a good fit for sites where the content and subscriber base live in WordPress, but email delivery needs to be more reliable than standard hosting mail. That could be a blog with regular newsletter issues, an expert site with interest-based segments, a small store, an educational project, a club, or a media site where the administrator wants to build emails in Newsletter and send them through an external service.

It is especially useful when a site already has a subscriber base in Newsletter, with forms and lists already set up, but hosting-based delivery is running into limits, a slow queue, or poor deliverability. In that case, Newsletter Sendinblue lets you keep the editorial workflow inside WordPress and replace only the transport layer. That is simpler than migrating your entire subscriber database and templates into another system, but it still requires proper sender and domain validation.

The integration may be unnecessary if you want to run all marketing directly inside Brevo, building campaigns, automations, segments, and forms in the Brevo interface itself. In that case, it makes more sense to look at the official Brevo plugin for WordPress or to work directly in the service. Newsletter Sendinblue is useful not as "another Brevo dashboard," but as a bridge for teams that have chosen Newsletter as the primary newsletter hub inside WordPress.

There is also a third option: if you only need a very simple newsletter, have a small list, and send infrequent emails, you can start with basic Newsletter and test delivery through your current mail setup. But once you have regular campaigns, deliverability complaints, bounced mail, server limits, or domain authentication requirements, an external delivery service stops being a luxury and becomes a normal technical part of the project.

What to check before installation and connection

Before installing the add-on, it helps to do a short technical prep pass. It saves more time than troubleshooting later, because most sending issues are not caused by the installation itself, but by a sender mismatch, an unverified domain, a conflicting SMTP plugin, or the assumption that external delivery will somehow fix list quality problems on its own.

The main Newsletter plugin and admin access

Newsletter Sendinblue works as an add-on for The Newsletter Plugin, so the main Newsletter plugin must already be installed and configured. In WordPress, make sure the main plugin is active, its menu is accessible, a public Newsletter page exists with the correct shortcode, and the sender in the main settings is a real address on your own domain. Free mailbox addresses are best avoided as the primary sender for newsletters sent from your site's domain.

If editors or marketers will be working with Newsletter, decide in advance who is allowed to change delivery settings. Integration panels, API keys, and SMTP parameters are sensitive settings. They should not be available to every role just because someone needs to write the email copy.

Brevo account, sender identity, and API key

To connect the integration, you need a Brevo account, a verified sender, and an API key. In the Brevo interface, you typically add a sender or domain first, then confirm ownership. After that, you generate an API key and paste it into the Newsletter Sendinblue add-on settings. The Newsletter Plugin documentation specifically notes that the sender in Brevo must match the sender configured in Newsletter. This is a simple but common source of errors: the key exists, but the sender address is different.

The API key should be treated as a secret. Do not paste it into public notes, articles, support tickets without masking it, or screenshots. If you suspect the key has been exposed, rotate it in Brevo and update it in the plugin settings.

Domain authentication and DNS

SPF, DKIM, and DMARC are not configured inside Newsletter Sendinblue. They are DNS records and mail infrastructure settings. But they are exactly what helps mailbox providers understand that your domain is actually authorized to send through the selected service. If you plan to send any meaningful volume, do not postpone domain authentication: connect the sender first, review Brevo's DNS instructions, and only then send a test campaign.

If you do not have DNS access, send your domain administrator the required record list from Brevo in advance. Do not try to "fix" domain authentication through WordPress settings - that is not the right layer. WordPress can create the message and pass it to the API, but it cannot publish DNS authentication for your domain.

Subscriber list and mailing consent

A delivery integration does not make a subscriber list healthy by itself. Before the first launch, review subscriber statuses: confirmed, unconfirmed, unsubscribed, complained, and bounced. If you imported a list from an older system, do not send a large email to every address right away. Start with a small segment, review complaints, bounces, and opens, and only then expand the volume.

Quick pre-connection checklist: the main Newsletter plugin is active, the sender uses a domain-based email address, the Brevo account is accessible, the sender is verified, the API key is created, DNS records are prepared, and the subscriber list has been cleaned of obviously invalid addresses.

Installing the add-on and running the first check in WordPress

Newsletter add-ons are installed like regular WordPress plugins. If you use Addons Manager, you can install the add-on from the Newsletter panel. If you go the manual route, download the add-on ZIP archive and install it through the standard WordPress screen: Plugins - Add New - Upload Plugin. After activation, the add-on should appear in the Newsletter menu as a separate delivery setting.

Do not edit the add-on files manually. An update will restore the original code, and any changes will be lost. If you need to change email behavior, look for built-in Newsletter settings, email template settings, lists, targeting, form CSS, or documented WordPress mechanisms. With Newsletter Sendinblue, the typical job is not to change code, but to correctly connect the API, sender identity, and test delivery.

Step-by-step installation

1. Make sure the main The Newsletter Plugin is installed and opens correctly in the WordPress admin area.
2. Install the Newsletter Sendinblue add-on through Addons Manager or by uploading the ZIP archive.
3. Activate the add-on on the WordPress plugins page.
4. Open the new add-on settings page from the Newsletter menu.
5. In Brevo, create or verify the sender, then generate the appropriate API key.
6. Paste the key into the add-on settings and save.
7. Confirm that the sender in the main Newsletter settings matches the verified sender in Brevo.
8. Send a test email through the Newsletter diagnostics page or a test campaign.

What counts as a successful initial check

Success is not just seeing a "saved" message in the admin panel. After the initial setup, you need at least one real-world result: a test email arrives in the inbox, Brevo records a sending attempt or delivery event, Newsletter shows no connection error, and the sender shown in the received email looks the way you expected. If the email lands in spam, that is not necessarily a plugin problem, but it is a signal to review the domain, content quality, and sender reputation.

Configuring the sender, API, and delivery behavior

The most important part of the setup is how Newsletter determines the sender and how Brevo accepts the email through the API. If those pieces do not line up, the integration may look "almost ready" while real emails are rejected, sent from the wrong address, or fail with confusing errors. That is why the setup should be validated step by step, not guessed by feel.

Sender identity in Newsletter

Open the main Newsletter settings and review the sender name and sender email. It is best to use an address on your site's or brand's domain, such as This email address is being protected from spambots. You need JavaScript enabled to view it.. This should be a real address or alias that can be verified and that your team can receive replies from if you use it as a contact address. Do not use Gmail, Outlook, or another free mailbox as the sender for campaigns sent from your site's domain unless you have a separate, correctly configured SMTP setup for that address.

If the site already uses an SMTP plugin, check whether it overrides the sender name or email address. Newsletter has its own sender settings, the SMTP plugin may have its own, and WooCommerce may define its own sender for service emails. For Newsletter Sendinblue, the key is understanding which system actually sets the sender identity in the specific test you are running.

Sender identity in Brevo

In Brevo, add the same sender email address and complete the verification process. If a domain is configured in Brevo, check the status of the domain and its DNS records. This is not the stage for a full campaign. First, send a test to one or a few internal addresses and see how the email appears across different mailbox providers.

API key

The API key is entered in the Newsletter Sendinblue add-on settings. Use a key created specifically for this connection, not a shared secret that is already in use across several projects. That makes it easier to revoke access if the site is migrated, the contractor changes, or you suspect a leak. After entering the key, save the settings and run a delivery test.

If Brevo lets you scope the key by purpose or rotate it when the administrator changes, use that practice. This guide does not provide commands or expose secrets: the key should exist only in the Brevo panel and in the site's protected settings.

Speed and limits

Newsletter can control sending speed, and external delivery services have their own account limits and policies. Do not set the maximum speed just because the API responds quickly. For a new sender, it is safer to start with moderate volume, review the errors, and gradually increase the pace. That matters even more for lists that have not received emails in a long time.

If you use Speed Control or Newsletter's general rate limits, remember that WordPress-side throttling and delivery-service limits do not replace each other. Newsletter limits help avoid sudden sending spikes and excessive site load, while Brevo limits determine how many emails the service will accept and under what policy.

Logs and diagnostic mode

Newsletter includes logging levels and diagnostic panels. Raise the log level only while troubleshooting. Debug logs can grow quickly, and a permanent debug mode is unnecessary on a production site. A good workflow is to enable detailed logs, repeat a single test, save your observations, and then return to normal mode.

Setup rule: change only one variable at a time - the sender identity, key, speed, link format, or DNS. If you change everything at once, you will not know which setting fixed or broke delivery.

Why this uses transactional delivery instead of a standard Brevo campaign

The add-on documentation explicitly explains that Newsletter has to send one email per subscriber because each message contains personalized elements: tracking links, unsubscribe actions, profile links, and other individual data. That is why this integration uses Brevo transactional delivery instead of creating a campaign inside Brevo. This is not a technical detail - it is the key to understanding the product's logic.

If you think of a newsletter as one "finished campaign," it is tempting to send the service a single template and a list of addresses. But Newsletter works differently: it decides who should receive the email, inserts subscriber-specific data, generates the required service links, and passes the finished email to the delivery layer. In this scenario, Brevo does not manage Newsletter's lists or decide who should receive the campaign. It delivers the messages created by WordPress.

What this changes for the administrator

The administrator has to test more than whether "the email was sent." After a test send, open the message and check the unsubscribe link, the profile link, button clicks, and the behavior of the Newsletter page. If the message arrives but link actions do not work, the problem may be cache behavior, security rules, Newsletter link formatting, or a blocked admin-ajax.php request - not Brevo.

What this changes for reporting

Some metrics stay in Newsletter, while some delivery events may be visible in Brevo. Do not treat these dashboards as interchangeable. Newsletter knows its subscribers, lists, and statuses. Brevo sees service-side delivery. When troubleshooting, review both sides: in WordPress, check who the campaign selected and what the logs recorded; in Brevo, check whether a delivery attempt happened and what result the service returned.

Lists, segments, and test subscribers before the first campaign

Even perfectly connected delivery will not rescue a poorly prepared list. With Newsletter Sendinblue, it is especially important to understand exactly who will receive the email, because external delivery can move a large volume quickly. A targeting mistake becomes more visible: the message can go to the wrong group, the wrong language audience, or a list that should have been cleaned up long ago.

Newsletter lists

In Newsletter, one subscriber can belong to multiple lists. Lists may be public, private, or hidden from the form or profile page. For the first campaign through Brevo, it is best to create a small test list with a few real team addresses. That lets you verify the subject line, sender identity, service links, appearance, and delivery events without risking a send to the entire database.

If the site covers multiple topics, split subscribers by interest. For example: blog updates, store offers, product updates, and events. In that setup, Newsletter Sendinblue serves as the transport layer, while campaign accuracy is determined by Newsletter lists and targeting. That is the right division of responsibility.

Test subscribers

Newsletter supports test subscribers. That is more useful than simply entering any email address into a test field, because the email may be built with real subscriber data: name, address, preferences, and identifiers. To validate personalization and links, it is better to have several test subscribers with different states and list memberships.

Minimal test address set

• An address on the company domain, to verify internal delivery and sender display.
• An address on a major mailbox service, to check filtering and the email's appearance in a normal mail client.
• An address with a different language or list assignment, if the site uses segmentation.
• An administrator address that can quickly verify profile and unsubscribe links.

Targeting before sending

Before launching a campaign, save the targeting settings and review the approximate recipient count. That number may change by the time the campaign runs if subscribers unsubscribe, edit their profile, or are removed. But a sharp mismatch from your expectations is a signal to stop. If you intended to send only to a test group and see the entire list instead, the wrong list or logical operator has been selected.

Practical example: send a test newsletter through Brevo and validate the full chain

Let's walk through a concrete scenario. Assume the site already has a Newsletter signup form and a small list called "Site News." The goal is to send a trial email through Newsletter Sendinblue to an internal test list, make sure the email goes out through Brevo, and confirm that the links work on the site.

Goal

Receive a test email from a verified domain-based sender, confirm that it reaches the inbox, and make sure the unsubscribe link, email button, and profile link all lead to the correct Newsletter pages.

Preparation

• The main Newsletter plugin is installed and opens in WordPress.
• The Newsletter Sendinblue add-on is active.
• The sender verified in Brevo matches the sender configured in Newsletter.
• The API key has been saved in the add-on settings.
• A test list has been created or test subscribers have been marked.
• The public Newsletter page contains the correct shortcode and has not been removed.

Steps

1. Open Newsletter - Newsletters and create a new email in the editor.
2. Add a short subject line, clear copy, and one button linking to a normal site page.
3. Review the footer block to make sure the email includes unsubscribe and profile service links.
4. Save the email and open the preview. Do not judge the links based only on the preview, because some links are generated only during a real send.
5. In targeting, select only the test list or test subscribers.
6. Send a test or a small real campaign to the internal group.
7. Open the received email in the inbox and verify the sender, subject, appearance, button, unsubscribe link, and profile link.
8. Log in to Brevo and check whether a sending attempt or delivery event is visible for the test address.
9. Return to Newsletter and review the logs, campaign status, and the absence of new errors.

Expected result

The email should arrive from the correct name and address, the button should lead to the intended page, the service links should perform the correct Newsletter actions, and Brevo should show signs of delivery or at least a send attempt. If the email arrives but the links fail, do not change the API key. First check the Newsletter link format, cache behavior, admin-ajax.php protection, and the public Newsletter page.

A common nuance that gets in the way

A test email and a real send may not use the same data set. In some cases, the test uses a specific subscriber; in others, it uses the address you entered manually. That is why, for final validation, a small real campaign sent to a test list is more useful than a single "quick" test. It checks the exact path your real newsletter will use.

How to verify the result after setup

Validation should go beyond "the email reached me." Mail delivery depends on the domain, recipient address, email content, sender reputation, links, images, and service limits. After connecting Newsletter Sendinblue, it is worth checking several layers.

Checking in WordPress

In WordPress, make sure the campaign is not stuck in the queue, the selected recipient count matches the targeting rules, test subscribers exist, and there are no warnings in Newsletter system panels. If you see messages related to speed, scheduling, the queue, or the external delivery service, save the exact text in your working notes before you change any settings.

Checking in Brevo

In Brevo, look at delivery events and sender status. If the service shows a rejection, bounce, or sender issue, that tells you far more than the vague feeling that "the plugin is not sending." Confirm whether the failure is tied to the recipient address, sender verification, account limits, domain authentication, or the email content.

Checking on the recipient side

Open the email in several clients. Check the sender name, subject line, preheader, images, button, links, unsubscribe action, and mobile rendering. Outlook, Gmail, and other clients can interpret HTML differently, so before a larger send, do not rely only on the editor preview.

Checking links and cache

Newsletter service links may rely on URL parameters or a call to admin-ajax.php. Optimizers, CDNs, cache layers, and admin security rules sometimes strip parameters or block AJAX access. If signup, unsubscribe, or click actions do not work, review the link format in Newsletter settings and send a new test email after changing the format. An old email will not retroactively update its links.

Delivery, bounces, and complaints: what matters after the first sends

After the first sends, the most useful part of the work begins - watching list quality. Bounces and complaints should not be treated as isolated annoyances. They are signals that help you avoid sending to nonexistent addresses, avoid frustrating users, and protect your domain reputation.

In Newsletter, subscriber statuses may reflect confirmation, bounce, complaint, unsubscribe, and other states. Delivery integrations help bring bounce information back and update statuses. Newsletter documentation emphasizes that professional delivery integrations do more than send messages - they also help return bounced addresses. With Newsletter Sendinblue, that logic matters even more, because the point of the integration is not just to "send faster," but to manage delivery quality.

Hard bounce and soft bounce

A hard bounce usually means a permanent problem: the address does not exist or the domain is not accepting mail. A soft bounce is more often temporary: a full inbox, temporary service unavailability, or a limit on the recipient side. Do not respond to both types the same way. Permanent bounces should be excluded from future sends, while temporary ones should be monitored without drawing immediate conclusions from a single event.

Complaints

A complaint means the recipient marked the email as unwanted. Even if the person subscribed at some point, they may have forgotten or decided they no longer want the emails. That is why every campaign needs clear service links and honest content. Do not try to "work around" unsubscribes or resend to people who have already clearly opted out.

When a separate list cleanup is needed

If you see a large number of bounces, complaints, or inactive addresses after the first campaign, do not increase the speed. Split the database first: active subscribers, long-inactive readers, unconfirmed addresses, imported contacts, and bounced addresses. With an old list, it is better to run a gentle re-engagement step or send only to the most trusted segment first.

Safe improvements without editing plugin code

Newsletter Sendinblue rarely requires code changes. Most improvements come from proper configuration: the sender identity, lists, test subscribers, service link format, domain authentication, logging, speed, and the email template. That is safer than inventing hooks or changing plugin files.

Improve the signup form with Newsletter's built-in CSS

If, after setting up delivery, you want to make the signup form stand out a bit more cleanly on the site, use Newsletter's built-in option for custom CSS. This does not interfere with delivery and does not require editing theme or plugin files. Insert the code only in Newsletter's custom CSS field or in a child theme if you clearly understand where the form is rendered.

.tnp-subscription input[type="email"] {
  border: 1px solid #d7dde8;
  border-radius: 6px;
  padding: 12px 14px;
}

.tnp-subscription input[type="submit"] {
  border-radius: 6px;
  padding: 12px 18px;
  font-weight: 600;
}

After inserting the snippet, open the page with the form in a normal browser window and check the mobile layout. If the theme already applies its own styling, the new CSS may look different. Rolling it back is simple: remove the snippet and clear the site cache.

Safe cache configuration for service links

If confirmation, profile, unsubscribe, or click links lead to the homepage without performing any action, first review Newsletter's Tracking and Action Links settings. After changing the format, be sure to send a new test email. Then review cache and optimization rules: parameters like ?na=... should not be removed, and wp-admin/admin-ajax.php should not be blocked by basic authentication or security rules if the AJAX format is selected.

Do not disable all site caching permanently. It is better to add a targeted exclusion for Newsletter service URLs or choose a link format that is compatible with your infrastructure. If you are not sure, take a screenshot of the current cache settings, change one parameter, send a new test email, and compare the result.

Common usage scenarios

Newsletter Sendinblue is most valuable in cases where the site already knows how to build an audience, and the administrator needs dependable external delivery. The examples below are not a list of "features for the sake of features," but practical models where this integration is especially appropriate.

Content site with topic-based lists

A blog or media site may cover multiple streams: news, reviews, roundups, partner offers. In Newsletter, you create interest-based lists, place signup forms on different pages, and use Sendinblue/Brevo for delivery. The user picks a topic, the editor builds the email in WordPress, and then sends it to the selected segment. It is important not to mix lists without a reason: the more closely the email matches subscriber expectations, the fewer complaints you will see.

Store with a customer base and a separate newsletter

If a store uses WooCommerce and Newsletter integrations, subscribers can be separated by interest or signup source. In that setup, Newsletter Sendinblue does not replace WooCommerce order emails if those are sent by a different mechanism, but it can deliver marketing emails, curated selections, and announcements. Before sending, verify that WooCommerce or an SMTP plugin is not overriding the sender identity for Newsletter emails.

Educational project or membership club

For a club, course, or private community, lists based on level, topic, and participation are useful. Newsletter stores subscribers and statuses, while Brevo helps deliver regular announcements. In this scenario, unsubscribe and profile validation is especially important: the user should have a clear way to adjust preferences, not just fully opt out of all mail.

Editorial newsletter with manual review

If each email is prepared manually, the editor can use Composer, test subscribers, and preview mode. A Brevo integration does not replace the editorial checklist: subject line, preheader, links, images, footer, and a real inbox test. External delivery makes sending more stable, but it does not fix a weak subject line or broken HTML.

When Newsletter Sendinblue is the right choice

Newsletter Sendinblue is worth using if you want to keep the editor, subscribers, lists, and targeting inside The Newsletter Plugin while sending email through Brevo as an external delivery service. It is a solid setup for WordPress sites that already have subscriber collection in place and need a more controlled sending workflow than hosting mail can provide.

Before going live, validate the full chain: a verified sender, the API key, domain authentication, a test list, service links, Newsletter logs, and Brevo events. If all of those pieces check out, you can get the Newsletter Sendinblue file and test the integration on your site without mailing your entire list on day one.

The key is not to treat the add-on like a magic send button. It performs its role well when the sender, domain, lists, testing, and diagnostics around it are all properly configured. In that setup, WordPress remains a convenient workspace for newsletter operations, while Brevo helps deliver email through specialized infrastructure.