Brevo formerly Sendinblue means that Brevo is the current name of the service previously called Sendinblue. The company announced the new brand in May 2023, reflecting a platform identity broader than email delivery alone. It was a rebrand rather than the launch of an unrelated replacement service. You may still encounter the Sendinblue name in older tutorials, integration listings, account records, and discussions, but Brevo is the name to use when looking for current product information.
Brevo formerly Sendinblue and the name change
Sendinblue became Brevo in May 2023. The change replaced the former company and product name with a brand intended to represent a wider customer communication platform.
The distinction matters because “Sendinblue” was strongly associated with sending email. Brevo’s scope now covers email campaigns, contact management, marketing automation, transactional delivery, reporting, and CRM-adjacent sales functions. The broader name therefore fits a service that extends beyond a conventional newsletter tool.
The Brevo formerly Sendinblue rebrand should not be interpreted as a merger between two competing products or as an instruction to move from one independent platform to another. Brevo is the name readers should associate with the continuing service. Sendinblue is its former identity.
That brand continuity does not mean every interface, plan, limit, or feature has remained unchanged since 2023. Products evolve after a rebrand, so an old Sendinblue article may correctly describe the historical service while still being unsuitable as a current set of instructions.
What the Brevo rebrand meant for Sendinblue users
For existing users, the central practical change was the identity under which the service operates. A company rebrand changes the name customers see; it does not by itself create a separate account or require a platform migration. Users encountering both names should treat them as references to the same service at different points in its history.
| Older reference | Current interpretation | Practical action |
|---|---|---|
| Sendinblue company or platform | Brevo | Use Brevo when seeking current product information or contacting support. |
| Sendinblue campaign guide | Legacy instructions for the platform now called Brevo | Confirm current labels and steps in Brevo documentation before making changes. |
| Sendinblue integration name | A possible legacy label for a Brevo connection | Identify the provider and connection purpose before removing or reconfiguring it. |
| Sendinblue plan or allowance | Historical commercial information | Do not assume the same plan, price, quota, or entitlement remains applicable. |
The rename alone is not evidence that customer contacts, campaigns, billing terms, integrations, or product entitlements changed. Equally, it is not proof that every detail stayed fixed. Those operational details can change independently as the platform develops.
If an existing account presents an access, billing, or integration problem, diagnose the specific issue rather than treating the old name as the cause. Check that you are using an official Brevo service, confirm the relevant account identity, and consult current support guidance. Avoid creating duplicate records, rotating credentials, or disconnecting a working integration solely because an older reference says Sendinblue.
Why the Sendinblue name still appears online
Brand changes spread unevenly across the web. The vendor can update its principal website and documentation, but it does not control every article, video, plugin description, internal company document, bookmarked page, or archived invoice that mentions the former name.
Search engines may also continue surfacing well-established Sendinblue pages because their subject remains related to Brevo. Third-party integration directories and internal procedures can retain old terminology long after the main brand changes. In some cases, an older name may be kept temporarily to help existing users recognize a connection.
A Sendinblue reference is therefore not automatically fraudulent or useless. Its value depends on what it is being used to establish. An old explanation of a basic email concept may remain helpful, while an old pricing table, account navigation path, API configuration procedure, or plan limit can become inaccurate.
For current operational decisions, prefer Brevo’s present website, help center, and support context. Treat legacy Sendinblue resources as historical or supplementary material rather than the final authority for a setting or entitlement.
How to check whether a Sendinblue reference is relevant
Use a short verification process before following an old tutorial or changing an existing configuration:
- Check the publication and update dates. Material created before May 2023 predates the Brevo name. A recent update date is more useful, although it does not guarantee every detail is current.
- Identify the actual task. Separate the enduring goal, such as creating an email campaign, from interface-specific instructions such as a menu name or button location.
- Look for current branding. Determine whether the publisher has updated Sendinblue references to Brevo and whether the screenshots or terminology match the service you can access.
- Confirm sensitive details. Validate pricing, quotas, plan entitlements, authentication settings, data-handling instructions, and integration procedures against current Brevo information.
- Stop if identities do not match. Do not enter account credentials or API keys into an unfamiliar site merely because it uses either brand name.
Illustrative search update
Suppose an older company guide tells a marketer to search for “Sendinblue automation setup.” The underlying task is still understandable, but the old wording may prioritize archived instructions. A better current search would be “Brevo marketing automation documentation,” followed by the specific action, such as creating a workflow or sending an automated email.
After finding the current material, compare its terminology and prerequisites with the old guide. The successful outcome is not simply finding the Brevo name; it is confirming that the instructions cover the same task, account area, and required connection without relying on obsolete labels.
Which name should you use now
Use Brevo in new marketing materials, internal procedures, procurement records, and support requests. Where the audience may know only the previous brand, introduce the relationship once as “Brevo, formerly Sendinblue,” then use Brevo for the rest of the communication.
Retain Sendinblue only when historical context is necessary, such as identifying an old contract, explaining a legacy integration label, or helping users connect an archived tutorial with the current service. This approach preserves clarity without making the former and current names look like separate platforms.
Explore more technology guides on Techistuff.
Frequently Asked Questions About Brevo formerly Sendinblue
Is Brevo the same service as Sendinblue?
Yes. Brevo is the current brand name for the service previously known as Sendinblue. It should be understood as a company and product rebrand, not as a separate email marketing platform competing with or replacing Sendinblue.
When did Sendinblue become Brevo?
Sendinblue announced the Brevo name in May 2023. The new branding reflected a broader platform identity extending beyond the email-focused meaning associated with the former name.
Can old Sendinblue tutorials still be useful?
They can provide background, but their navigation labels, screenshots, plan details, limits, and configuration steps may no longer match the current platform. Use the tutorial to identify the underlying task, then confirm the procedure in current Brevo documentation.
Should marketers use Brevo or Sendinblue in new content?
Use Brevo as the primary name in current communications. If readers may recognize only the former brand, introduce it once as “Brevo, formerly Sendinblue.” Continuing to use Sendinblue alone can make current guidance appear outdated or suggest that it describes a separate product.
