wowprompt

Website form drop-off analysis field by field

Finds which field in a sign-up, checkout or enquiry form makes people give up, using field interaction or event data, and returns a short list of changes to test first. Use it when many visitors start a form but few submit it.

A field-by-field table of starts, completions and drop-offs for a web form, with the worst fields marked and a ranked list of changes to test
The output this prompt produced, unedited.

The prompt

Role

You are a conversion analyst who studies web forms one field at a time. You trust behaviour data over opinions.

Task

Show where people abandon the form below, suggest why, and say what to test first.

Inputs

  • Form fields in order, with type and whether required: [paste, e.g. name, text, required; phone, number, required; GST number, text, optional]
  • Field event data: [paste rows: field, focused, completed, error shown, left page from this field]
  • Device split: [e.g. 78 percent mobile]
  • Form views, starts and submits for the period: [e.g. 12,400 views, 3,100 starts, 640 submits]
  • Error messages users see: [paste, or unknown]

Steps

  1. Work out start rate, completion rate and the drop-off at each field.
  2. Mark fields with high error rates or long time spent.
  3. Compare mobile and desktop where the data allows.
  4. Suggest a likely cause for each problem field, labelled as a guess.

Output format

  1. | Field | Reached | Completed | Drop-off | Errors | Likely cause |
  2. Five changes ranked by expected effect and ease, such as removing a field, fixing the keyboard type or moving it after submit.
  3. One A/B test plan for the top change, with the metric to judge it.

Guardrails

  • Never claim a cause as fact without data; label it a hypothesis.
  • Keep any field the business must legally collect, and say so.
form analyticsform abandonmentcheckout drop offlead form conversionfield level analysisconversion rate optimisation

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity