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

# Onboarding

### Video Guide

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

### Add Channel

To add a channel, begin by entering the channel's name. We recommend choosing a name that clearly describes the dataset you are adding. This will assist with debugging if any issues arise.

<figure><img src="https://1474399258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZJWZKbUk0hRISkCIj2p4%2Fuploads%2FjcQfTf3nMilJVxHavCZ1%2FScreenshot%202026-01-14%20at%205.29.52%E2%80%AFPM.png?alt=media&amp;token=d2de2641-79fb-4ca6-894e-f38584ff89aa" alt=""><figcaption></figcaption></figure>

### Mandatory Fields

The following fields are mandatory to send events to `Meta`

* Pixel Access Token
* Dataset ID
* Ad Account ID

<figure><img src="https://1474399258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZJWZKbUk0hRISkCIj2p4%2Fuploads%2FTXRxq9rgBfRdq2zAZAdv%2FScreenshot%202026-01-14%20at%204.51.10%E2%80%AFPM.png?alt=media&amp;token=0218d7c4-b8f9-4fd9-bbc0-b8daea6294c8" alt=""><figcaption></figcaption></figure>

### Pixel Access Token

To generate a Pixel Access Token,

* Navigate to your [Events Manager](https://business.facebook.com/events_manager2/list/)
* Select the desired `Dataset ID`
* Open the `Settings` tab
* Scroll down to the `Conversions API` section
* Click the `Generate access token` button

<figure><img src="https://1474399258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZJWZKbUk0hRISkCIj2p4%2Fuploads%2FUUAt14Wn82W9F2KHOIK0%2Fimage.png?alt=media&amp;token=51cac3d6-4184-4cc8-a141-392890148ff6" alt="Generate Access Token"><figcaption><p>Generate Pixel Access Token</p></figcaption></figure>

* Copy the generated `Access Token`
* Ensure that you keep this token secure, as it is required to authenticate events sent to Meta.

### Dataset ID & Ad Account ID

To get the Dataset ID & Ad Account ID,

* Navigate to your [Events Manager](https://business.facebook.com/events_manager2/list/)
* Select the desired `Dataset ID`
* Open the `Settings` tab
* Copy the `Dataset ID` and `Ad Account ID`

<figure><img src="https://1474399258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZJWZKbUk0hRISkCIj2p4%2Fuploads%2FcRPbt5tmiZ3kSdb0iF43%2Fimage%20(5).png?alt=media&amp;token=c3b9bca8-e4ff-4e9f-9150-ec21cb29f5e7" alt=""><figcaption><p>Dataset ID &#x26; Ad Account ID</p></figcaption></figure>

Add `Pixel Access Token`, `Dataset ID` & `Ad Account ID` in the form.

<figure><img src="https://1474399258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZJWZKbUk0hRISkCIj2p4%2Fuploads%2FOrnDMo5unzSWcdSyxwgi%2FScreenshot%202026-01-14%20at%205.34.14%E2%80%AFPM.png?alt=media&amp;token=c38fbb28-9e6d-4f7a-8d58-177c375ea0e3" alt=""><figcaption><p>Form with mandatory fields</p></figcaption></figure>

Click **Save & Deploy.**

Congratulations :tada:, the basic setup is now complete.&#x20;

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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.edgetag.io/channels/meta/onboarding.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.
