An opt-in form is a small piece of interface with an outsized job: it is the moment consent either exists or does not. The wording on the screen and the fields in the database have to match, because a year later the question is never did they tick the box, it is what were they shown and what did it say. Six examples below, three that work and three that do not.
Three that work
A newsletter box with an unticked checkbox reading send me the monthly summary, you can unsubscribe from any email, and a link to the privacy notice beside it. A checkout with a separate, clearly optional line offering product announcements, with the purchase working identically either way. And a webinar registration that says plainly what the organiser will send afterwards and, where a partner is involved, names the partner rather than saying our partners. In each case the purpose is specific, the choice is real, and the wording can be stored verbatim.
Three that do not
A pre-ticked box, which is not an affirmative action and produces nothing. A single tick covering terms, privacy policy and marketing together, which is not specific and not freely given because the service depends on it. And a form whose only wording is a link labeled privacy policy, which informs nobody about what will arrive. Each is common, each looks compliant at a glance, and none of the three produces a record you could show anybody.
What to store when it is pressed
The identifier for the person, the purpose in words rather than a column name, the exact wording displayed as a string, the timestamp with a timezone, and where the submission came from. Store it as an event rather than a flag, so that later changes add rows instead of overwriting the answer to the question you will actually be asked. Withdrawal is stored the same way, which gives you a complete history per person in one table.
The details that raise the rate and the quality together
Say what arrives and how often, because vagueness costs sign-ups and produces weaker consent at the same time. Ask for as little as possible: every extra field reduces completion and adds data you then have to justify holding. And send a confirmation, which both verifies the address and produces a second piece of evidence. None of these is a trade-off between conversion and compliance; the same choices help both.
Questions people ask about opt in form examples
Is double opt-in required?
Not by the regulation. It is the cheapest way to get a record you can rely on and to keep bad addresses off the list, which is why most senders use it.
Can we require marketing consent to download a guide?
Exchanging the guide for the email is a contract-like trade and is common. Bundling a broader marketing consent into it is where it stops being freely given, so keep the guide's delivery and the ongoing list as separate choices.
Does a US sender need opt-in at all?
CAN-SPAM works on an opt-out model with its own duties about unsubscribing, headers and a postal address. Opt-in is required for European recipients and is better practice regardless, because the list performs better.