> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/activate/event-streaming/destinations/advertising/mntn.md).

# MNTN

MNTN measures the effect of connected TV (CTV) advertising. Chord offers two MNTN pixels. Both run in the shopper's browser, and neither has a server version.

## What each version does

* [**MNTN Tracking Pixel**](/activate/event-streaming/destinations/advertising/mntn/mntn-tracking-pixel.md) fires on every page view. MNTN uses it to build audiences and to attribute site visits to CTV ad exposure.
* [**MNTN Conversion Pixel**](/activate/event-streaming/destinations/advertising/mntn/mntn-conversion-pixel.md) fires on conversions such as purchases, sign-ups and leads. MNTN uses it to attribute conversions to CTV ads and to report return on ad spend.

## Why use both

The Tracking Pixel gives MNTN the full picture of who visits your site. The Conversion Pixel tells MNTN which of those visits turned into a conversion. Run both for audience building and conversion reporting.

Because both run in the browser, an ad blocker or a closed tab can stop either one. There is no server version to cover that gap.

## Set up

* [MNTN Tracking Pixel](/activate/event-streaming/destinations/advertising/mntn/mntn-tracking-pixel.md)
* [MNTN Conversion Pixel](/activate/event-streaming/destinations/advertising/mntn/mntn-conversion-pixel.md)


---

# 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.chord.co/activate/event-streaming/destinations/advertising/mntn.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.