How to Set Up a Consent-Based Newsletter With Brevo

Before opening Brevo

Prepare these owner decisions:

• the approved public sender name;
• a real sender mailbox controlled by the organization;
• the exact newsletter purpose and frequency;
• the privacy notice URL;
• who owns the contact data and Brevo account;
• who can edit, export or delete contacts;
• the lawful basis and jurisdiction-specific advice;
• the retention and deletion process.

If the website's public contact email is configured through an environment variable, use only the approved value. Do not guess an address such as hello@ or newsletter@ because the domain exists.

Step 1: create a dedicated list

In Brevo, create one master newsletter list with an internal name that identifies the site and consent source. Do not mix customers, transactional recipients, manually collected business cards and newsletter subscribers into one undifferentiated list.

Create only the contact attributes you need. Email is required for an email newsletter; name can be optional. Avoid collecting phone, company, birthday or location without a clear purpose.

Step 2: write clear form language

The form should explain:

• who is sending;
• the content subscribers will receive;
• approximate frequency;
• how to unsubscribe;
• where the privacy notice is located;
• whether optional analytics or profiling is involved.

Use an active, unchecked action. Do not hide consent inside general terms or make unrelated marketing consent a condition of a necessary service.

Example:

Send me UseAIVisora's practical AI-tool and software guides, approximately twice per month. I can unsubscribe from any newsletter email. See the Privacy Policy for how subscriber data is handled.

This is illustrative copy, not legal advice. Adapt it to actual operations and reviewed requirements.

Step 3: build the Brevo form

Brevo's current guide places forms under Marketing → Forms. Create a full-page/embedded or other approved form, assign it to the dedicated list and add the minimum fields.

Brevo documents GDPR field blocks and preference choices. If subscribers can choose materially different topics, provide separate choices where the plan and implementation support them. Record which version of the form generated each contact.

Step 4: enable double opt-in

Brevo supports a double-confirmation email. A new subscriber submits the form, receives a confirmation link and becomes confirmed only after clicking it.

Configure:

1. a plain confirmation subject and sender;
2. a confirmation template containing the required confirmation link;
3. a post-submission page explaining that confirmation is required;
4. a post-confirmation page;
5. an optional final confirmation/welcome message;
6. the correct destination list.

Do not enable two independent double-opt-in systems for the same form. Brevo warns that using form-based and automation-based confirmation together can send duplicate confirmation messages.

For an external website form, Brevo documents a temporary-list automation: add the submitted contact to a temporary list, send the confirmation request and move only confirmed contacts to the master list. Protect the integration key and validate error/retry behavior.

Step 5: authenticate the sending domain

Brevo may supply domain-authentication and branded-link DNS records. Add them only through the authorized DNS account and only after copying the current values from Brevo. Check each host name, type and target for conflicts.

Important safeguards:

• do not delete MX records or unrelated SPF/DKIM records;
• do not replace website A/CNAME records;
• do not publish an API key in DNS;
• understand whether a TXT host must be merged rather than duplicated;
• keep a before-and-after record;
• allow DNS propagation and verify inside Brevo.

Use a DMARC policy appropriate to the organization's current mail setup and obtain expert help before enforcing a stricter policy. This article does not authorize or perform DNS changes.

Step 6: create a minimal welcome email

The welcome message should confirm what the subscriber requested, set the cadence, link to useful existing content and include the normal unsubscribe mechanism. Avoid a long sales sequence before trust is established.

A practical first email can include:

• one-sentence confirmation;
• links to best AI tools for freelancers and best backend platforms for AI apps;
• a preference or reply invitation;
• sender identity and postal/legal details required for the operation;
• unsubscribe link.

Step 7: test the full lifecycle

Use controlled addresses from different providers where authorized. Test:

Also test mobile form layout, keyboard use, error messages, privacy link, slow connection and duplicate submission.

Step 8: publish the form carefully

Add the form where readers can make an informed choice—such as the footer, article end or a dedicated newsletter page. Do not cover content with an immediate intrusive popup. Label the form and confirmation state clearly.

The UseAIVisora codebase should enable a live form only after owner approval, provider configuration, consent flow and privacy documentation are complete. A placeholder should not silently begin collecting addresses.

Step 9: send a controlled first campaign

Preview on desktop and mobile, test every link, verify sender and reply-to, and check that unsubscribe is visible. Send to a small approved segment first. Monitor hard bounces, complaints and authentication results before a larger campaign.

Do not promise a fixed cadence you cannot maintain. Helpful, expected email is the foundation of list health.

Step 10: maintain the list

Review access, forms, automations, DNS verification, suppression and privacy text regularly. Remove invalid addresses, investigate complaints and retain only the consent evidence needed. When changing provider, export suppression status so unsubscribed contacts are not reactivated.

Our Brevo vs MailerLite comparison helps evaluate whether Brevo remains the right platform as the list grows.

Limitations and legal boundary

UseAIVisora did not configure a Brevo form, alter DNS, send a campaign or test deliverability for this guide. Laws and platform terms vary. Obtain appropriate legal and technical advice for the organization's location, recipients and content.

Frequently asked questions

Official sources reviewed

Steps were checked against Brevo's sign-up form guide, GDPR-oriented form guidance, external-form double opt-in workflow and plan guide. Last checked 2026-08-01.