This is a guide on how to implement the Image version (img/gif - non-script) of the MNTN Tracking Pixel (TRPX). It does not use scripts and only an image tag which responds with Content-Type: img/gif in the browser. It is strongly recommended all calls be made over SSL (HTTPS) as described below.

We do not recommend using an image pixel as it is extremely manual to install and maintain. The advertiser is fully responsible for setting up and maintaining all aspects of the image pixel. Instead, we recommend installing the tracking pixel with Shopify, Google Tag Manager, or JavaScript. You can find our complete Pixel Installation Guide collection here.

If an image pixel is required, please contact your MNTN team member to receive the actual pixel code, as it is not included in this article. This article serves as documentation for image pixel implementation only.

The minimum you can do to make the call to the MNTN Pixel Service is to add the following HTML <img tag to the pages you want the MNTN Image Pixel to be fired on:

<SH-ADVERTISER-ID> - Customer Identification (Advertiser ID), usually an integer number, like 12345

​<CACHE-BUSTER> - Cache Buster is a necessary parameter to instruct the browser not to cache the URLs for the call, so it will fire actual calls to the MNTN Pixel Service every time. It could be any random value, epoch timestamp, or whatever else might be used as a unique value. A recommended way to generate it is a random number; here is a JavaScript code snippet you can use:

<CURRENT-PAGE-URL> in case you wrap the <img tag into an IFrame. In that scenario, the Pixel will get the proper page URL as a referrer, which is needed for various MNTN Pixel features, like identifying the different types of pages, filtering pages, firing rules, etc.

The MNTN Tracking Pixel contains an additional variable that can be utilized to pass along any additional information to our pixel. The information passed to the additional variable in the MNTN Tracking Pixel can be used in the MNTN UI audience engine for segmenting and retargeting purposes.

The additional variable in the MNTN Tracking Pixel accepts a comma-separated list of key=value pairs, i.e. isExistingUser=true or isExistingUser=false.

In this example, the objective is to identify existing vs non-existing users; the key is isExistingUser and the value is either true or false.

The key=value pair could be a comma-separated list, and when specified in the URL, it must be preceded by &shadditional=, like in the example below:

&shadditional=isExistingUser=true

If multiple key=value pairs will be passed to the MNTN Tracking Pixel, each subsequent key=value pair will need to be comma-separated, like the example below:

&shadditional=isExistingUser=true,isHighValueUser=true,membershipTier=loyalty

The minimum you can do to make the call to the MNTN Pixel Service is to add the following HTML <img tag to the pages you want the MNTN Image Pixel to be fired on:

<MNTN-ADVERTISER-ID> - Customer Identification (Advertiser ID), usually an integer number, like 12345

​<CACHE-BUSTER> - Cache Buster is a necessary parameter to instruct the browser not to cache the URLs for the call, so it will fire actual calls to the MNTN Pixel Service every time. It could be any random value, epoch timestamp, or whatever else might be used as a unique value. A recommended way to generate it is a random number; here is a JavaScript code snippet you can use:

<CURRENT-PAGE-URL> in case you wrap the <img tag into an IFrame. In that scenario, the Pixel will get the proper page URL as a referrer, which is needed for various MNTN Pixel features, like identifying the different types of pages, filtering pages, firing rules, etc.

<COMMA-DELIMITED-LIST-OF-KEY=VALUE-PAIRS> The additional variable specified in the above description

When you need MNTN to integrate with GA, you must add additional parameters to the call. Here is the Image Pixel Tag:

All parameters (required and optional) as described in the “Minimum Required Parameters” section, plus the additional GA values needed to be passed:

<MNTN-ADVERTISER-ID> - Customer Identification (Advertiser ID), usually an integer number, like 12345

​<CACHE-BUSTER> - Cache Buster is a necessary parameter to instruct the browser not to cache the URLs for the call, so it will fire actual calls to the MNTN Pixel Service every time. It could be any random value, epoch timestamp, or whatever else might be used as a unique value. A recommended way to generate it is a random number;

​<GA-TRACKING-ID> - GA Tracking ID is the GA website identification;

​<GA-CLIENT-ID> - GA Client ID is the GA user identification;

​<GA-PAGE-TITLE> - GA Page Title is the current page's title, usually what is showing in the browser’s tab for the current page, like the HTML title.

<CURRENT-PAGE-URL> - in case you wrap the <img tag into an IFrame. In that scenario, the Pixel will get the proper page URL as a referrer, which is needed for various MNTN Pixel features, like identifying the different types of pages, filtering pages, firing rules, etc.

In order for those extra values to be acquired and passed to the MNTN Image Pixel, there might be some extra effort for the Engineers.

Here is a JavaScript code snippet on how to get those values and then construct the URL for the call to the MNTN Pixel Service:

Here is a JavaScript code snippet on how to construct the URL for the call to the MNTN Pixel Service, including also the bare minimum for the parameters required:

Here is a JavaScript code snippet on how to inject the <img tag to your page using the above-constructed URL:

The entire implementation of the call, including acquiring the GA values, will look like this:

The minimum you can do to make the call to the MNTN Pixel Service is to add the following HTML <img tag to the pages you want the MNTN Image Pixel to be fired on:

<MNTN-ADVERTISER-ID> - Customer Identification (Advertiser ID), usually an integer number, like 12345

​<ORDER-OR-ACQUISITION-ID> - ID of the purchase order or other acquisition identifier, in alpha-numeric formats, like A-1000123 <ORDER-OR-ACQUISITION-AMOUNT> - The amount of the purchase order, or other value referring to an acquisition, in numeric formats, like order amount 1234.56, or 1234

​<CACHE-BUSTER> - Cache Buster is a necessary parameter to instruct the browser not to cache the URLs for the call, so it will fire actual calls to the MNTN Pixel Service every time. It could be any random value, epoch timestamp, or whatever else might be used as a unique value. A recommended way to generate it is a random number; here is a JavaScript code snippet you can use:

<CURRENT-PAGE-URL> in case you wrap the <img tag into an IFrame. In that scenario, the Pixel will get the proper page URL as a referrer, which is needed for various MNTN Pixel features, like identifying the different types of pages, filtering pages, firing rules, etc.