Brevo: separate campaign goals from operational messages

Research-based product guide · Published August 29, 2026 · How we research

5 min read · Fact-checked November 4, 2026 · Research-based analysis

Table of Contents

Contact storage, daily sending and message purpose are separate

Brevo’s plan documentation describes email, messaging and customer-relationship functions. Its email-type explanation distinguishes marketing, transactional and automation email. Use that distinction to identify the responsible source and owner for each message.

A receipt triggered by an order, a newsletter approved by an editor and a product recommendation after purchase should not be treated as one undifferentiated stream. Inventory the trigger, expected timing, recipient choice and failure route. Then check which parts the selected configuration must support.

Planning dimension	Example	Question to settle
Stored contacts	People represented in the account	Which records count for the selected package?
Send volume	Campaigns plus triggered messages	Can the required volume be delivered in the required period?
Operational trigger	An order event from the authoritative system	Who investigates a missing or repeated message?
Marketing preference	A subscriber’s current choice	Which connected system controls eligibility?

For a time-sensitive launch, estimate the audience that needs the message on that day. Spreading a send over several days changes the campaign, so a nominally large contact capacity does not by itself make a free configuration suitable.

Inventory the messages before choosing a plan

List the messages the business sends in an ordinary week. For each, record the trigger, audience, owner, expected timing and source system. A receipt may come from a checkout event. A newsletter may come from an editorial calendar. A cart reminder needs a reliable event and a clear stopping condition.

Then identify duplication. A store plugin and a marketing workflow may both send a welcome or order-related message. Customers experience the combined output even if different departments consider each individual send correct. Assign one responsible sender per purpose before enabling new automations.

Use this inventory to distinguish a publishing problem from a delivery integration problem. If marketers cannot produce campaigns consistently, the editor and approval process deserve attention. If developers cannot track an operational message reliably, the evaluation needs technical evidence about the sending path and event handling.

Build a test around an ordinary customer journey

Imagine a small homeware store introducing a new collection. A subscriber requests product updates, receives a launch email and places an order. Marketing wants to thank the buyer and eventually suggest care instructions. Operations needs the buyer to receive the essential order information from the authoritative order system.

Create controlled records for a prospect, an existing customer and someone who changes their marketing preference. Write down the expected communication for each. Check that the launch audience is correct and that an order changes the later marketing journey where intended. Do not assume a purchase event contains every item, category or status field your segmentation needs.

Include a failed or delayed event in the design discussion. Ask who sees an integration error and how the team determines whether a customer already received a message. A successful evaluation should explain the exceptional path, not merely demonstrate that a template can be sent once.

Separate purpose, ownership and measurement

Message	Operating question	Useful evidence
Editorial newsletter	Did the intended audience receive the promised content?	Audience rule, approved version and useful reader response
Promotional journey	Did the customer remain eligible at each step?	Entry, exit and suppression checks
Order-related message	Did the authoritative event produce the intended communication?	Event identifier, sending result and failure owner
Human reply	Can a person continue the conversation?	Monitored inbox and accessible order context

This planning table does not classify your specific messages for legal purposes. If a message combines essential information with a sales offer, have the responsible business owner review the applicable requirements using current official guidance. Product categories in an interface do not make that decision for the business.

Make preferences usable across the workflow

Document how a person joins the audience and which choices they can change. Keep the original source and the relevant preference state accessible to the people who maintain the program. Imported contacts need the same care as newly collected contacts; an old spreadsheet is not a complete explanation of what recipients expect.

Test an opt-out with every connected campaign path you plan to use. Then inspect the affected record in the other systems. If the storefront, support tool and marketing platform each maintain customer fields, decide which one controls the marketing preference and what happens during a synchronization failure.

Keep channel choices distinct where the business requires distinct choices. A person who requests email updates may have no interest in another messaging channel. Design the preference experience around understandable customer decisions, then verify the supported implementation rather than forcing every preference into a single generic tag.

Review the editor as a production tool

Ask the person who will publish campaigns to build a real draft using approved brand assets. Preview it on a phone, inspect the text version if relevant to your workflow and check all destinations. Confirm the process for approval and the final send. An attractive library of templates is less valuable than a repeatable method for producing the next twelve campaigns.

Prepare a backup operator. They should be able to find the approved audience, identify the current draft and understand which links need checking. Record any steps that require specialist knowledge. Include that training burden in the buying decision instead of assuming the interface is self-explanatory to everyone.

Pricing: the free plan’s daily cap matters

Brevo’s current plan help states that Free includes 300 daily email sends and storage for up to 100,000 contacts. Unused daily sends do not carry over. The two figures describe different capacities.

A 1,000-person launch therefore cannot be budgeted as one same-day campaign using a 300-send daily allowance. Obtain the paid configuration for the required volume, contacts, features and channels. Keep separate services and implementation work visible instead of treating the headline email plan as the entire customer-communication bill.

Our buying recommendation

Put Brevo on the shortlist when the message inventory and volume forecast match its proposed configuration. Start with a bounded stream, verify the trigger and preference paths, then expand. Compare GetResponse for an acquisition journey and ActiveCampaign when lifecycle coordination is the dominant requirement.

Keep exploring

• A welcome email checklist: promise, permission and the next step
• Moosend: build an email programme your team can maintain
• GetResponse: connect the signup page to the next useful email
• Browse every tool in the directory

Sources and editorial notes

Checked November 4, 2026. Product facts and plan boundaries are linked to official sources; recommendations are our editorial analysis. Worked examples use fictional inputs. We have not run hands-on performance tests or claimed vendor partnerships.

• marketing platform
• official explanation of email types
• Brevo official product website
• Plan and free-cap documentation
• Current commercial options

Product links go directly to official websites. Any future paid referral will be identified. Affiliate disclosure · Editorial methodology.