You can look at the performance of individual questions in your typeform in this section. Note that this data is only stored for 90 days (a 90 day rolling period).

Drop-off shows you the performance of each of the fields or questions in your typeform. You can see if any of your questions are a huge turn-off for your audience, and which ones people like answering more.

This is currently a BETA feature. You can filter drop-off data by date and views in Question by question.  Any typeform created before July 23, 2020 will not include full data for this feature. We do not currently support drop-off data for typeforms embedded with our Conversations feature.

Views shows you how many times each question has been viewed by respondents. In the image below, you can see fewer people viewed the Thank You Screen of this typeform than the questions before it. 

Drop-off shows you the percentage and total number of people who looked at a question and then closed (not completed) your typeform. The percentage is calculated by dividing the total number of people who stopped at that question, by the total number of views for that question. So, the lower this number is, the better your questions are performing.

Use the arrows next to Drop-off or Views to order the list by best or worst performing questions.

The question where most respondents drop off is highlighted in red, so you know where you might be able to make the most improvements. Hover your mouse over it, and an Edit button will appear so you can try to improve that question. 

You can filter your results by date by clicking the calendar icon under Question by question:

You can also use the date filter as a workaround to reset drop-offs. For example, you can set the date filter to only include the dates after the day you submitted test responses. This has the same effect as resetting the numbers in the Insights section.

You may notice discrepancies in drop-off data. The current implementation of drop-off tracks when someone closes a browser tab or a browser completely, for example. However, there are some limitations. We cannot currently track drop-off:

• if someone is responding from the latest version of safari, as the event may not properly be sent (a bug with safari version)
• if someone is responding from a mobile device and they exit their browser by “swiping up” (e.g. closing out the application completely) then the event won’t be sent
• if someone is filling out the typeform and just leaves the tab open forever, then the event won’t be sent
• if the form is not linear (e.g. when the form uses logic jumps, or if you add or remove questions or change the position of a question) then the views for one question cannot be calculated from the views minus drop-offs of the "previous" question
• if question views and drop-offs aren't interpreted for each question in isolation (e.g. you can't use the question views and drop-off rates to calculate and compare with the form completion rate)