• contact@insightclickiq.com
  • Every click, every session, explained by AI
Request a demo
Form analytics

See which field loses the customer, never what they typed

Every <form> is analysed automatically, field by field. Only timings, counts and a length bucket are sent; the values stay in the browser.

AI insights & AskAgentsJourneysHeatmaps & zonesFormsReplaySegmentsReportsMCPMobileExperimentsSurveysComments & sharingAI agent analyticsData platform
Form detail

The field funnel, the slow fields and the one people stop at

Starts, submits, abandons, conversion and median time for the form, then each field in order: sessions that touched it, median focus time, average visits, refill rate, empty rate, the share of abandoners whose last field it was, and the error rate (an error within five seconds of leaving the field).

On the demo checkout form, 40 sessions started and 24 submitted (60%). Five of the 12 abandoning sessions stopped at city, which is also empty 24% of the time; email takes about three times as long as a typical field, with a 22.5% refill rate.

clickiq.example.com/forms/#checkout-form
Checkout form analytics: 40 started, 24 submitted, 60% conversion, 12 abandoned, 7.8s median time; a field funnel from email (100%) to shipping (33%, 13 sessions); a ‘What the numbers say’ AI panel tagging Drop-off, Slow and Error fields; and a per-field table.
The funnel turns red at zip (−17%) and shipping (−33%). The AI notes ‘5 of 12 abandoning sessions (42%) stopped at ‘city’’ and a 15.4% error rate on the shipping radio, and suggests address autocomplete as the first fix.
Privacy by construction

What is sent for a field, and what is not

SentNever sent
Field name (name, id, aria-label or placeholder-derived), type and positionThe value, or any part of it
Focus time for this visit, number of visits, changed, refilled, emptyPassword fields and anything marked autocomplete="cc-*" or card-like
Length bucket: 0, 1–10, 11–50, 50+Hidden, submit and file inputs
On submit: fields touched and duration; on abandon: the last fieldAnything inside [data-clickiq-block]
How it works

Form analytics: from a field's blur to a finding about it

Form analytics: from a field's blur to a finding about it 1Field eventsOn blur (or changefor select, checkbox,radio): timing,visits, refilled,empty, length bucket.2Submit or abandonAbandon is sent whenthe page or route isleft with a touched,unsubmitted form.3Per-field tableInteractions, focustime, refill, empty,drop-off share, errorrate; the funnel.4AIFindingsDrop-off, slow,refill, empty anderror findings fromthe table only.5AbandonersUp to 8 abandoningsessions, replaysfirst; Investigateabandoners.No model: the rules read the top drop-off field, a field slower than twice the median, refills over 25%, empties over 40%, errors over 10%.Form analytics: from a field's blur to a finding about it 1Field eventsOn blur (or change for select,checkbox, radio): timing, visits,refilled, empty, length bucket.2Submit or abandonAbandon is sent when the page orroute is left with a touched,unsubmitted form.3Per-field tableInteractions, focus time, refill,empty, drop-off share, error rate;the funnel.4AIFindingsDrop-off, slow, refill, empty anderror findings from the tableonly.5AbandonersUp to 8 abandoning sessions,replays first; Investigateabandoners.No model: the rules read the topdrop-off field, a field slower thantwice the median, refills over 25%,empties over 40%, errors over 10%.
Works on any <form> or any element marked data-clickiq-form="name" (single-page apps without form tags). Up to 60 fields per form.
What you can ask

Questions this answers

Type them into Ask, give them to an agent as a goal, or send them through MCP from your own assistant.

Which field do people abandon the checkout form at?The drop-off field with its share of abandons
Which fields are slow or get re-typed?Focus time and refill rate, with the findings
Do errors follow the shipping field?Error rate per field
Show me sessions that abandoned the signup formAbandoning sessions with replays
Run the Form doctorAn agent run over the worst form
How long does the form take to complete?Median duration, first focus to submit
Outcomes

What teams do with it

Shorter forms, decided by data

Drop a field that is mostly left empty, or move it after the step people abandon at.

Better validation

Refill and error rates point at the fields whose format people get wrong.

Privacy review passed

There is no field value to leak, so there is nothing to mask after the fact.

Where it stops. Form analytics reads the DOM of web forms; native app forms are tracked with your own events. The error rate is a timing association (an error within five seconds), not proof the field caused it.
Heatmaps & zones Session replay Security & privacy Web SDK

Find the field that costs you

Point us at your signup or checkout form; the first findings come with a week of traffic.

Request a demo