> 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/publish.md).

# Publish

If you're happy with the look of your survey and want to post it to your users, you should publish your survey. Click on the "Publish" CTA on the top right corner to publish the survey.

To Publish a survey from listings page, click Edit CTA under the Actions section on the [campaigns listing page](/product-guides/create-a-survey/legacy/survey-listings-page.md). You will be redirected to the survey "Review" Screen, where you have an option to "Publish" the survey in the top-right-hand corner. Click on Publish on the confirmation message, and your Survey will be live at the scheduled time.

<figure><img src="/files/GRwsdjj05CDN3cyH6rWw" 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://guides.apxor.com/product-guides/create-a-survey/latest/publish.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.