Acquisition · capture → confirm → nurture
Lead generation isn't the form — it's the full path from a stranger's first click to a confirmed subscriber who's already inside their welcome sequence. Mumara Campaigns owns the lifecycle: Web Forms capture, double opt-in confirms, Triggers respond as they land, Drip Campaigns carry the cadence, Segmentation shapes the audience. One platform, one data model, no glue.
Alex Foster
via footer-signup form
Form submitted
footer-signup · source tag: footer
Confirmation email sent
double opt-in · awaiting click
Confirmed
status flipped to active
Trigger fired
"Footer signup confirmed" → start drip
Welcome drip · email 1
"Welcome to Acme" delivered
One contact. Five events. All inside Mumara — no webhooks to Zapier to spreadsheet.
Built for the full pipeline
The platform's compound advantage is that it owns every step. The form knows about the trigger; the trigger knows about the drip; the drip knows about segmentation. The contact moves through without leaving.
Embed anywhere
When you've built a Web Form in Mumara, the Embed dialog gives you two paths to put it on your site. The HTML Embed tab hands you a ready-to-paste snippet you drop into your footer / sidebar / landing page. The Post URL tab gives you a direct endpoint — useful when you've built your own form HTML and just need somewhere to POST it. Hidden fields like UTM tags auto-flow into source attribution on the contact record.
A ready-to-paste <form> snippet with the right action URL, the right field names, and the right hidden values. Style it however you like — Mumara never imposes presentation.
Bring your own form HTML and POST submissions to the Mumara endpoint. Useful when your designer has already built the form and you don't want to re-build it in Mumara's builder.
Hidden field `source: footer-signup` (or whatever you set) lands on every submitted contact. Downstream segmentation can filter 'everyone who came in via the footer signup' — without you wiring anything extra.
The Copy code button puts the snippet on your clipboard. The Or POST directly to row beneath gives you the raw endpoint when you want it without the wrapper.
Three lead-capture patterns
Most lead-gen pages on most sites are one of three patterns. Mumara's Web Forms + Triggers + Drips combination handles each, with the same building blocks composed differently.
Low-friction
Single email field, single opt-in (or double for compliance), thank-you redirect, immediate drop into a recurring newsletter cadence. The "footer signup" pattern every content site runs. Auto-tag with the form ID for source attribution; let segmentation pull the right audience as engagement data accumulates.
Higher intent
Form with 3-5 fields (email + first name + company + role). Double opt-in mandatory for compliance and lead quality. Confirmation email delivers the asset (PDF, video, template). Trigger fires once confirmed; drip starts a 5-7 step nurture sequence ending in a sales-ready outreach. Auto-tag with the asset name for cross-asset performance comparison.
List-builder
Form with a date or interest field. Confirms inclusion. Trigger fires at a specific later date (event start, product launch, waitlist opening). Useful for product launches, webinar registrations, beta sign-ups — anywhere the value of the signup is "I want to know when X happens" and the platform has to wait until X to act.
Web Forms vs Lead Generation
Both terms are used in marketing, and they're not interchangeable. Knowing the distinction makes the platform pages easier to navigate.
[Web Forms](/campaigns/features/web-forms/) is the form-builder UI — the mechanic for capturing a contact. It covers field types (email, text, date, dropdown, hidden), the wizard for building forms (4 steps — Details / Confirmation / Welcome / Error), embed options (HTML or POST URL), and the form-level settings (double opt-in toggle, reCAPTCHA, multi-list submit). If you want to know how a form actually works on Mumara, that's the page.
Lead Generation is the broader story — the funnel that uses Web Forms as one of its components. The page you're reading covers the full lifecycle: capture (Web Forms), confirmation (the Double Opt-in flow), journey start (Triggers), nurture (Drip Campaigns), long-term audience shape (Segmentation). It's the strategic view; Web Forms is the tactical mechanic underneath.
Most pages in marketing platforms blur the two. Mumara separates them on purpose — when a customer asks "how do I capture leads from my site?" the right answer depends on whether they mean the form-builder details (Web Forms) or the post-capture journey (Lead Generation + Triggers + Drips). Reading both pages gives the complete picture.
One platform, end-to-end
What actually happens between a visitor seeing the form and them being two emails into the onboarding sequence. The whole flow runs inside Mumara — no Zapier, no glue, no sync lag.
Step 1
Embedded on your site or landing page. Mumara renders the form, or you provide the markup and POST to Mumara. Either way, no JavaScript dependency on a third-party widget.
Step 2
The form data hits Mumara. reCAPTCHA validates if enabled. Field validation runs. On pass, a new contact record is created with the form's tags, the source attribution, the consent timestamp + IP.
Step 3
When double opt-in is ON, contact gets a confirmation email immediately and is held in pending status. When they click confirm, status flips to active. When OFF, contact goes straight to active. Either way, the audit trail is preserved.
Step 4
A Trigger watching "contact added to list X" acts as soon as the contact lands; one watching "contact reaches segment Y" runs on the trigger cycle you set in Cron Settings (as fast as a minute). Trigger actions can copy/move to another list, send a broadcast, start a drip group, notify an admin, update a custom field.
Step 5
The Drip Campaign begins. First email goes out per the drip's schedule (immediate, day 1, day 3, etc.). Each subsequent step waits the configured delay. Engagement feeds segmentation as it accumulates, refining downstream targeting.
Four common funnels
Common questions
No — it's the strategic view on top of Web Forms + Triggers + Drips + Segmentation. Web Forms is the mechanic (the form builder). Lead Generation is the pipeline (form → confirm → trigger → drip → segment). Both pages exist to give buyers two angles into the same surface: tactical ("how does a form work?") and strategic ("how do I run lead generation?"). The platform is one thing; the pages document different lenses.
No. The capture (Web Forms), the confirmation flow, the post-signup automation (Triggers + Drips), the audience shaping (Segmentation), and the long-term communication (Broadcasts) all run on the same platform with the same contact record. No Zapier, no Make.com, no glue scripts. The exception is if you're capturing leads in a SaaS tool Mumara doesn't directly integrate with (e.g. a typeform-style builder) — then the [REST API](/campaigns/features/rest-api/) and [Webhooks addon](/campaigns/addons/webhooks/) are the connection layer.
Each Web Form has a Double Opt-in toggle. When ON, a contact who submits the form lands in the list with pending status, gets a confirmation email, and only becomes active when they click confirm. The confirmation timestamp + IP are recorded permanently on the contact record for compliance evidence. Triggers fire on the active state — so a 'contact added to list X' trigger doesn't fire until the contact actually confirms. Useful for compliance (CASL, GDPR) and lead quality (filters bot signups and accidental submissions).
Yes — every Web Form can be configured with custom tags applied to every contact submitted through it. Combined with hidden form fields populated by URL parameters (utm_source, utm_campaign, referrer), you get full source attribution baked into the contact record. Downstream segmentation can then filter by source — 'show me everyone who came from the May newsletter referral campaign' is a saved segment query.
A Trigger fires. The trigger is configured to watch for 'contact added to list X' or 'contact reaches segment Y' or 'contact custom-field equals Z'. When that condition matches a newly-confirmed contact, the trigger's action runs — copy to another list, send a broadcast, start a drip group, notify an admin, update a field. A confirmation is a contact-based event, so a trigger set to Instantly acts without waiting for a batch; segment-based matches run on the trigger cycle you set in Cron Settings (as fast as a minute).
Yes — and this is the typical pattern. Auto-tag each form with a unique tag. Build a Trigger per tag that starts a specific Drip Campaign. A user who signed up via the 'whitepaper-2026' form gets the whitepaper-2026 nurture; a user who signed up via 'webinar-may' gets the webinar-follow-up sequence. The contact record carries the tag forever, so segmentation can recombine them later.
Yes — Web Form fields can map to any contact field, including custom fields. A B2B lead form with role and company-size fields maps those values directly into custom fields on the contact record. Drip Campaigns and Broadcasts can then personalise based on those fields ([Personalization Options](/campaigns/features/personalization-options/)), and Segmentation can filter by them.
Mumara's [A/B Testing](/campaigns/features/ab-testing/) is for broadcast variants today, not form variants. To A/B test forms, the typical pattern is to run two separate Web Forms with different fields or layouts on different landing pages, then compare conversion rates in the per-form statistics. The platform tracks form-level submissions, so the comparison is in the reporting surface.
Web Forms support reCAPTCHA V2 and V3 — toggle per form. V3 is invisible (score-based), V2 shows the checkbox challenge. Combined with double opt-in (which filters bot signups that don't click the confirmation link), bot signups become statistically negligible for most installations. See [Web Forms](/campaigns/features/web-forms/) for the full anti-abuse surface.
Related
The form-builder mechanic — fields, embed options, double opt-in, reCAPTCHA, multi-list submit.
Read moreFires when a new contact lands. Starts the post-signup journey — drip, broadcast, field update.
Read moreThe nurture cadence — multi-step welcome sequence with conditional branching based on engagement.
Read moreLong-term audience shape — combine signup source, behaviour, and profile data into reusable segments.
Read moreDouble opt-in is the cornerstone of CASL / GDPR-aligned lead generation. The audit trail is part of the platform.
Read moreWhere the captured contacts live — lists, custom fields, the data model behind every later action.
Read moreMumara Campaigns · Lead Generation
Web Forms, Double Opt-in, Triggers, Drips, Segmentation — every piece ships with Mumara Campaigns. Self-Hosted and Mumara Machine both. No Zapier, no glue, no integration sync lag. The complete lifecycle from first click to engaged subscriber lives in one contact record.
