The Insights tab shows how a form is performing: how many people reached it, how many of them submitted, and where they came from. It is available on all plans, and every form has its own.
Insights are about the form itself rather than about any one submission. For the submissions themselves, use the Submissions tab.
A form only starts collecting insights once it is published. A Draft form records nothing, because nobody can reach it yet.

Every number and chart on the tab reflects the date range selected in the dropdown at the top right. It defaults to "All time".
The options are All time, Last 7 days, Last 30 days, Last 90 days, and Custom range. Custom range lets you set your own start and end dates. Changing the range updates the whole tab at once, including the breakdown panels at the bottom.

A row of cards sits across the top of the tab.
The gap between Visits and Submissions is usually the most useful thing on this tab. A form with few visits and a high conversion rate has a sharing problem. A form with many visits and a low conversion rate has a form problem. Forms started sits between the two and tells you which: people who started and did not finish were lost inside the form, and people who never started were lost before it.
Two bar charts sit below the cards. The left chart plots visits over time and the right plots submissions, each labeled with its total for the selected date range.
Reading them side by side is what tells you whether a change you made had an effect. A spike in visits without a matching spike in submissions is the pattern worth looking into.
The Sources panel lists the sites people arrived from, with a count beside each one, showing the top eight from most to fewest.
Only visits that arrived from a link on another website appear here. A visit with no referring site is left out of this panel rather than grouped as direct traffic, and that covers QR code scans, most email clients, and anyone who typed or pasted the link. So the counts in Sources will add up to less than Visits, often much less, and that is expected rather than a gap in the data.
An embedded form reports the page it is embedded on, so the site hosting your form appears as the source.
Three panels at the bottom break your visits down by the equipment people used.
This matters most when someone reports a problem uploading. Knowing that a meaningful share of your uploaders are on mobile changes how you build and test a form.
