MNTN Tracking Pixel (Web Pixel)

introduction the mntn tracking pixel destination enables client side event delivery from your website to mntn this pixel captures user activity directly in the browser and supports audience building, attribution, and campaign measurement for full signal coverage, use this destination alongside the mntn conversions pixel what this destination does the mntn tracking pixel fires browser based events to mntn tracks user behavior (such as page views and conversions) enables audience building and retargeting supports attribution measurement unlike the conversions pixel, this destination relies on browser execution how it works a visitor interacts with your website the mntn tracking pixel fires in the browser event data is sent directly from the user’s device to mntn because this is browser based, delivery may be impacted by ad blockers, privacy settings, or browser restrictions prerequisites before enabling the mntn tracking pixel you must have an active mntn account you must have your mntn pixel id your site must allow javascript execution your consent management setup must permit firing marketing pixels where required connecting the mntn tracking pixel log into the chord platform navigate to cdp select destinations click add destination choose mntn tracking pixel enter destination name advertiser id click create recommended events common browser side events include page viewed product viewed added to cart purchase completed align event selection with your campaign goals and consent policies testing and validation after activation use browser developer tools to confirm the pixel fires confirm events appear in your mntn dashboard validate event parameters (order id, revenue, etc ) if events do not fire confirm the pixel id is correct confirm your site permits marketing scripts confirm consent conditions allow firing confirm selected events are triggering in chord using both mntn destinations together for the strongest performance, use tracking pixel for browser level engagement tracking and audience building conversions pixel for reliable server side conversion delivery this combined approach improves attribution completeness optimization feedback loops campaign performance confidence browser side captures intent server side confirms outcomes together, they give mntn the clearest signal possible before connecting destinations in the chord cdp, please verify with all destination owners that all non chord cdp configured destinations are disabled running external destinations alongside configured chord cdp destinations can result in duplicate events downstream