SOURCE-BASED ANALYSIS · NO HANDS-ON RATING
Start with the business event, not the canvas
Brevo describes an automation as triggers, actions and rules, with optional audience settings controlling re-entry and exit. Before adding steps, name the event that should admit a contact and the state that should stop further messages. A welcome sequence and an abandoned-cart reminder need different repeat behavior even if both send email.
Choose a re-entry policy by outcome
Brevo's documentation uses a welcome automation as an example that would usually run once, while an abandoned-cart automation may allow a contact to re-enter after leaving and matching the trigger again. Turn that distinction into a written rule. For example: “A contact receives onboarding once per account; a cart reminder may restart for a new cart after the previous journey has ended.”
| Scenario | Proposed repeat rule | Failure to test |
|---|---|---|
| Welcome series | One completed entry per contact identity | An import or manual action sends onboarding again |
| Abandoned cart | Re-entry only after exit and a new qualifying event | One cart creates overlapping journeys |
| Sales-stage notification | Re-enter when the stage transition happens again | An unchanged stage repeatedly creates tasks |
These policies are planning examples, not Brevo defaults. Configure the product to match the rule you approve.
Understand manual addition
Brevo documents a dedicated “Contact added manually” trigger for an automation intended to receive manual additions. It also notes that a contact already in an automation, or one that has exited and is not allowed to re-enter, will not be added again merely because an operator tries. Use a manual path as an explicit operational procedure, not as a workaround for unclear re-entry settings.
Run a four-contact acceptance set
- Create a synthetic contact that has never entered and prove the main trigger admits it.
- Present the same qualifying event while the contact is still active and check that the result matches your overlap policy.
- Let a second contact exit, present the event again and verify the configured re-entry choice.
- Force the documented exit condition for a third contact and confirm later actions do not continue.
- Use the manual-add trigger with a fourth contact and record whether the journey begins as intended.
Separate contact import from journey entry
Brevo warns that large contact imports may not add contacts to an automation whose entry point is “contact added to a list.” A successful import therefore does not prove journey enrollment. If historical contacts need a one-time campaign, decide whether a campaign or a controlled manual automation entry is the appropriate mechanism and verify the supported volume and consent basis.
Record the version you approved
Keep the automation name, trigger, audience settings, exit rules, active date and synthetic acceptance results. When a trigger or audience rule changes, repeat the first-entry and re-entry cases. The goal is to prevent an apparently small configuration change from sending an old journey to the wrong audience.
Sources and verification
Official documentation checked on 2026-10-29. Worked examples are hypothetical planning exercises, not measured product benchmarks.