MNTN Conversions Pixel (Server-Side)

introduction the mntn conversions pixel destination allows you to send server side conversion events from chord directly to mntn use this destination to improve attribution accuracy, strengthen campaign optimization, and ensure your ctv investment reflects real business outcomes this destination complements your on site mntn tracking pixel for best results, use both what this destination does when enabled, chord sends selected conversion events (such as purchases) directly from our infrastructure to mntn using secure server side delivery server side delivery helps improve conversion accuracy reduce signal loss from browser restrictions strengthen attribution reliability provide more complete optimization feedback for ctv campaigns because events originate from your unified chord data model, you send consistent, validated event data — not fragmented signals how it works a customer completes a conversion event on your site (for example, a purchase) the event is captured and modeled within chord chord securely sends the event to mntn via server side integration mntn uses the event for attribution and campaign optimization this reduces dependency on browser based tracking alone prerequisites before connecting the mntn conversions pixel destination, confirm you have an active mntn account the mntn tracking pixel installed on your website a configured conversion goal inside mntn api credentials or ingestion details from mntn appropriate permissions in your mntn account if you do not have api credentials, contact your mntn representative chord sends the events you select — but conversion goals must already be defined in mntn connecting the mntn conversions pixel log into the chord platform navigate to cdp select destinations click add destination choose mntn conversions pixel from the catalog enter destination name advertiser id conversion type override (optional) select the conversion events you want to send click create recommended event types most brands send purchase completed subscription started lead submitted if you are unsure which events to send, align them with your defined mntn conversion goals testing and validation after activation confirm conversion events appear in your mntn dashboard validate order count and revenue totals monitor match rates if events do not appear confirm credentials are valid confirm conversion goals are configured in mntn confirm selected events are firing in chord confirm your mntn tracking pixel is installed properly when to use this destination use the mntn conversions pixel when you want stronger attribution accuracy you are experiencing signal loss from browser restrictions you want mntn to optimize against actual revenue data you want server side reliability in addition to web pixel tracking 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