Form Analytics That Actually Help You Ship: How FlexForm Tracks Submissions, Sources, and Peak Hours

Most form builders ship analytics that tell you the total. FlexForm ships analytics designed to be acted on. Every submission carries the country it came from, the campaign that drove it, the embed it loaded inside, the active seconds the respondent actually spent, and the page they finished on. The aggregation runs in Postgres against an index, so the analytics page loads in under 200ms whether the form has 100 submissions or a million.

This post walks through what FlexForm tracks, where each field comes from, how the analytics endpoint stays constant-size at scale, and what the data lets a team actually do — pause Friday ad spend, route mobile traffic differently, retire a country-specific form variant, ship the next change.

Where each metric comes from

FlexForm captures metadata at three points: when the session is created, when the respondent navigates between pages, and at submission. The capture path is deliberately split so that even abandoned drafts carry enough metadata to be useful for funnel analysis later.

Why server-side aggregation matters

A common mistake in form-builder analytics is fetching every submission row to the browser and computing aggregations client-side. This works at 1,000 rows. It dies at 100,000.

FlexForm runs six parallel GROUP BY queries against the (form_id, submitted_at) composite index: total + timing, by day, by hour, by UTM source, by device, by browser, and by country. The response payload is the same shape every time. A workspace with three forms and a million combined submissions still loads its analytics page in well under a second.

The analytics endpoint

A single endpoint serves the entire analytics dashboard. It accepts a date range, a status filter, and an IANA timezone, and returns everything the dashboard renders in one round trip.

GET /forms/:id/submissions/analytics
    ?tz=Asia/Kolkata
    &from=2026-04-01
    &to=2026-05-15
    &status=submitted

{
  "total": 1248,
  "withTiming": 1190,
  "avgTimeSec": 187.4,
  "medianTimeSec": 142.0,
  "peakHour": 14,
  "embedCount": 312,
  "timezone": "Asia/Kolkata",
  "byDay": [ { "date": "2026-05-01", "count": 42 } ],
  "byHour": [ { "hour": 14, "count": 187 } ],
  "bySource": [ { "label": "google", "count": 540 } ],
  "byDevice": [ { "label": "desktop", "count": 820 } ],
  "byBrowser": [ { "label": "Chrome", "count": 710 } ],
  "byCountry": [ { "label": "India", "count": 480 } ]
}

What this lets a team actually do

The point of the dashboard is not the chart. It is the next action. Five concrete moves the data unlocks on a typical lead-gen form:

1. Pause Friday paid traffic — if byDay shows Friday submissions are 40% below Monday at the same spend, route budget elsewhere.
2. Reskin the mobile layout — if byDevice shows 87% mobile but the form was designed at desktop width, the layout work is overdue.
3. Cut the country-specific form variant — if byCountry shows 92% of conversions from three countries, the long-tail variants are operational debt.
4. Restructure the embed strategy — if embedCount is 312 out of 1,248, a quarter of submissions come from partner sites; their embed placement is the highest-leverage thing to tune. Web embed reference.
5. Front-load the form for the peak hour — when peakHour is 14, schedule sales follow-up coverage for 2–4pm local time and route those submissions to the on-call rep.

How FlexForm compares

Most form builders track submissions over time and average response time. The gap shows up in everything else.

Frequently asked questions