ToolPickly Editorial Research

Brevo tutorial: a verifiable path from contact import to first-campaign review

Use a small consented list to verify import, domain authentication, the first send, automation fit, and cost—with a pass or stop condition at every stage.

Reviewed 2026-09-1612 minute readHow we work

Decision in one minute

Complete one traceable end-to-end campaign at small scale before importing the full list, building complex automation, or upgrading. A successful send is not the same as a successful purchase.

Original analysis · Reproducible arithmetic

First-campaign validation ledger

Keep setup action, retained evidence, pass condition, and stop condition in one ledger. Sample sizes are pilot recommendations—not official Brevo allowances. Recheck current official limits and pricing before upgrading.

Stage	Pilot action	Retain	Pass if	Stop if
Contact preparation	Select 50–200 explicitly consented contacts	Consent source, date, and field dictionary	Every record has a traceable source and purpose	Consent is unprovable or identifiers conflict
Import	Map fields into a dedicated test list	Accepted, updated, rejected counts and error file	Counts reconcile and five sampled records match	Create-versus-update behavior is unclear
Send preparation	Authenticate the domain, configure sender, and preview	Authentication result, template version, and test proof	Authentication, unsubscribe, and destination work	The domain cannot authenticate or compliance has no owner
First campaign	Send one representative campaign and wait for reporting	Delivery, bounce, unsubscribe, click, and complaint baseline	No unexplained hard-bounce cluster appears	Unknown addresses or complaints expose list-quality risk
Business review	Reconcile tagged links to one downstream action	Campaign, audience, link, and target-action record	Reporting leads to one observable next decision	Only opens are discussed and no action can be reconciled

The ledger can reject a weak operating fit; it does not prove Brevo is suitable. Move to automation and paid-plan evaluation only when the team can maintain list integrity, delivery, attribution, and cost.

01 | Prepare contacts: consent comes before CSV

Begin with 50–200 real contacts and record consent source, consent date, expected message type, and owner. The import needs at least one accepted identifier; new contacts should not carry CONTACT_ID values generated elsewhere. Clean email, phone, country code, language, and subscription state first.

Create a field dictionary documenting source, format, required status, overwrite behavior, and null handling. Do not invent field meaning during import. Exclude historical contacts whose marketing consent cannot be demonstrated instead of hiding the gap inside a bulk import.

Why may each contact receive this message type?
Which fields may overwrite existing values?
Who owns rejected rows and when are they retried?

02 | Import contacts: reconcile before scaling

Use CRM > Contacts > Import contacts, place pilot records in a dedicated list, and complete attribute mapping. Preserve accepted, updated, and rejected counts plus the error report, then sample at least five records for identifiers, subscription state, language, and critical custom fields.

Do not send when counts fail to reconcile. Determine whether the system created, updated, skipped, or merged each record and document the behavior. Scale only when the team can explain the rule.

03 | First send: verify domain, unsubscribe, and delivery operations

Authenticate the sending domain, configure a recognizable sender, and test preview, mobile rendering, links, unsubscribe, and destinations before creating the campaign. Use representative recurring content rather than a demo designed to produce attractive metrics.

Record delivered, soft bounce, hard bounce, unsubscribe, complaint, and link-click outcomes. Privacy mechanisms can distort opens, so open rate is not a sufficient success metric. Pause scaling when unknown-address failures cluster, unsubscribe fails, or compliance ownership is unclear.

04 | Automation: prove trigger, exit, and human handoff

Do not make complex automation the first task. Choose one observable event such as form submission, list entry, or purchase, then document entry, delays, branches, frequency cap, exit, and human handoff. Run test contacts through every path.

Mark any automation-contact, send-volume, seat, or add-on threshold that would trigger an upgrade at real scale. Automation creates value only when it removes manual work without creating unexplained messages.

05 | Cost and fit: decide whether to upgrade

Enter monthly sends, stored contacts, automation contacts, marketing seats, logo removal, Sales Essentials, SMS or WhatsApp, dedicated IP, and implementation time separately. Choosing Free, Starter, or Standard requires the limits triggered by the real workflow—not the headline entry price.

The fit is strongest when multichannel marketing and lightweight CRM need shared contact data. It weakens for newsletter-native publishing, complex sales-object governance, or complete export of deal notes, files, and email activity. Compare Brevo and alternatives with the same job and scorecard, keeping ‘do not buy’ available.

Official sources and evidence

Product behavior and search-report definitions can change. Recheck the linked official pages before a purchase or migration.