> For the complete documentation index, see [llms.txt](https://docs.pulseinsights.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pulseinsights.com/implementing-pulse-insights-dev/implementing-on-web-and-mobile-web/supporting-inline-surveys.md).

# Supporting Inline surveys

An inline survey is a survey that looks and acts like part of the page. Users get frustrated with various popups as they browse, so inline surveys are a great way to capture feedback contextually in a way that doesn't feel like an interruption or afterthought.

Pulse Insights needs a Target CSS Selector (configured in Console) to insert inline surveys. 

The positioning of inline surveys is dictated by their **Target** (CSS selector), **Location** (Above/Inside/Below) and, if located inside the target, the **Order** with Target (First/Last). 

See more details in the [Formatting section](broken://pages/qjLxxvYTvRqypS9lANyU) of Console Configuration.

## Inline Survey FAQs

### Do I need to create a specific div to host inline surveys?

{% code title="Example:" %}

```html
<div id="pulse-survey"></div>
```

{% endcode %}

In most cases, **you** **don't** need to create an empty div. As long as there is a consistent CSS selector, that will suffice.&#x20;

There are two cases where it is helpful to have a dedicated div to host the surveys:

* the survey is targeted to show across multiple pages and not all pages contain the same CSS selector&#x20;
* the structure of the page changes (e.g. different page content for customers vs. prospects)


---

# 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.pulseinsights.com/implementing-pulse-insights-dev/implementing-on-web-and-mobile-web/supporting-inline-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.