> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/intercept-studies/manage-an-intercept-study/view-intercept-study-performance.md).
# View intercept study performance
Once you’ve launched your intercept study, you can get an idea of how it’s performing from the **Responses** tab.
This data can help you assess how often participants are seeing the opportunity, where they might be dropping off, and more. This can help you adjust your recruitment criteria if you need it to be more specific or if you feel it’s not specific enough.
To view more data, click **See more**. A modal is displayed with the additional metrics described in the sections below.
## Intercept
The **Intercept** section of the modal gives you an idea of how often your study is being presented to participants and how those participants are reacting to the opportunity.
**Here’s a breakdown of each metric in this section:**
| Metric | Description |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Views** | Number of times the opportunity was displayed to eligible participants. These are unique views, so each participant is only counted once—even if they see the opportunity again after snoozing it initially. |
| **Dismissals** | Number of participants who permanently dismissed the opportunity, opting not to see it again. |
| **Snoozes** | Number of participants who temporarily dismissed (snoozed) the opportunity, opting to be reminded later if the opportunity is still available.
If a participant snoozes the study but later joins, this count may drop as that participant moves to Started or Completed submissions. If they eventually decline the study, they are then recorded under Dismissals.
|
| **Started** | Number of participants who were accepted into the study and answered at least one question. If your study has a screener question, this number ***does not*** count participants who were knocked out. |
| **Completed submissions** | Number of complete entries submitted by participants. |
## Screener
If your study has a screener question, you can see a breakdown of how many applicants are being disqualified in the **Screener** section of the modal:
Here, you’ll find the **Total knocked out** count, which shows how many people have applied to your study but have been disqualified by your screener question. Click the screener question to see a breakdown by answer choices:
In the above example, you can see that 87 of the study's total applicants have been disqualified—45 choosing **News** and 42 selecting **Other**, both of which are set as knockout choices.
## What do I do with this data?
The metrics in this modal are meant to provide a look into how your study is filling. What you do with that information is up to you, but we can offer some guidance:
High views, high dismissals
If you notice a lot of people are seeing your intercept (a high **Views** count) and declining the opportunity (high **Dismissals** count), participants might not think the opportunity is worth it. **Consider increasing your incentive or adjusting your prompt to clarify the time commitment.**
High views, low completion
If a lot of people are seeing your intercept (a high **View** count) but the number of entries you’ve received is low, look at the following:
* Are **Dismissals** also high? If so, refer to High views, high dismissals.
* Are **Dismissals** low? If so, assess your knockout question. Are a lot of people being knocked out by a specific response choice? Is that a response choice you can be more flexible on? If so, this can help boost your response rate.
High starts, low completion
If there’s a drop-off between the number of people who **Started** your study and the **Completed submissions**, there may be an issue with the study itself. Reassess your questions and study setup to see if there’s a specific question or task where you might be losing participants. They’re getting in, but for some reason they aren’t sticking around—and that’s often to do with study design.
High views, high snooze
If your views are high *and* your snoozes are high, there typically isn’t much to worry about. If a participant happens upon your intercept during working hours, for example, they’re more likely to snooze it. They’ll see the study again later (if the study is still open and they hit your intercept URL again), and will have another chance to join.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.dscout.com/intercept-studies/manage-an-intercept-study/view-intercept-study-performance.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.