Every other number in NueForm starts at "someone answered something". Visits is the one that sees the people who arrived and left without touching a question — usually the largest group on any form, and the one you can actually do something about.
A visit is one page load of your published form. Repeat visits count. If the same person opens your form four times, that's four visits — deduplicating them would hide exactly the behaviour worth knowing about, like a respondent who keeps coming back and never finishes.
Where to find it
- Visits tab on a form's dashboard — the full picture for one form.
- Visits column on your forms list and on
/fuseforms, for scanning many forms at once. - Traffic (section D) in Analytics, for your whole workspace.
- Team analytics shows a Total Visits tile beside Total Responses.
Reading the numbers
Visits vs Visitors. Visits counts page loads. Visitors counts distinct browsers. Two very different stories share the same response count: 400 visits from 40 visitors is a form people keep returning to; 400 visits from 390 visitors is a form people bounce off.
Start rate. Responses started divided by visits. This is the number that tells you whether a disappointing response count is a traffic problem or a form problem.
"—" means unknown, not zero. Wherever NueForm couldn't measure something, it shows a dash rather than a zero. A form created before visit tracking existed shows "—" in the Visits column — it has an unknown number of visits, which is a completely different fact from a form nobody has opened. A start rate shows "—" when there were no visits in range, because a percentage with an empty denominator isn't 0%, it's undefined.
Blocked visits still count. If your form is closed, or hit its response limit, or your plan quota is full, the loads that got turned away are still recorded — and broken out by reason. A form that closed while traffic kept arriving is precisely the situation you want to see, and it's invisible if blocked loads go unrecorded.
Time zones
The Visits tab shows times in your browser's time zone, not the respondent's and not UTC. Someone reviewing form data from anywhere in the world sees the times where they are.
Workspace-level metrics in Analytics use UTC day boundaries instead, so a reported number doesn't change depending on who opens the panel.
Per-response visitor details
Open any response and its header carries the visitor's details: country and city, device, browser and OS, how they arrived (direct, referral, or embedded), and their language. This connects the anonymous traffic story to individual answers.
Some responses show "No visitor details for this response." That's expected for:
- Responses imported from a CSV — there was no visit.
- Responses submitted before visit tracking shipped.
- Phone responses, which show call metadata instead. Web-only fields (browser, referrer) are omitted with a note rather than guessed at.
Searching and filtering responses
The response list is paginated at 100 per page, and all filtering happens on the server — so a search covers every response on the form, not just the page you're looking at.
- Search answers — free-text across every answer on the form, including sub-answers inside composite questions.
- Status — completed or partial.
- Device, country, source — these dropdowns only offer values that actually occur on your form, so you can never pick a filter that returns nothing.
Two things worth knowing:
The Responses tile doesn't move when you filter. It describes your form. The count under the filter bar describes your query. Those are different questions and they get different numbers.
Export respects your filters. If the list shows 12 of 40,000, the CSV contains those 12. Clear the filters first if you want everything.
Older responses: search and the device/country filters read columns that are populated as responses come in. Responses submitted before this feature shipped need a one-time backfill before they become searchable — ask support if you have historical data you need to search.
What NueForm records
- Coarse location (country, region, city) derived at the edge
- Device type, browser, and operating system from the User-Agent header
- Referring host only — never the full referring URL
- UTM parameters, when present on the URL
- Screen and viewport size, device pixel ratio, time zone, connection type
- Which translation of your form was rendered
What NueForm does not record
- Your respondents' IP addresses are never stored. Location is derived at the edge and the address is discarded — it is never written to the database.
- No cross-form tracking. Visits are scoped to one form. NueForm does not build a profile of a person across the forms they visit.
- No respondent identity on ungated forms. A visit is linked to a signed-in user only when the form itself requires login. Someone logged into NueForm who opens your public form stays anonymous to you — the same rule responses already follow.
- Bots are flagged, never dropped. Self-identifying crawlers are marked rather than deleted, so your numbers stay auditable.
HIPAA and data residency
On HIPAA-enabled teams, precise location (city, latitude, longitude) is suppressed at the point of collection — not filtered later, never written. Visit records are also covered by your team's response retention policy.
On data-residency teams, the answer-search index is not built. Your answers stay in your own database by contract, and a searchable copy in the control-plane database would relocate exactly the data that guarantee protects. The device and location filters still work, since those aren't answer content.
Retention
Visit records are kept indefinitely by default. If your team sets a response retention period, visits are deleted on the same schedule. HIPAA teams get an additional purge pass.
Related
- Custom Visitor ID — assign your own respondent identity on embedded forms
- Require Respondent Login — the setting that governs whether visits and responses carry an identity
- Teams — team-level analytics and permissions