> For the complete documentation index, see [llms.txt](https://surveysparrow.gitbook.io/spotchecks/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://surveysparrow.gitbook.io/spotchecks/configure-essentials.md).

# Configure Essentials

There are 4 types of conditions on which Spotchecks can be configured.

1. Spots
2. Checks
3. Visitors
4. Recurrence

## Spots

Spots allow you to set conditions on which page the surveys should be displayed. For instance, if you require the app to display only on certain pages or if you want to exclude certain pages, you can pass the specific URL or the page (for web targets) or screen name (for mobile targets) to enforce this page condition.

<figure><img src="/files/6vQjxpw82yp4yhDgqw74" alt=""><figcaption></figcaption></figure>

### Checks

Checks focus on triggering the surveys based on events within the application. For instance, if a survey needs to be popped when the user clicks on a button, you can simply pass the class name of the element. So, when the elements get clicked, the survey will be displayed on the application. Similarly, there are various events that when triggered, lead to the display of the survey. There are custom events as well.

<figure><img src="/files/yl7iup2Ejz7k42gZEwRI" alt=""><figcaption></figcaption></figure>

### Visitors

It is used to set conditions based on visitors' metadata such as location, surveys, date, etc.&#x20;

<figure><img src="/files/IJ68FfSA6DaEzoJq4JR5" alt=""><figcaption></figcaption></figure>

### Recurrence

Recurrence defines the number of days, the survey is not allowed to be shown to the visitors of the app. This condition can also be set for various events happening in the survey. For instance, if you want the user to not see the survey for another 40 days when they respond to that survey, you can enter 40 days

<figure><img src="/files/qQ8nPsr9RNpuXGR4Cv80" alt=""><figcaption></figcaption></figure>


---

# 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://surveysparrow.gitbook.io/spotchecks/configure-essentials.md?ask=<question>&goal=<endgoal>
```

`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.