Pixel Installation Guide: Site-Direct

Learn how to install the MNTN pixels directly into your site.

Jazmine Jackson avatar
Written by Jazmine Jackson
Updated this week

Whether you're new to the concept or simply seeking a clear walkthrough, this site-direct guide is designed to make pixel installation accessible and achievable for anyone, regardless of technical expertise.

Accessing Your MNTN Pixels

Your pixel codes can be found within your account's dropdown menu, more specifically under Pixel.

Emailing Pixels to Your Developer

If you're working with a dev team, email the tracking and conversion pixels to those team members for a seamless installation. To email the codes out:

1️⃣ Select Email Your Developer from the bottom right-hand corner of the Pixel Setup modal.

2️⃣ Enter the email address(es) of the developer responsible for implementing your pixels.

3️⃣ Once complete, click Send to send your email message to the team with the pixels attached for install.

Implementing Your MNTN Tracking Pixel

Pixel Setup Requirements

✅ Pixel must be placed site-wide, on every page.

❌ Pixel cannot be placed within any iFrames and/or Floodlights.

❌ Pixel cannot be placed on international sites.

🚩 Important: Placing MNTN pixels in iFrames hinders the code from effectively mapping products into dynamic product carousels, retrieving the unique order ID and order amount variables, comprehending the current page URL, and can result in inaccurate reporting.

Site Direct Installation Steps

1️⃣ Copy the tracking pixel from the Tracking Pixel field. You can do this by using the Copy Code button, which will store the code on your clipboard.

2️⃣ Paste it in the HTML on every page of your website. Most preferably just above the end </body> tag or in your global header.

3️⃣ Confirm the pixel is firing on all pages of the site, including checkout pages, cart pages, and conversion pages.

💡Note: The tracking pixel is placed on the conversion page in order to run specific campaigns and send tracking information to our data warehouse.

Implementing Your MNTN Conversion Pixel

Setup Requirements

✅ The point of conversion must be accessible from the main site.

❌ Pixel cannot be placed within any iFrames.

❌ Pixel cannot be placed on international sites.

Site Direct Installation Steps

1️⃣ Copy the conversion pixel from the Conversion Pixel field. You can do this using the Copy Code button, which will store the code on your clipboard.

2️⃣ Conversion pixels should only be placed on confirmation pages that are utilized for site conversion and should fire for all conversions.

3️⃣ Map in variables into parameters "l" and "i" by replacing the text within the double quotes with the corresponding variables from your site.

💡 Note: For more information (including examples of what you could pass into each field depending on the conversion event) on the Conversion Pixel's Order ID and Order Amount fields, check out this article here.

→ l = "ORDER ID"

The order ID field can be leveraged for any unique identifier associated with the conversion event.

Though it is strongly recommended, you can also move forward without mapping anything into the order ID field.

→ i = "TOTAL ORDER AMOUNT"

The order amount field should be leveraged to map your conversion point's specific dollar value.

In most cases, the order amount field would be the purchase amount. However, this field can also be used if you consider a non-revenue conversion point as carrying a specific dollar value to your business.

💡 Note: No changes should be made to the other parameters seen in the conversion pixel's code (i.e. c="", k="", g="", etc.). Only adjust the order ID and order amount fields.

If you do not have a dollar value associated with your conversion point, you can move forward without mapping one in.

🧠 Pro Tip: We recommend mapping the order amount value exclusive of tax and shipping to accurately report out on ROAS in your MNTN Reporting Dashboard.

4️⃣ Once complete, click the I Installed This button within the MNTN platform.

Further Pixel Setup Considerations

For Mobile Sites

If you run a separate domain for your (web-based) mobile site, you can follow the same procedures above to ensure the same data is being passed by our Tracking Pixel.

If you do not install the Tracking Pixel on your mobile site, you will lose performance as a result of excluding all the user data from your mobile traffic.

Security Tool Whitelisting

The domain (*.mountain.com) for our pixels should fall under the "script-src" section of the content security policy. For example: script-src blob: 'self' 'unsafe-eval' 'unsafe-inline' *.mountain.com

Did this answer your question?