> For the complete documentation index, see [llms.txt](https://support.quizkitapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.quizkitapp.com/building-a-quiz/integrations/email-and-sms/omnisend.md).

# Omnisend

Learn how to connect the Omnisend integration, and set it up in your quiz.

Quiz Kit allows you to add new customers to your Omnisend account.

{% hint style="info" %}
**Note:**&#x20;

If you’re on a legacy Quiz Kit plan, then this feature is available for the **Basic** plan or higher.
{% endhint %}

## Connecting Quiz Kit to Omnisend

**Steps:**

1. From the Quiz Kit dashboard, click **Integrations**.
2. On the **Email marketing** tab, go to **Omnisend** and click **Connect**.
3. Insert your Omnisend **Private** **API key**.
4. Click **Save**.&#x20;

In order for the email and contact information to be passed to Omnisend, make sure you're [collecting customer data](/building-a-quiz/collecting-customer-data.md) on your quiz.&#x20;

If you're using a form field question, use the **Marketing property name** field to pass the correct information, such as entering `firstName` if you're collecting the customer's first name.


---

# 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://support.quizkitapp.com/building-a-quiz/integrations/email-and-sms/omnisend.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.
