Screens

Supported screen kinds:

• intro - landing screen with headline and CTA
• question - single-question step (used for branching)
• content - informational content / value prop
• cta - call-to-action button
• form_collect - captures lead fields and creates a Submission
• redirect - sends the visitor to a URL
• outcome - final result screen (used with scoring)

Each screen has a position, a kind, a free-form config object, and an optional ab_variant_key. Screens with a variant key only render to sessions in that variant.

Screen order

The position controls the default flow. Visitors start at the first active screen and move forward unless branching or redirect behavior sends them somewhere else. Keep the first screen focused on the promise of the funnel, then ask only the questions needed to qualify or route the visitor.

* * *

Collection screens

form_collect is the bridge from funnel session to normal form submission. When it succeeds, Formspring creates the underlying Submission and includes funnel metadata in the payload. Put required lead fields here, and keep earlier question screens focused on qualification so the final collection step stays short.

* * *

Variant-specific screens

ab_variant_key lets you attach a screen to one experiment variant. Screens without a variant key are shared. A typical test keeps the intro and final collection screens shared, then swaps one question, proof screen, or offer screen per variant.

* * *

Content and redirect screens

Use content for proof, explanation, or reassurance between questions. Use cta or redirect when the goal is an external action instead of a form submission. Redirects still record funnel events, which makes them useful for tracking outbound bookings, payment links, or partner handoffs.