Brevo Free Hands-On: Creating a Contact, List, and Campaign Draft

Last verified: 2026-09-02 JST

What we tested

TESTED BY ORAVENDA Synthetic contact → persisted Brevo CRM record → dedicated test list → regular email campaign draft → Preview & Test attempt. The contact, list membership, audience, subject, content, and design were saved. Preview & Test was blocked by a phone-verification prompt.

Brevo Free test environment

The account used Brevo Free. No paid plan was purchased, no credit card was added, and the controlled test cost USD 0. The sender shown in the draft was Oravenda using [email protected].

No real customer PII, contact list, lead, or CRM export was used. No marketing email was sent.

OFFICIAL PRODUCT FACT The official Brevo plan record lists Free at $0 per month with no time limit, no credit card requirement, 300 daily sends, up to 100,000 contacts, one user seat, and marketing automation up to 2,000 contacts. These are changeable plan facts; check Brevo's current official pricing before relying on them.

Creating the synthetic contact

We manually created the synthetic contact and saved it. It was then visible in Brevo CRM with the expected name and email fields. This is persistence evidence, not a claim about duplicate matching, imports, permissions, enrichment, or other contact properties.

• CONTACT_CREATED = YES
• CONTACT_VISIBLE = YES
• EXPECTED_FIELDS_PRESENT = YES
• REAL_CUSTOMER_PII_USED = NO

Creating and using a dedicated list

Oravenda created Oravenda Sprint68 Controlled Test as a separate list. The automatically created “Your first list” was not counted as the test list. The synthetic contact was added to the dedicated list, and the contact record showed membership in that list.

• TEST_LIST_CREATED = YES
• CONTACT_IN_TEST_LIST = YES

A stored contact and the intended campaign audience are separate things to verify. The test did not import a real segment or mailing list.

Creating the campaign draft

We created a regular draft named Oravenda Sprint68 Controlled Draft. Brevo displayed the dedicated test list as the recipient audience with 1 recipient. The subject was saved as Oravenda Brevo Controlled Test.

This is a controlled Oravenda product test.
No marketing communication is intended.

The rich-text editor accepted the content and the design was saved. These are persistence observations, not evidence that a recipient saw the message.

• CAMPAIGN_DRAFT_CREATED = YES
• RECIPIENT_LIST_SELECTED = YES
• RECIPIENT_COUNT_OBSERVED = 1
• SUBJECT_PERSISTED = YES
• EDITOR_ACCESSIBLE = YES
• DESIGN_SAVED = YES

The campaign was never sent or scheduled.

What happened at Preview & Test

After saving the draft, the owner selected Preview & Test. On the account we tested, Brevo displayed “One last step to secure your account” and requested phone verification. The UI indicated that verification enables capabilities including campaign sending and API-key creation.

Oravenda stopped at that gate. No phone number was entered, no SMS code was requested, and verification was not completed.

• PREVIEW_AND_TEST_ATTEMPTED = YES
• PREVIEW_AVAILABLE = BLOCKED_BY_PHONE_VERIFICATION
• PHONE_VERIFICATION = NOT_PERFORMED

This is an account-specific observation. We do not claim every Brevo user sees the same prompt at the same step.

Free-plan branding observation

In the campaign editor, the tested Free account displayed a notice that removing the “Sent by Brevo” footer branding required an upgrade. This was observed in this controlled account and is not a claim that every account or every paid plan has identical behavior.

What we did not test

UNVERIFIED / NOT TESTED Email delivery, inbox placement, deliverability, a successfully rendered preview, a test email, campaign scheduling, phone verification, API-key creation, automation workflows, contact import, bulk list management, large audiences, and long-term reliability were not tested. Brevo's Affiliate Program was not tested.

EMAIL_SENT = NO · TEST_EMAIL_SENT = NO · CAMPAIGN_SCHEDULED = NO · EMAIL_DELIVERY_TEST = NOT_TESTED · DELIVERABILITY = NOT_TESTED · AUTOMATION = NOT_TESTED

Who Brevo Free may suit

This tested path may suit an individual or small team that needs to keep a modest contact list, organize a named audience, and prepare a campaign draft before deciding whether a paid email service is worthwhile. Free-plan limits should be checked against the current official plan and the operator's consent process.

When a simpler workflow may be enough

A spreadsheet plus a manual, consent-aware email workflow may be simpler for a tiny list and occasional messages. Brevo introduces a contact database, list management, and a campaign editor; those layers are useful only when they solve a repeatable problem.

For event-driven routing, see the tested Make webhook-to-Google-Sheets guide and the Pabbly vs Make comparison. The Oravenda methodology explains how tested facts and unknowns are separated.

Final evidence-based takeaway

In this controlled Brevo Free test, Oravenda successfully created a synthetic contact, organized it into a dedicated list, confirmed membership, selected that list as a campaign audience, saved a subject, created rich-text content, and saved the design as a draft. Brevo displayed one recipient.

When Preview & Test was attempted, Brevo prompted us for phone verification on this account. No verification was completed, and no email was sent or scheduled. Delivery, inbox placement, deliverability, and automation therefore remain untested.

That is the useful boundary: this account state supported contact organization and campaign drafting before payment, while the next preview/send step was gated. Recheck current official plan details and reproduce the relevant step with synthetic data before relying on Brevo for real marketing.