> 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.md).

# Universal Ads

Universal Ads integration helps connect your Universal Ads with your website through browser pixel tracking. We manage browser event streaming for you, enabling seamless tracking of user interactions. The integration provides a straightforward setup with simple configuration options to get you started quickly.

### Details

Channel name: universalAds

NPM package: [@blotoutio/providers-universal-ads-sdk](https://www.npmjs.com/package/@blotoutio/providers-universal-ads-sdk)

### Event Flow

Our Universal Ads integration focuses exclusively on browser-side event tracking. When enabled, we automatically inject the Universal Ads browser pixel and handle event transmission from the user's browser to the Universal Ads Dashboard.


---

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