form-analyzer

Form Analyzer

Field-by-field form analysis — which fields cause abandonment, where validation errors hit, how long each field takes, and where users get stuck.

When to Use

• "Which field on the signup form has the highest abandonment?"
• "Why are users dropping off at the password field?"
• "How long does it take users to complete the checkout form?"
• "Which form fields trigger the most validation errors?"
• "Compare form completion on mobile vs desktop"
• "Did the new inline validation reduce form abandonment?"

Mental Model

A form is a sequence of fields users must fill. Each field is a micro-funnel: enter → validate → proceed. The goal is to find which fields cause users to stall, error, or abandon.

Forms have unique failure modes:

• Confusion: Users don't know what to enter (e.g., "Username" vs "Email")
• Validation friction: Strict rules reject valid input ("Password must contain a special character")
• Technical failure: Field doesn't respond, autofill breaks, input type mismatch
• Trust barrier: Asking for too much info too early ("Why do you need my phone number?")

For visual checks, follow session-review: open with fullstory:review-open, pass its client_id to fullstory:review-snapshot at the target timestamp, and always call fullstory:review-close, including on errors. Delegate repeated captures to session-replay.

Use free fullstory:discover_groups and fullstory:get_opportunity_stats for live signals. Discovery accepts one scope at a time (page_id, domain, app_name, segment_id, or funnel_id); use a segment for device/user filters and the live schema for time ranges. Use computed metrics for exact custom windows.

Workflow

Step 1: Identify the form

Clarify which form and what success looks like:

• Form page: /signup, /checkout, /contact
• Success event: page navigation to /signup/confirmation, custom event form_submitted, or purchase completion
• Fields of interest: all fields, or specific ones the user suspects