Overview
Use this article to verify if your MNTN pixel is installed and firing correctly using Chrome DevTools. It's useful when validating pixel events on live pages. Since it doesn't require a developer background, use it yourself or feel free to share it with your developer.
Before you begin:
This article is written for Google Chrome but works the same in Firefox and Safari.
Check for Pixels in ChromeDev
Navigate to your website.
Open Google Chrome and navigate to your website.
Open Chrome DevTools.
Right-click anywhere on your webpage and select Inspect.
💡 Pro Tip: Or use a keyboard shortcut:
Mac:
Cmd + Option + IWindows:
Ctrl + Shift + I
This opens the Developer Tools panel.
Select the Network tab.
At the top of the panel, click Network.
💡 Pro Tip: If this tab isn’t visible, click the >> to find it. Make sure you’re on the Network tab before refreshing the page. Network activity only shows from the moment the tab is open.
Narrow the list to pixel-related scripts.
In the top-left Filter box, type
mountain.Refresh your browser.
Pro Tip: Use a keyboard shortcut:
Mac:
Cmd+RWindows:
Ctrl+R
Locate your MNTN scripts.
Under the Name field, look for both of these MNTN scripts:
spx?dxver= ; AND
st?ga_tracking_id=
These indicate success — the MNTN pixel is present and firing!
⚠️ Warning: If you're only seeing the
spx?dxver=script, that could indicate issues with installation.
Check if It’s a Conversion Pixel
To confirm that you’re seeing a Conversion Pixel and not just a tracking pixel:
Click on a script request (like
st?ga_tracking_id=...)Click on the Payload tab.
Look for this key-value:
conv = 1
This means you're looking at a Conversion Pixel and a conversion event has been successfully captured.
Not Seeing the Pixel?
Here’s what to check:
Confirm the pixel is installed on the correct page.
Try a hard refresh (
Shift + Cmd + RorShift + Ctrl + R).Check for JavaScript errors in the Console tab of DevTools.
Review your tag manager (if applicable) to ensure the tag was published.
📝 Note: If your site loads content dynamically, you may need to wait a moment or trigger the action that causes the pixel to fire (e.g., completing a form or reaching a confirmation page).
Next Steps
Still stuck? Click the button below to reference our in-depth pixel installation documentation.