> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/documentation/readme.md).

# Documentation overview

Browse the platform by topic or find step-by-step guides for common tasks.

### Find what you need

The UbiQuity documentation is organised around the key areas of the platform, so you can get to the right information quickly - whether you're setting something up for the first time, learning how a feature works, or completing a specific task.

Use the sidebar to navigate by topic, or search if you already know what you're looking for.

***

### How the docs are structured

* **Basics** - Core platform concepts including Content & Preview, Media Manager, Filters, Channels, and Templates.
* **How To** - Step-by-step guides for common tasks such as creating emails, forms, surveys, and events, importing data, sending emails, and activating campaigns.
* **Channels** - Guidance specific to each channel UbiQuity supports: Email, TXT, and Push.
* **Data Capture** - Everything related to capturing data through Forms, Surveys, Events, and Layouts, plus guidance on finding your form and survey data.
* **Data & Integrations** - Covers how to bring data into UbiQuity, including Imports, Connectors, and the API, with guidance on choosing the right integration method.
* **Audience Management** - Managing your database, filtering audiences, handling Opt Outs, and working with GNA (Gone No Address).
* **Keep Learning** - Additional resources including Training and the UbiQuity Blog.

***

### Not sure where to start?

If you're new to UbiQuity, head to the [**Getting Started**](https://docs.ubiquity.co.nz/) section.


---

# 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.ubiquity.co.nz/documentation/readme.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.
