> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/ios/setup-luciq-for-ios/setup-in-app-surveys.md).

# Setup In-App Surveys

The in app Surveys setup section for the Luciq iOS SDK. Show and target surveys, hook into survey events, and disable surveys entirely.

## Test Surveys Without Frequency Limits

By default, Luciq enforces survey frequency settings. In iOS SDK 19.12.0 and later, you can bypass those settings while testing in the Simulator or on a physical device signed with a development provisioning profile.

{% hint style="warning" %}
`disableFrequencyEvaluationInDebugBuilds` is experimental and may change or be removed in a future release.
{% endhint %}

{% tabs %}
{% tab title="Swift" %}

```swift
Surveys.disableFrequencyEvaluationInDebugBuilds()
```

{% endtab %}

{% tab title="Objective-C" %}

```objectivec
[LCQSurveys disableFrequencyEvaluationInDebugBuilds];
```

{% endtab %}
{% endtabs %}

The call takes effect immediately for the current app process and is not persisted. To restore frequency checks, omit it on the next launch.

Survey targeting still applies, paused surveys stay paused, and announcements keep their frequency settings. The API is ignored in App Store, TestFlight, ad hoc, and enterprise builds. A configuration named **Debug** or a `DEBUG` macro does not determine eligibility.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.luciq.ai/ios/setup-luciq-for-ios/setup-in-app-surveys.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.