Newsletter signup flow

Wire the form, the double opt-in, the welcome email, and the email-provider integration end to end

A working newsletter signup has four moving parts: the form that captures the email, a double opt-in step that confirms the address belongs to the person who submitted it, a welcome email that lands in the inbox within minutes, and an integration that pushes the subscriber to the email provider so future campaigns can reach them.

Stop at the form and the rest does not happen. This recipe wires all four parts together — first time, no rework.

What is this for?

Use this recipe to set up a complete signup path on a new site, or to fix a half-built one where the form captures emails but nothing else fires. The end state: a visitor submits the form, gets a confirmation email, confirms, lands in the welcome flow, and shows up in the email provider's list — all in under a minute from submit to inbox.

The end state:

• A SGEN form with an email field and consent checkbox.
• A double opt-in step that sends a confirmation email and waits for the click.
• A welcome email that sends once the visitor confirms.
• An integration to the email provider (Mailchimp, Klaviyo, or a webhook to whatever else is in use).

Good use cases

Site launch. New site, no list yet. Footer form plus a popup at exit intent. Both feed the same flow.

Existing list, broken flow. Site has been collecting emails for a year but the welcome email never went out and the provider was never connected. The form-submissions inbox has 400 unread entries.

Two lists. Weekly digest and monthly product email. Single form with a preferences select; integration routes each subscriber to the right list.

What NOT to use this for

• Pre-checked consent. Pre-ticking the marketing checkbox is not valid consent under GDPR. The checkbox stays unchecked by default and only counts if the visitor ticks it themselves.
• Single opt-in for cold-list import. Importing a purchased or scraped list with no consent record is a different recipe (and usually a bad idea). This recipe assumes opt-in from a real submission.
• A standalone CRM. SGEN form submissions are a safety net. Real list management lives in the email provider — Mailchimp, Klaviyo, or similar.

How this connects to other features

• Forms — the signup form lives here. Same form can be embedded in a popup, the footer, or a standalone page.
• Form Integrations — the integration to the email provider lives here. SGEN supports common providers and a generic webhook for everything else.
• Form Submissions — every submission lands in Forms → Submissions regardless of whether the integration fires. This is the safety net if the provider is down.
• Custom Codes — the welcome email template can use Custom Codes for shared header and footer markup.

Before you start

You are signed in as an Administrator. You have an account at the email provider you plan to use (Mailchimp, Klaviyo, or another). You have an API key or the webhook URL ready.

You have the welcome email body written — a short paragraph, one or two links, and a way to manage preferences. Writing the email mid-build slows the work.

You have legal sign-off on the consent checkbox copy and the privacy policy link.

Pre-build checklist:

The sending domain authentication (SPF + DKIM) is the most commonly missed prerequisite. If the domain is unauthenticated, the confirmation and welcome emails land in spam at a high rate from day one. Check this before setting up anything else.

Where to find it

Steps

1. Build the signup form

Navigate to Forms. Click + Add New. Title the form Newsletter Signup. Add the fields:

The consent checkbox label reads something like: "I want to receive the newsletter and accept the privacy policy." Keep the label short and the link visible.

Set the success message to: "Almost done. Check your inbox for a confirmation link." Save the form.

2. Turn on double opt-in

In the form settings, find the Double opt-in toggle and switch it on. Set the confirmation email subject to something the visitor will recognise — "Confirm your signup for [site name]" — and write a one-paragraph body with the confirmation link.

The confirmation flow: the visitor submits the form, SGEN holds the entry as Pending, sends the confirmation email, and only moves the entry to Confirmed when the visitor clicks the link. Until they click, the entry is not yet a real subscriber.

3. Connect the email provider integration

Open the form. Click the Integrations tab. Pick the email provider from the list. Paste the API key or webhook URL.

Map the form fields to the provider's fields:

• Email → primary email
• First name → first-name field
• Consent → consent timestamp (the provider should record the date)

For a generic webhook, the integration sends a payload with every form field plus a timestamp. The receiving service handles the mapping. Test the webhook with one submission before relying on it.

4. Write the welcome email

Navigate to the email provider's automation panel. Create a new automation triggered by "subscriber added" or "subscribed" — the exact label depends on the provider.

Keep the welcome email short:

• One paragraph that confirms what the visitor signed up for and what they will receive.
• One or two links to recent posts or featured pages.
• A clear "Manage your preferences or unsubscribe" link at the bottom.

The welcome email fires from the email provider, not from SGEN. SGEN's role ends once the integration push succeeds. From there, the provider handles the inbox delivery.

5. Embed the form on the site

Decide where the form goes. Common picks:

• Footer — visible on every page. The widest top-of-funnel reach.
• Dedicated subscribe page — /subscribe/ or similar. Linked from the main menu.
• Exit-intent popup — fires when the visitor moves toward the browser chrome. Higher capture rate on first visit.

For any of these, embed the form with the SGEN form shortcode in the relevant Page, Template, or Popup body. The shortcode renders the same form everywhere it appears.

After the first week of live signups, the Submissions inbox shows entries in two states — Pending (awaiting confirmation click) and Confirmed (pushed to the provider). Confirmed entries are the ones that count as real subscribers:

6. Test the full path

Submit the form with a real email address you control. Walk through every step:

1. The submit shows the success message: "Almost done. Check your inbox for a confirmation link."
2. The confirmation email arrives within a minute. Open it.
3. Click the confirmation link. The browser shows a Confirmed page or a redirect to the site.
4. The form-submissions inbox shows the entry as Confirmed.
5. The email provider shows the new subscriber in the list.
6. The welcome email arrives in the inbox within a few minutes of confirmation.

Run the test from a fresh email address — not one already in the provider's list. Existing subscribers may skip the welcome flow.

7. Verify drop-offs and re-send capacity

Navigate to Forms → Newsletter Signup → Submissions. Filter by status:

Some entries will sit in Pending — visitors who submitted but never confirmed. Decide on a re-send window (most sites pick three to seven days) and configure the re-send rule in form settings. SGEN re-sends the confirmation email once after that window; entries still Pending after the re-send drop off the list.

What success looks like

After all seven steps:

1. A visitor signs up from any embed location and gets the confirmation email within a minute.
2. Clicking the confirmation link moves the entry from Pending to Confirmed.
3. The email provider receives the subscriber automatically.
4. The welcome email arrives in the inbox within a few minutes of confirmation.
5. Form-submissions inbox holds every entry as a backup — even if the provider integration fails.
6. Pending entries that go un-confirmed re-send once, then drop off.

What to do if it does not work

The confirmation email never arrives. Check the form-submissions inbox to confirm the entry exists. If the entry is there but the email is not, the email-sender settings in Settings → Email are off or pointing at a domain with no DNS. Re-check the SPF / DKIM records for the sending domain.

The confirmation link returns a 404. The confirmation URL in the email is pointing at a stale or wrong domain. Open the double opt-in settings and confirm the confirmation URL uses the live site domain, not staging.

The provider integration does not fire. Open Form Integrations. Confirm the API key or webhook URL is correct. Try a test submission and watch the integration log — most providers log push attempts with a status code. A 401 means the API key is wrong; a 422 means the field mapping is off.

The welcome email goes to spam. The sending domain in the provider is unauthenticated. Add SPF and DKIM records at the DNS provider and retest. New-domain warm-up takes a few weeks before deliverability stabilises.

Subscriber appears in the list with no consent timestamp. The consent field is not mapped in the integration. Open the integration, map the consent checkbox to a field the provider records on the subscriber, and re-test with a new submission.

Variations

Single opt-in for specific use cases. Double opt-in is the right default. In some contexts — in-person event signups, handwritten list imports where the person was physically present — single opt-in is more appropriate. SGEN supports turning off double opt-in per form. Use single opt-in deliberately, not as a shortcut, and document the reason in the form notes field.

Pop-up form on exit intent. The same newsletter form embedded in a popup that fires when the visitor moves toward the browser chrome on their first visit. The popup uses the same SGEN Form shortcode as the footer. All submissions from the popup go through the same double opt-in path and land in the same provider list. Set the popup to fire once per session — re-firing on every page is a friction point.

Subscriber preferences center. Instead of one list, the brand runs three: weekly blog digest, monthly product news, and event announcements. The signup form includes a Preferences multi-select. The integration reads the preferences value and subscribes the contact to the matching lists. The welcome email confirms which list they are on. A "Manage your preferences" link in the footer gives subscribers control without unsubscribing entirely.

Re-permission campaign for an old list. A list that predates double opt-in, or a list migrated from another provider without consent records, cannot be mailed without risk. Run a re-permission campaign: import the old list into a separate segment, send one email asking them to re-subscribe via the new form, and wait 14 days. Contacts who re-subscribe enter the standard double opt-in path. The rest are suppressed.

Anti-patterns

Pre-ticked consent checkbox. Pre-ticking the marketing checkbox is not valid consent under GDPR. The checkbox starts unchecked and only counts when the visitor actively ticks it. A pre-ticked form may collect more addresses in the short term and creates a compliance liability.

Welcome email from a provider subdomain with no authentication. The welcome email arrives from mg.yourdomain.com or a provider-managed subdomain because SPF and DKIM were not set up on the main sending domain. Deliverability is lower, unsubscribes are higher, and the sender name looks off. Authenticate the main domain before launching.

Form submissions as the primary list. SGEN form submissions are a safety net — they catch the entry if the provider integration fails. They are not a list management system. Real list management, segmentation, and campaign sends happen in the email provider. Import from the submissions backup only when recovering from a provider outage.

Same form on every page without scoping. Embedding the newsletter form in a popup that fires on the checkout confirmation page or the order-received page is jarring. The visitor finished a purchase; a newsletter signup interrupt is friction at the wrong moment. Scope the popup to content pages, blog posts, and the homepage. Exclude checkout, account, and confirmation pages.

Examples

Single list, footer only. One form, footer embed, Mailchimp integration to a single audience. Welcome email is one paragraph plus a link to the most recent post. Total setup: 30 minutes.

Two-list preference selector. One form with a Preferences select — Weekly Digest, Monthly Product, or Both. Integration uses a webhook that reads the preferences value and pushes to the right list in the provider. Two separate welcome emails, one per list.

Popup + footer + dedicated page. Same form, three embed locations. Exit-intent popup fires once per visitor. Footer is always visible. /subscribe/ is linked from the main menu. All three feed the same form, the same opt-in path, and the same provider list.

After a month of live signups, the form submissions view shows the pipeline from submit through confirmation. Confirmed entries are real subscribers; Pending entries are still in the inbox waiting for the confirmation click:

The public subscribe page sets the right expectation before the visitor commits — one email a week, no noise, cancel any time:

Related recipes

• Lead-magnet funnel — when the signup is incentivized by a free asset, the newsletter form wires into the same delivery pattern as the lead-magnet capture form
• Customer onboarding emails — post-purchase email automation uses the same form integration and trigger pattern as the newsletter flow
• Blog content calendar — 90-day plan — the newsletter cross-post in the weekly check-in ties directly to the calendar; plan newsletter sends against the blog publish schedule

Related reading

• Forms overview
• Build a form
• Form integrations overview

Last updated: 2026-05-25