A Practical Brevo Automation Guide: Customer Events, Branches and Re-entry

By Trayan Hristov · Thrivelia · Reviewed 13 October 2026

A Brevo automation should translate a customer event into useful follow-up. Define the customer milestone and the required data before choosing a template or adding channels.

Brevo is moving from its classic automation editor to the newer editor. Check which editor and feature tier your account uses so that the build instructions match the tools actually available.

Start with an event and a customer question

Choose an event your team can trace: a new signup, a completed order, a product action or a customer request. Describe what the person needs next and which action would demonstrate progress. For software onboarding, that might be completing a useful first task rather than simply opening an email.

Give each required event an owner and a sample payload. Check identity, event time and the properties needed for the message. If an event arrives late or duplicates are possible, address that before assuming that a branch will represent the customer’s current state.

Use the current editor deliberately

Brevo’s newer editor provides conditional and percentage splits, a wait-until-event action and audience settings for re-entry, exit and restart behaviour. Its documentation also describes testing messages without running other steps or affecting statistics. Availability can depend on the account and plan.

Those features answer different questions. A conditional split should reflect customer context; a percentage split can support an agreed experiment. Waiting for an event should have a defined purpose and fallback. Re-entry should represent a repeat customer need, not an accidental loop.

Read Brevo’s comparison of the new and classic editors before planning a new build or moving an existing automation.

Design the smallest useful journey

Build one path that helps a customer reach the chosen milestone. Add a separate message for someone who has completed it only if that message has a different useful job. An onboarding reminder should not congratulate a completed task, and a completion message should not keep asking the person to start.

For ecommerce, connect the programme to the product decision and the post-purchase experience. For SaaS, use the actual activation event and the next task. When a business has both sales-led and self-service customers, make the handoff owner clear so the automation does not contradict a human conversation.

QA the audience rules and fallbacks

Use test messages for copy, design and links, then separately test the full behaviour with controlled profiles. Include missing properties and a delayed event. Record expected and observed results so the launch decision is based on the journey rather than a screenshot alone.

Customer state	Decision to check	Useful evidence
New signup without the goal event	The intended onboarding path starts	Entry event and initial message
Goal completed while waiting	The next action responds to completion	Wait or branch outcome
Goal never arrives	The agreed fallback remains useful	Timing and fallback message
A repeat qualifying event	Re-entry matches the planned experience	Duplicate prevention and audience settings

Review pricing and outcome together

Brevo’s pricing combines email-volume tiers with associated contact limits; the required automation tier and add-ons also matter. Use your actual stored audience and peak sending month when comparing plans, rather than assuming a volume-based tool has no contact constraint.

Measure the milestone reached, time to the milestone and the quality of the next action. For a purchasing journey, add the relevant order or repeat-purchase measure. See Brevo’s pricing explanation, our six-platform comparison or Thrivelia’s services. Reviewed 13 October 2026.

Worked build: help a new software user complete one useful task

Consider an illustrative software product where a signup becomes useful only after a user connects a data source and completes a first report. The onboarding automation should help the user complete the next missing action. A person who has already built the report should receive a useful continuation rather than another instruction to begin.

Define activation in product terms with the product team. A click to the dashboard is a step towards the goal, not the goal itself. Make sure the reporting source can distinguish a connected source, a generated report and repeat use. This example describes an event-led planning approach; confirm that Brevo and your integration can represent the necessary identity and events before committing to the build.

Create an event and identity contract

These are illustrative event names for an implementation brief. They are not promised Brevo defaults. Decide whether the customer is a user, account or other object, then verify the relevant editor and plan capabilities. A contact-only design may be insufficient if the essential decision belongs to a shared workspace.

Example input	Meaning to preserve	Implementation question
signup_completed	An eligible new user has an account	Which identity receives the marketing programme?
data_source_connected	The source was connected successfully	Does the integration send success rather than only a button click?
first_report_created	The customer reached the agreed activation milestone	Can the event stop or redirect the onboarding reminder?
repeat_report_created	The product is becoming useful again	How is repeated use measured independently?
human_handoff	A person is managing the account conversation	Which messages should pause or change?

Use waits, branches and restarts for different purposes

A time delay gives the customer an opportunity to act. Waiting for an event can represent a specific milestone, with an agreed fallback when it never arrives. A conditional split routes by a relevant state. Re-entry allows a new qualifying situation to start another path; restart behaviour can send a person back through a sequence. Decide what each of these means to the customer before configuring it.

Brevo’s newer editor centralises audience entry, exit, re-entry and restart settings and provides a test function. Use the official new-editor overview to check the tools available in the account. Older classic-editor instructions can describe different controls.

Specify the useful next message

These are sample briefs. Deep links should land on the correct task for the user’s current product state, with a useful login fallback. Keep each message focused on one action and test whether the page fulfils the promise. A generic home-page link will often add unnecessary work for a newly activated customer.

Customer state	Illustrative message brief	Primary action
Signed up, source missing	‘Your first report starts with one connection’ — explain the needed source and the benefit	Connect the source
Source connected, report missing	‘Turn that connection into a useful answer’ — show one achievable first report	Create the first report
First report complete	‘Make next week’s report easier’ — explain the next useful product action	Set up the next task
Human-led conversation active	Coordinate the continuation with the account owner	Use the agreed handoff

Test the behaviour as well as the email

Brevo’s message-test guidance distinguishes message testing from the rest of the automation. Use it for subject, personalisation, design and links, then run a controlled full-path test for entry and event behaviour. Keep both kinds of evidence in the release record. See testing automation messages.

• Signup occurs once and twice; the entry behaviour matches the agreed duplicate rule.

• The source is connected immediately and after a delay; both routes remain relevant.

• The report is created before the reminder; the later message recognises completion.

• An event arrives late or lacks a required property; the fallback is useful.

• A shared account has two users; the identity design avoids contradictory reminders.

• A human handoff is active; the agreed messaging rule is applied.

• A repeat qualifying event occurs; re-entry or restart reflects a new customer need.

Measure activation with a usable denominator

Suppose 1,000 eligible new accounts enter a complete 14-day observation window and 260 create their first report. Activation is 26% for that defined cohort. If 180 of those activated accounts create another report in the next equal observation window, repeat use among activated accounts is about 69.2%. These are hypothetical examples, and each denominator should be stated alongside the rate.

Email clicks can help diagnose whether the message reaches the right action, but the product event determines activation. Review missing events and identity mismatches before explaining a low conversion rate as a copy problem. Also keep paid conversion and retained use separate from first activation.

Estimate software using actual stored contacts, email volume, required automation tier and any object or integration features. Include the engineering work needed to make the events reliable. A low headline licence price does not remove the need for a correct product-data contract.