Start with a signup form and a list for confirmed subscribers. In Brevo, open Marketing, then Forms, create a full-page or embedded signup form, and choose double opt-in in the confirmation settings. Try the signup yourself before sending a newsletter. This guide covers the setup sequence and provides sample confirmation copy; it is based on Brevo documentation, without an independent campaign test.
- Best for
- A small publication or business starting a permission-based newsletter with an approved domain, privacy notice and predictable content cadence.
- Not suitable for
- Cold outreach lists, purchased data, invented sender addresses or a launch before domain ownership and privacy responsibilities are clear.
- Bottom line
- Connect the provider only after consent language, sender identity, DNS authorization, suppression and ownership are documented.
Consent-evidence lifecycle with failure and unsubscribe recovery
- Capture a specific permission
- Action
- State the newsletter purpose beside an unchecked action and link the applicable privacy information.
- Output
- A timestamped form submission tied to the disclosed purpose.
- Stop when
- Consent is bundled with an unrelated request or preselected.
- Confirm address control
- Action
- Send the double-opt-in message and add the address to the active list only after confirmation.
- Output
- A confirmation event plus the form and wording version used.
- Authenticate and test delivery
- Action
- Configure the sender records supplied for the domain, then test rendering, links, reply handling and the welcome automation.
- Output
- A dated preflight record for the sending identity and first message.
- Stop when
- Authentication fails, the sender is not controlled, or the expected message path breaks.
- Preserve withdrawal
- Action
- Test one-click unsubscribe, suppression and re-import behavior so an opted-out address cannot be silently reactivated.
- Output
- A suppression record and a documented recovery path for accidental sends.
- Double opt-in confirms control of the submitted address and creates stronger evidence, but it is not by itself a complete legal compliance program.
- Use a real organization-controlled sender address; do not display or send from an invented mailbox.
- Add only the DNS records Brevo currently supplies after checking for conflicts, and do not alter unrelated mail or website records.
- Test unsubscribe and suppression before the first campaign so opted-out contacts cannot re-enter through automation.
What to prepare
Have these details ready before creating the form:
- an approved public sender name and a real mailbox you control;
- a privacy notice link and a plain description of what subscribers will receive;
- a sending frequency you can maintain;
- the minimum fields you need, usually email with an optional name;
- an account owner responsible for access, consent records and deletion requests.
The sample below describes a fortnightly software newsletter. It is illustrative, not a claim about your sending schedule. Adapt the wording to your actual operation and get advice on the requirements that apply to your subscribers.
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
- Open Marketing, then Forms in Brevo.
- Choose Sign-up, then Create sign-up form.
- Choose Full page/embedded, give the form an internal name and create it.
- Add the fields you need, the newsletter explanation and the privacy notice link.
- Choose the destination list and confirmation settings before sharing or embedding the form.
These labels follow Brevo's sign-up form guide, checked on 9 September 2026. Continue with double opt-in below before making the form public.
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:
- a plain confirmation subject and sender;
- a confirmation template containing the required confirmation link;
- a post-submission page explaining that confirmation is required;
- a post-confirmation page;
- an optional final confirmation/welcome message;
- 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.
Copy for the confirmation journey
Keep the next action clear at each stage. These are sample messages, not tested email templates.
| Stage | Sample copy |
|---|---|
| After submitting | Check your inbox. Confirm your email address to finish joining the newsletter. |
| Confirmation subject | Confirm your newsletter subscription |
| Confirmation body | You requested our software newsletter. Use the confirmation link below to subscribe. If this was not you, ignore this email. |
| After confirming | Your subscription is confirmed. You can unsubscribe using the link in any newsletter email. |
Use Brevo's required confirmation link in the actual template. Ordinary text or a link to your homepage does not replace that confirmation action.
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:
| Test | Expected result | Evidence to keep |
|---|---|---|
| Submit valid address | Confirmation requested; not yet in normal sends | Timestamp and form source |
| Do not confirm | No newsletter campaign | Unconfirmed status |
| Confirm once | Single activation and welcome | Confirmation timestamp |
| Confirm twice | No duplicate contact or welcome loop | Contact event history |
| Unsubscribe | Suppressed from future newsletters | Unsubscribe event |
| Submit after unsubscribe | Behavior follows approved reconfirmation policy | New consent evidence if applicable |
| Delete request | Handled through documented process | Completion record without excess personal data |
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.
Enable the live form only when provider configuration, consent handling and privacy information are ready. 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
Which email should I add as the Brevo sender?
Use a real mailbox controlled and approved by the organization, ideally on its verified domain. Do not invent an address. The sender must be able to receive relevant replies and verification.
Should I enable double opt-in?
It is a strong default for list quality and confirmation evidence. It does not automatically satisfy every law or replace clear consent language and privacy information.
Can I import LinkedIn or business contacts?
Do not assume a connection or public business address permits newsletter marketing. Import only contacts whose permission and lawful basis are documented for this purpose.
Does connecting Brevo require changing MX records?
Follow only the current Brevo records for the specific verification flow. Do not change unrelated MX, website, DNS or email records. Get domain-admin review if any record conflicts.
Was this setup tested on UseAIVisora?
No. The guide is based on official Brevo documentation rechecked on 2026-08-25. It did not enable a form, change DNS, send email or test deliverability.
Research notes
Steps were checked against Brevo's sign-up form guide, GDPR-oriented form guidance, external-form double opt-in workflow and plan guide. Last rechecked 2026-08-25.
Revision scope, 9 September 2026: The form-creation and confirmation setup was rechecked against Brevo's sign-up form documentation. Sample messages were added without sending a campaign. The broader source review above remains dated 25 August 2026.
Reader discussion
Comments are public and require a GitHub account. By taking part, you agree to the Terms and Conditions and acknowledge the Privacy Policy.