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

# Onboarding

The Universal Ads team provides a conversion pixel snippet for each tracked page, where `tag_id` and `segment_key` change based on the URL of your site.

```html
<img
src="https://cnv.event.prod.bidr.io/log/cnv?tag_id=1111&buzz_key=universalads&value=&segment_key=ua-1331&account_id=3478901"
width="0"
height="0"
style="position:absolute;visibility:hidden;"
border="0" />
```

Onboarding requires filling out the provider form, and all the information can be found at the URL in the snippet above.

**Account Id** (`account_id`) - This is your Universal Ads account ID

**Buzz Key** (`buzz_key`) - This is the buzz key provided by Universal Ads

**Source Mapping** (`tag_id`, `segment_key`)- This is used to map a Tag ID and Segment Key pair to a specific URL of your site

**Example Source Mapping:**

<table><thead><tr><th width="137.265625">Segment Key</th><th width="97.54296875">Tag ID</th><th width="277.91796875">URL</th><th>Description</th></tr></thead><tbody><tr><td>ua-1331</td><td>1111</td><td>https://edgetag.io</td><td>Landing page</td></tr><tr><td>ua-1332</td><td>2222</td><td>https://edgetag.io/thank-you</td><td>Thank you page</td></tr><tr><td>ua-1333</td><td>3333</td><td>https://edgetag.io/products/*</td><td>Product pages</td></tr></tbody></table>

{% hint style="info" %}
URLs are matched on origin + path only — query strings, hashes and trailing slashes are ignored. Matching is case-insensitive. A \* wildcard matches exactly one path segment, so <https://edgetag.io/products/\\>\* matches <https://edgetag.io/products/snowboard> but not <https://edgetag.io/products/snowboard/reviews>.
{% endhint %}

### Add Channel <a href="#add-channel" id="add-channel"></a>

To add a channel, enter 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.&#x20;

<figure><img src="https://1474399258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZJWZKbUk0hRISkCIj2p4%2Fuploads%2FwaoUEs08u0Bm2a2ou57Z%2Fimage.png?alt=media&amp;token=1250668e-6672-492f-ad21-86039131ee84" alt=""><figcaption></figcaption></figure>

At least one mapping with a `Segment Key`, `Tag ID` and `URL` is required. Each URL can only be added once. If a page URL does not match any mapping, no pixel is fired for that page.

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

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 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/universal-ads/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.