> For the complete documentation index, see [llms.txt](https://guides.apxor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.apxor.com/product-guides/create-a-survey/latest/survey-stop-conditions.md).

# Survey Stop Conditions

You can configure conditions to stop showing a survey to the end user based on the scenarios below. Once you have finalized the design and navigated to the **Target** section on the dashboard, you will find the **Stop Conditions** section at the bottom.

<div align="left"><figure><img src="/files/gXMuO8w086rvC72MksMy" alt="Survey Stop Conditions"><figcaption></figcaption></figure></div>

#### 1. **User Property**

Stop showing the survey once a specified user property is updated.

**To configure:**

* Check the box for **User Property**
* Select the desired user property from the dropdown
* Choose the value at which the survey should stop being shown

**Examples:**

* `subscription_type` updates to `paid`
* `app_version` updates to `2.0.03`

#### 2. **Goal Event**

Stop showing the survey once a specific goal event from the campaign is triggered.

**To configure:**

* Check the box for **Goal Event**
* Select one or more goal events associated with the campaign

**Examples:**

* `purchase_complete` is triggered
* `level_up` is triggered

You can also define combinations of events using **AND** or **OR** logic.

**Examples:**

* `Event A AND Event B`
* `Event A OR Event B`

#### 3. **Survey Completed**

Stop showing the survey once the user has completed it.

**To configure:**

* Check the box for **Survey Completed**

Once the user completes the survey (e.g., submits the final response), they will no longer be shown the same survey again.


---

# 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://guides.apxor.com/product-guides/create-a-survey/latest/survey-stop-conditions.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.
