Form analytics: reading traffic without guessing at drop-off
Read Thunder Forms views, visitors, device breakdowns, and referrers. Learn what these reports can tell you, and how to review completion separately.
After sharing an event signup link, open its analytics from the forms dashboard. The chart shows daily views and visitors, with browser, operating-system, and device breakdowns describing the traffic and a referrer report to help identify where visits came from.
The reports describe reach. Open the response list for answers. Thunder Forms does not currently record a start-to-submit funnel or show the page where someone stopped answering.
Read views alongside your distribution
Suppose you post a link in a newsletter on Monday and share it on a community site on Thursday. A rise in Thursday views tells you the form received traffic around that second share. Check the referrers before attributing the change to a particular source.
A view does not equal an answer. Repeat visits can contribute views, so take care when interpreting visitor counts as well, since they do not provide a verified list of the people who opened the form. Someone may open the link to read the event details and have no intention of registering.
Use device data to choose a test
If the device breakdown shows mobile traffic, try the public form on your phone. Use the same upload and date questions you expect respondents to complete. Check that labels fit and that a required answer can be corrected without losing the answers on an earlier page.
The chart cannot identify a broken control. It suggests where to test. Ask a colleague to complete the form and explain any question they find confusing, then compare their experience with the answers you receive.
Keep completion estimates clearly labeled
Imagine a seven-day period with 100 views and 20 submissions. Dividing the two gives a 20 percent response-to-view ratio. It does not establish that 80 people started and abandoned the form, because the report does not measure starts and some visits may be repeats.
If you track that ratio outside the dashboard, use the same date range for both counts, note its limitations, and keep test submissions separate when reviewing the results. It is an operational estimate you calculate yourself.
Review one change at a time
Record the date when you change a question or publish the link somewhere new. For example, "October 16: made phone optional" gives you context when inspecting later answers. A traffic change at the same time makes it harder to attribute a difference in submissions to the edit.
Compare similar periods. Small samples need caution. If a required field produces repeated requests for help, investigate the wording and validation rule directly. A promise of a higher completion rate would need evidence from your own form.
Keep a small review log
For each review, record the form name, date range, views, visitors, submitted responses, where the link was shared, and any change made during that period. Add a note when a number includes your own test submissions. A log gives later readers enough context to interpret a chart without guessing what changed.
If a partner newsletter goes out on the 12th, mark that date and check referrers and traffic in the following days. If responses stay low, check whether the link opened correctly, whether the intended audience received it, and whether a test submission appears in the response list. Those checks help separate distribution problems from form problems without claiming an unmeasured abandonment funnel.
What to do when the counts disagree
Use the response list as the source for submitted answers and analytics as a source for traffic patterns. Confirm that both views cover the same date range and form. A copied form has a separate response history, and an old link can send people to the wrong copy. Test the exact link in the message or page where it is published before changing your questions.
| Report | Useful for | It does not establish |
|---|---|---|
| Views | Checking whether the form page received traffic | How many people began answering |
| Visitors | Reviewing traffic over time | A verified list of unique people |
| Referrers and device details | Choosing which link or screen to test | Why someone did or did not submit |
| Response list | Reviewing completed submissions | Unsubmitted or abandoned answers |
Frequently asked questions
Short answers to the questions every reader asks next.
Open the forms dashboard, review traffic for one form, and compare it with the submitted answers from the same period. Note any question that needs a direct usability check.