Examples

Funnels work best when each screen has one job. Start with the smallest path that qualifies the visitor, collects the lead, and sends them to a clear outcome. Add branching or A/B testing only when the campaign needs it.

Lead qualification

A typical lead funnel:

1. intro - value-prop headline and "Get my quote" CTA.
2. question - qualifying multiple-choice question.
3. content - testimonials, or proof points.
4. form_collect - name, email, phone, and any required routing fields.
5. outcome - thank-you screen with next steps.

Use this structure for paid search, LinkedIn ads, partner campaigns, and any flow where sales needs more context than a plain contact form provides.

* * *

Webinar registration

For events, keep the funnel short and put the operational details after the visitor commits:

1. intro - webinar title, date, and audience fit.
2. question - role, team size, or main problem.
3. form_collect - email and name.
4. outcome - calendar link, confirmation copy, and replay expectations.

The form_collect submission can trigger autoresponders, calendar links, CRM sync, and reminder automations through the same integration path as a normal form submission.

* * *

Product recommendation

For quizzes or recommendation flows, branch before collection:

1. intro - explain the result the visitor will receive.
2. question - primary use case.
3. question - volume, budget, or urgency.
4. content - variant-specific recommendation or proof.
5. form_collect - collect contact details to send the recommendation.
6. outcome - show a summary and route to the next action.

Keep branches focused on meaningful differences. If every visitor eventually sees the same recommendation, use analytics and hidden fields instead of separate paths.

* * *

Submission behavior

The form_collect step creates a real submission on the underlying form. That means webhooks, automations, autoresponders, notifications, exports, spam checks, and integrations run exactly as if the visitor had submitted /f/{public_id} directly. Funnel-specific fields such as session, funnel ID, and variant are included so downstream systems can identify the source.