Skip to main content

Install MNTN Pixels In Google Tag Manager

Learn how to add, configure, and manage MNTN tracking and conversion pixels in Google Tag Manager (GTM) for accurate campaign measurement.

Overview

MNTN supports tracking and conversion pixel installation through Google Tag Manager (GTM).

After installation and verification, pixel metrics become available within reporting to help measure website visits and conversion activity.

Why it matters

Pixels help you:

  • Measure website visits and conversion activity

  • Access reporting metrics like visits, conversions, CPA, and ROAS

  • Better understand campaign performance

  • Monitor pixel activity directly from the Pixels page

Before You Begin

Before you can install pixels with GTM, you'll need to create an account and container.

See Google's Get Started with Tag Manager to learn how.

Steps

1. Install pixels in GTM.

1. Go to GTM and login.

2. Click the arrows to install MNTN Pixels:

Tracking Pixel in GTM

  1. On the Accounts tab, under Container Name, click the desired container.

  2. On the Workspace tab, from the left navigation pane, click Tags.

  3. In the Tags box, click New.

  4. Click anywhere in the Tag Configuration box.

  5. Click the top Discover more tag types in the Community Template Gallery banner.

  6. In the upper right, click the magnifying glass icon.

  7. Search for MNTN.

  8. Select MNTN Tracking Pixel.

  9. Click Add to workspace.

  10. Click Add.

  11. In the Tag Configuration box under MNTN Advertiser ID ( required ), enter your MNTN Advertiser ID.

  12. Click anywhere in the Triggering box.

  13. Click All Pages.

  14. Click Save.

  15. Under Tag Name, optionally rename your Tag.

  16. Click Save.

  17. Click Submit.

  18. Click Publish.

  19. Under Name, enter MNTN Pixels.

  20. Click Continue.

Conversion Pixel in GTM

If you only want to measure website visits, you can install the MNTN Tracking Pixel only and skip this step.

Without the Conversion Pixel installed:

  • Site Visits reporting remains available

  • Conversion reporting metrics, including conversions, conversion rate, CPA, and ROAS, won't be available in reporting

To install it:

  1. On the Accounts tab, under Container Name, click the desired container.

  2. On the Workspace tab, from the left navigation pane, click Tags.

  3. In the Tags box, click New.

  4. Click anywhere in the Tag Configuration box.

  5. Click Discover More Tag Types.

  6. In the upper right, click the magnifying glass icon.

  7. Search for MNTN.

  8. Select MNTN Conversion Pixel.

  9. Click Add to Workspace.

  10. Click Add.

  11. In the Tag Configuration box under MNTN Advertiser ID ( required ), enter your MNTN Advertiser ID.

  12. Click anywhere in the Triggering box.

  13. Click the plus + icon.

  14. Click anywhere in the Trigger Configuration box.

  15. Choose the trigger type that fits your desired conversion setup.


    📘 Example: This trigger configuration fires the conversion pixel when a page URL contains “thank,” such as a thank-you or order confirmation page displayed after a completed action.

    This is a common example configuration, but conversion triggers are not one-size-fits-all. Trigger setups should be configured based on your specific website structure and the conversion actions you want to measure.


  16. Click Save.

  17. Under Trigger Name, optionally rename your Trigger.

  18. Click Save.

  19. Click Submit.

  20. Click Publish.

  21. Under Name, enter MNTN Pixels.

  22. Click Continue.

2. Verify installation in MNTN.

  1. Go back to the MNTN platform browser tab.

  2. Click Next: Verify →.

  3. Follow the on-screen steps to verify pixel installation.

  4. Click ᐅ Run verification.

    The Verifying Your Pixels modal displays.


    ⚠️ Warning: To verify the conversion pixel, MNTN must detect conversion activity on your site within the last 15 minutes.

    If no conversion activity is detected, verification may fail even if your pixel was installed correctly. Before running verification, complete a test conversion on your website, such as a form submission or purchase, to trigger the conversion pixel.

    This is especially important if your business does not receive frequent website conversions.


  5. If no pixel activity is detected, click ᐅ Re-run verification.

    Otherwise, skip to Step 6.

    You can re-run verification as many times as needed.


    💡 Pro Tip: If detection issues persist, see Troubleshoot Pixels Alerts and Statuses or you can opt out by clicking Opt-out of tracking > Yes, opt out of conversion tracking.


  6. Click ✓ Finish Setup.

Quick Answers

What is the dataLayer?

The dataLayer is a JavaScript object that stores data about user interactions, making it accessible to GTM for tracking and tag triggering. For example, you can use the dataLayer to capture information such as:

  • Page views or form submissions

  • Order ID, total value, and product details

  • Custom events like button clicks

How does the dataLayer work?

  • Data Collection: The dataLayer stores information about user interactions on the website.

  • Triggering Tags: GTM reads the data from the dataLayer and uses it to trigger tags based on conditions (e.g., firing a tag when a purchase is made).

  • Creating Variables: The dataLayer data can be stored in GTM variables (e.g., form IDs, user names, transaction values), which are then passed to analytics or advertising tools.

How to use the dataLayer:
Here’s an example of a dataLayer.push() used for tracking a form submission:

javascriptCopy codewindow.dataLayer = window.dataLayer || []; dataLayer.push({ 'event': 'formSubmission', 'formID': 'contactForm', 'userName': 'JohnDoe' });

GTM uses this data to trigger tags and populate variables, ensuring accurate and dynamic tracking. In this example:

  • An event named formSubmission is pushed to the dataLayer, along with the form ID and user name.

  • GTM can now use this event and data to trigger tags (such as tracking form completions).

Next Steps

Once your pixels are installed, visit this article to verify your installation:

Did this answer your question?