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.
💡 Note: While you can install MNTN's site-direct pixels, we recommend that you leverage our Shopify app or install MNTN pixels using our Google Tag Manager Template. The site-direct method should only be leveraged if you do not have a Shopify store or use Google Tag Manager.
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 developer 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 developer's email address(es) responsible for implementing your pixels.
3️⃣ Once complete, click Send to email the team with the pixels attached for installation.
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 copy the pixel using the Copy Code button to store the code on your clipboard.
2️⃣ Paste it in the HTML on every website page, preferably in the global header.
3️⃣ Confirm that the pixel is firing on all site pages, including checkout, cart, and conversion pages.
💡Note: The tracking pixel is placed on the conversion page 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 to store the code on your clipboard.
2️⃣ Conversion pixels should only be placed on confirmation pages utilized for site conversions and fire for all conversions.
3️⃣ Map the Order ID and Order Amount 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: The other parameters seen in the conversion pixel's code (e.g., c="", k="", g="", etc.) should not be changed. 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.
🧠 Pro Tip: We recommend mapping the order amount value, exclusive of tax and shipping, to report out on ROAS in your MNTN Reporting Dashboard accurately.
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 that our tracking pixel passes the same data.
If you do not install the Tracking Pixel on your mobile site, you will lose performance because you will exclude all 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
WHERE TO GO NEXT: