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

# Onboarding

Omnisend channels offer a straightforward setup process, utilizing an API key to connect your Omnisend account with EdgeTag. This connection allows your site to stream events into Omnisend for powerful product insights. Let’s walk through the steps.

### Video Guide

{% embed url="<https://www.loom.com/share/d08482395290413eaa6edc0dc8f537e3>" %}

### Add Channel

To add a channel, begin by entering the channel's name. We recommend choosing a name that clearly describes the channel you are adding. This will assist with debugging if any issues arise. Once you have entered the name, get an API key from **Omnisend**

<figure><img src="/files/kXXaTaCWFyThHKwjsRb6" alt=""><figcaption></figcaption></figure>

### **Generate an API Key in Omnisend**

Log in to your **Omnisend** account, navigate to the **Settings** page by clicking the bottom-left ⚙ Store Settings option, select API, and then click the **Create API** Key button.

<figure><img src="/files/Mub2M9zX9UkER629dN1I" alt=""><figcaption></figcaption></figure>

Give a name to the key and enable **Contacts** and **Events** only.

<figure><img src="/files/jhrfI3ubqb4qFLtRCFFD" alt=""><figcaption></figcaption></figure>

Click on Create API Key.

<figure><img src="/files/f9p70fnC7P6Lz3WSGQ1P" alt=""><figcaption></figcaption></figure>

Copy the api key and store it in a secure place since it cannot be viewed again.

<figure><img src="/files/SyFRt0KPpPJgUQO3wPY4" alt=""><figcaption></figcaption></figure>

Paste the copied **API Key** in the EdgeTag form

Click **Save & Deploy**&#x20;

Congratulations :tada:, the basic setup is now complete. \
Let's proceed to the next section to explore additional configuration options.


---

# 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://docs.edgetag.io/channels/omnisend/onboarding.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.