> 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/mntn-tracking-pixel.md).

# MNTN Tracking Pixel

**MNTN Tracking Pixel** is MNTN's site-wide audience building and attribution pixel for Connected TV (CTV) advertising. This destination fires a JavaScript pixel on every page view, enabling MNTN to build audiences and attribute site visits to CTV ad exposure. There is no server-side component.

For conversion tracking (purchases, sign-ups, leads), use this destination alongside the [MNTN Conversion Pixel](/activate/event-streaming/destinations/advertising/mntn/mntn-conversion-pixel.md).

## Getting started

This is a browser destination. Chord fires the pixel for you, so you don't install any script.

You need your MNTN advertiser ID, which is the value of the `o` parameter in MNTN's tracking pixel snippet, found in your MNTN account.

## Settings

* **Destination Name** (required): a name to tell this destination apart.
* **Advertiser ID** (required): your MNTN advertiser ID. It is the value of the `o` variable in your tracking pixel snippet.
* **Consent Requirements** (optional): the consent categories a visitor must accept before Chord sends data to this destination. See [Consent](/activate/event-streaming/consent.md).

## Connect

Add **MNTN Tracking Pixel** from the destination catalog, using the settings above. See [Connect a destination](/activate/event-streaming/connect-a-destination.md) for the full steps.

## Event mapping

The `page` and `screen` events fire the tracking pixel.

All other event types (track, identify, etc.) are silently skipped.

## Page / screen events

Fires a tracking pixel request to MNTN with referrer and page URL data.

**Pixel request:** `GET https://dx.mountain.com/spx?shaid=...&tdr=...&plh=...&cb=...`

| Chord source (priority order)                 | MNTN field | Notes                                                                                            |
| --------------------------------------------- | ---------- | ------------------------------------------------------------------------------------------------ |
| Configuration                                 | `shaid`    | Advertiser ID                                                                                    |
| `top.document.referrer` > `document.referrer` | `tdr`      | URL-encoded, max 2048 chars; falls back when `top` is not accessible (e.g. cross-origin iframes) |
| `parent.location.href`                        | `plh`      | URL-encoded, max 2048 chars; empty when not accessible                                           |
| Generated                                     | `cb`       | Random cache buster                                                                              |

## Initialization

Chord does not load an external SDK for this destination. Each event fires by creating a `<script>` tag with the pixel URL as its `src` attribute, inserted before the last script tag in the document.

## CSP requirements

If your site uses a Content Security Policy, allow the following domains:

| Directive     | Domain                    |
| ------------- | ------------------------- |
| `script-src`  | `https://dx.mountain.com` |
| `connect-src` | `https://dx.mountain.com` |


---

# 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/mntn-tracking-pixel.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.