Build a permission-based email list with a clear signup offer, useful placement, and records that survive imports and platform changes.
A useful email list is a record of people who want a particular kind of message from you. The number of rows is secondary.
Start with the promise. What will a subscriber get that they cannot get by occasionally visiting your homepage? If the answer is unclear, a larger signup form will not help.
A weekly analysis, release notes for a product someone uses, or a practical course can all work. Choose something you can keep producing. If the signup offers a download, make clear whether it also subscribes the person to ongoing marketing.
Show an example before asking for an address. A recent newsletter issue or a preview lesson lets readers judge the content instead of guessing from a headline.
Keep the form short. Ask for additional information only when it changes what you will send. You can learn more later through preferences, replies, or product behavior.
Near the form, answer the questions a careful reader asks before typing an address:
An article about a problem is a sensible place to offer a related guide. A product's settings page is a sensible place to offer release updates. A checkout can offer marketing signup, provided the choice is clear and separate from completing the purchase.
For events, explain who will email attendees and why. A scanned badge does not tell you which messages the person expected. For partnerships, let people choose each sender; exchanging contact files is a poor substitute.
A popup that blocks the material someone came to read asks for trust before earning it. If you use one, keep it dismissible and test its effect on reading as well as signups.
Each of these asks the person directly and leaves a record of what they chose.
You do not need all eight at once. Start with the two or three closest to where your readers already spend time. Add another once you can see which sources bring in subscribers who open, click, or reply.
These leave you without a clear record that the person chose your email:
If someone asks where you got their address, you should be able to answer from your records.
Store when and where the person subscribed, the promise shown at signup, and their current subscription status. Confirmation emails can help establish that the address belongs to the person submitting it. They also reduce accidental and malicious signups.
Give each form and tactic its own source value, such as article-inline or webinar-registration, and store it with the signup. Without it, the source comparison below has nothing to work with.
Keep suppression and unsubscribe records when moving platforms. Do not turn an import into a new subscription. Brew's import workflow still depends on the audience and status data you supply.
Brew requires permission-based marketing. Legal obligations differ by location; the FTC's commercial email guidance describes US requirements, not a universal consent rule.
Measure whether new subscribers read, click, reply, or use what you send. Compare signup sources over time. A source that produces many addresses and immediate unsubscribes is probably attracting the wrong audience or making the wrong promise.
The page after the form matters too. Tell the person what happens next, including whether they need to confirm by email, when the first message will arrive, and where to find anything you promised.
Send a welcome email while the signup is still familiar. Deliver the promised resource first, explain what comes next, and make leaving easy.
For an old list with unclear origins, do not assume silence means permission. Review its source records before sending. A smaller list that recognizes your name is a better foundation for reliable delivery.
