Double Opt-In
Double opt-in asks a new subscriber to confirm their request by email. Learn what confirmation establishes and how to handle pending contacts.
Double opt-in adds an email confirmation step to a subscription request. A person submits a form, receives a confirmation message, and confirms before marketing begins.
What confirmation establishes
The extra step helps check that someone can access the address they entered. It can catch a typo or a signup submitted by someone else, but it does not guarantee engagement or exclude every disposable address.
Confirmation can support a consent record. Keep the signup wording, purpose, source, and relevant timestamps as well. A confirmation click alone does not establish compliance with every law. The US CAN-SPAM rules and UK electronic-marketing consent rules differ. See the FTC guide and ICO guidance.
Handle the pending state
Keep the confirmation message focused on the subscription request. Name the sender and mailing list, explain the action, and test the confirmation flow on a phone. Decide how to handle expired links and unconfirmed records according to your retention policy.
In Loops, double opt-in currently gates Form endpoints, while API contact creation and updates need separate permission checks. Pending contacts are not automatically deleted. Confirmation controls marketing. It does not block account-critical transactional email. See the double opt-in documentation before implementing either path.