# MNTN Reference

This is a reference document for the MNTN destination. For information on how to set up this integration, see the [mntn-quick-start-guide](https://documentation.freshpaint.io/integrations/destinations/demand-side-platforms-dsps/mntn/mntn-quick-start-guide "mention").

## Destination Info

* Supports [Track](https://documentation.freshpaint.io/reference/developer/freshpaint-sdk-reference#track) calls
* Supports [HIPAA mode](https://documentation.freshpaint.io/readme/hipaa-mode)
* Supports forwarding from the [Google Tag Manager Integration](https://documentation.freshpaint.io/integrations/google-tag-manager-integration)
* Supports [Freshpaint Impression Pixel](https://documentation.freshpaint.io/integrations/impression-pixel)
* Refer to this destination as **MNTN** in the [Integrations object](https://documentation.freshpaint.io/reference/developer/freshpaint-sdk-reference#using-the-integrations-object)
  * If you've configured multiple Advertiser IDs, you can choose a specific one by suffixing the Advertiser ID, such as: **MNTN::123456.** You can retrieve this value from MNTN configuration page for the Advertiser ID of interest.

{% hint style="info" %}
When no suffix is specified, all configured Advertiser IDs are selected for inclusion / exclusion.
{% endhint %}

* Connection Modes:

<table><thead><tr><th width="200.33333333333331" align="right"> </th><th data-type="checkbox">Client-side</th><th data-type="checkbox">Server-side</th></tr></thead><tbody><tr><td align="right">Web</td><td>false</td><td>true</td></tr><tr><td align="right">Mobile</td><td>false</td><td>true</td></tr><tr><td align="right">Server</td><td>false</td><td>true</td></tr></tbody></table>

## View Through Tracking

Freshpaint supports view through tracking by capturing the `mntn_impid` parameter passed in by MNTN using the Freshpaint Impression Pixel. Assuming you have followed the [mntn-quick-start-guide](https://documentation.freshpaint.io/integrations/destinations/demand-side-platforms-dsps/mntn/mntn-quick-start-guide "mention") to set up your MNTN destination, you can verify that view through tracking is working by looking for an event in event verification that contains the `$mntn_impid` field.

You can also look for a transformation that shows that the event data was enriched by the Freshpaint Impression Pixel.

<figure><img src="https://1666823438-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MA7aDqsXMFbUsWVqonF%2Fuploads%2F6DTd2D9p6DhTSjDbs5X6%2FScreenshot%202025-06-26%20at%204.38.07%E2%80%AFPM.png?alt=media&#x26;token=52b9d65f-b773-43db-ac1a-06bdfa5a45bb" alt=""><figcaption><p>Transformation applying the Impression Pixel captured impression to an event</p></figcaption></figure>

## Relevant Properties

These are the properties that are sent to MNTN. If you've followed the [mntn-quick-start-guide](https://documentation.freshpaint.io/integrations/destinations/demand-side-platforms-dsps/mntn/mntn-quick-start-guide "mention") correctly, no further action is necessary. This section is just informational.

<table data-header-hidden data-full-width="true"><thead><tr><th width="207"></th><th width="214"></th><th width="137"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Freshpaint property</strong></td><td><strong>MNTN</strong><br><strong>parameter</strong></td><td><strong>Type</strong></td><td><strong>Required?</strong></td><td><strong>Description</strong></td></tr><tr><td><code>order_id</code></td><td><code>order_id</code></td><td>string</td><td>Recommended</td><td>Unique order identifier for connecting conversion activities to advertising campaigns.<br><br>If not provided or not allowlisted, this property will default to a unique masked ID for the conversion event. </td></tr><tr><td><code>$mntn_impid</code></td><td><code>Impression</code></td><td>string</td><td>Recommended</td><td>This is the MNTN View Impression ID. This property is captured by the Freshpaint Impression Pixel, and is passed to Freshpaint via the tracking pixel configured on the creative. The impression ID is required for attribution.</td></tr><tr><td><code>order_amount</code></td><td><code>order_amount</code></td><td>number</td><td>Recommended</td><td>The amount associated with the conversion.</td></tr><tr><td><code>order_currency</code></td><td><code>order_currency</code></td><td>string</td><td>Recommended</td><td>Currency code associated with the conversion. <a href="https://www.iso.org/iso-4217-currency-codes.html">ISO 4217</a> format.</td></tr><tr><td><code>product_identifier_list</code></td><td><code>product_identifier_list</code></td><td>array of strings</td><td>Recommended</td><td>List of product SKUs or identifiers associated with the conversion.</td></tr><tr><td><code>account_id</code></td><td><code>account_id</code></td><td>string</td><td>Recommended</td><td>Account ID of the connected MNTN account. </td></tr><tr><td><code>event_id</code></td><td><code>event_id</code></td><td>string</td><td>Optional</td><td>Common identifier to connect Verified Visits to a conversion for a specific user journey.</td></tr><tr><td><code>mntn_event_type</code></td><td></td><td>string</td><td>Optional</td><td>Determines if an event is sent as a Verified Visit or as a conversion. <br><br>Valid values: <code>visit</code>, <code>conversion</code></td></tr></tbody></table>