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

# Onboarding

The Vibe channel integration with EdgeTag is an easy setup using Pixel ID to link your Vibe Pixel with EdgeTag. This connection allows your site to stream events into the pixel for comprehensive conversion tracking and campaign optimisation.&#x20;

Let's walk through the steps.

<figure><img src="/files/4a6wKIEvtBaX9DSasxdu" alt=""><figcaption></figcaption></figure>

### Add Channel

To add a Vibe channel, begin by entering the channel's name. We recommend choosing a name that clearly describes the purpose of the channel you are adding to EdgeTag. This will assist with debugging if any issues arise.&#x20;

Once you have entered the name, get the Pixel ID from Vibe.

### Get Pixel ID from Vibe

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

Log in to your Vibe account, navigate to [Web Pixel](https://www.vibe.co/dashboard/settings/tracking/web). <br>

* Under Profile Menu from the top right&#x20;
* Set up a pixel in there
* Copy the Pixel ID from the Vibe Dashboard to connect with EdgeTag.

After completing the above steps, just add the events that you want to trigger in the event mapping section on the EdgeTag Dashboard. As of now, we only support **PageView, Lead and Purchase** for the Vibe Channel.<br>


---

# 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/vibe/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.
