Double Opt-In
Double opt-in asks new subscribers to confirm their email address before they become active. Use it when you want cleaner lists, stronger consent records, and fewer fake or mistyped signups.How It Works
- A visitor submits a signup form, or an API call creates a subscriber with double opt-in enabled.
- Sequenzy stores the subscriber as
unsubscribedwhile confirmation is pending. - Sequenzy sends your confirmation email with a signed confirmation link.
- After the subscriber clicks the link, Sequenzy changes the subscriber to
active. - Sequenzy adds the subscriber to the target lists, applies signup tags, and triggers matching automations.
Requirements
Before enabling double opt-in, set a default sender profile for the workspace. Sequenzy uses that sender for the confirmation email. When you enable double opt-in for the first time, Sequenzy creates a confirmation email template for you. You can edit it like any other email, but it must include the{{DOUBLE_OPT_IN_URL}} variable somewhere in the content. Sequenzy replaces that variable with the subscriber’s confirmation link at send time.
Enable Double Opt-In
- Go to Settings → Email Tracking.
- Find Double Opt-In.
- Turn on Enable double opt-in.
- Click Edit confirmation email if you want to customize the subject, copy, design, or button text.
- Save your settings.
Signup Forms
Embedded signup forms follow the workspace double opt-in setting. When double opt-in is enabled:- Form submissions create pending subscribers with
status: "unsubscribed" - Selected list IDs and tags are held until confirmation
- The confirmation email is sent automatically
- The success message or redirect still runs after the form submission succeeds
Signup Form Widget
Learn how embedded signup forms work with double opt-in.
Events, Webhooks, and Tags
Contacts are not only created by signup forms. Events from external apps (Tally, Cal.com, Typeform, and other webhook triggers), the events API, and tag operations can also create brand-new contacts. These paths follow the workspace double opt-in setting too. When double opt-in is enabled and an event or tag creates a new contact:- The contact is stored as
unsubscribedwhile confirmation is pending, and the confirmation email is sent automatically - The event is still recorded and tags are still applied, so your data stays complete
- List membership is held until confirmation
- Sequences triggered by the event or tag enroll the contact immediately, but the enrollment is parked at the trigger step - no emails send yet
API Behavior
The subscriber API accepts anoptInMode field:
| Value | Behavior |
|---|---|
default | Follow the workspace double opt-in setting for new active subscribers. This is the API default. |
confirmed | Create or keep the subscriber active immediately when you have verified consent. |
double_opt_in | Force a confirmation email for this request. The subscriber stays unsubscribed until they confirm. |
confirmed for server-side flows where your app already verified consent, such as paid customer syncs or explicit in-product opt-ins. Omit optInMode or use default when you want the workspace setting to decide for new subscribers. Use double_opt_in when this one request must require confirmation regardless of the workspace setting. default does not send confirmation email to an existing unsubscribed contact.
optIn object:
Create Subscriber API
See the full subscriber create request and response reference.