Skip to main content
Upstack Data

MNTN integration: identity-resolved conversions, sent server-side

Forward resolved conversions to MNTN so connected-TV spend is judged against orders rather than against household reach.

Role
Destination
Category
Ad platforms
Pre-built connectors
12 sources
Plans
All plans

What Upstack sends

Every conversion reaches MNTN with the identifiers it matches on. Captured on the server, resolved to a person, then sent.

In: from Shopify1 of 12 sources
  • order_idShopify order and checkout token
  • email / phonecustomer contact from checkout
  • customer_idShopify customer record, if they have one
  • line_itemsproducts, variants and quantities
  • total / subtotal / discountorder economics

Storefront events from the Upstack Pixel, orders directly from Shopify.

Upstack DataResolved before it is sent
  • IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
  • customer_typeNew or returning, resolved before send.
  • DeduplicationBrowser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
  • Bot and fraud filteringAutomated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
Out: to MNTNOn every event
  • hashed email / phonematch a purchase to an exposed household
  • ip / user_agenthousehold matching for a no-click channel
  • event_iddedupe against site-side reporting
  • value / currencymeasure television on revenue
  • order timestampplace the order inside the airing window

Connected TV, attributed to purchases.

About MNTN

Upstack forwards resolved purchases server-side with the full order value, so MNTN measures against complete orders rather than partial browser events.

For a channel with no click, the conversion feed is the entire measurement apparatus.

What MNTN is

MNTN sells connected-TV advertising to performance marketers, on the promise that television can be bought and measured like direct response.

Delivering on that promise requires conversion data television has never had access to.

How MNTN works

MNTN attributes by matching households that saw an ad against site visits and purchases, within its own attribution window. The quality of that match depends entirely on the conversion data it is given.

What you can do with it

Three jobs this connector does inside MNTN.

01

Send complete conversions

Conversions reach MNTN through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival, and the conversions you never saw stop being invisible.

02

Optimize on the customer you want

Map any order attribute to the conversion MNTN receives (profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout), so the platform learns from the buyers worth acquiring.

03

Television measured on orders

Complete, resolved purchases give a no-click channel something real to attribute against, rather than a partial view of site activity.

Pre-built connectors

12 sources connect to MNTN. Whichever of these you run, MNTN is one switch away.

See all connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for MNTN as a destination.

FAQ

MNTN integration questions.

What does Upstack send to MNTN?

Forward resolved conversions to MNTN so connected-TV spend is judged against orders rather than against household reach.

How do I check that events are reaching MNTN?

Open MNTN › Performance › Conversions. Matched conversions report the household attribution window they fell inside.

Which plans include the MNTN integration?

All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.

Which sources can send events to MNTN?

12 sources: Shopify, WooCommerce, BigCommerce, Checkout Champ, Recharge, Custom stack, Funnelish, Lasso Commerce, Phoenix Technologies, Skio, Loop Subscriptions and Stripe. Each one has its own pre-built connector.

Will Upstack slow down my store?

Upstack’s own pixel loads asynchronously and fails silently, so it doesn’t hold up your pages. What each destination adds depends on its Tracking Method. The default, Browser + Server, loads that platform’s own tag on your store, in place of the copy you would otherwise install yourself, and also sends the same events from Upstack’s servers. Choose Server for any destination that offers it and its tag never loads, while its events still arrive from Upstack’s servers.

Similar integrations

Other Ad platforms integrations.

See all integrations

Get MNTN tracking right.

A 15-minute walkthrough tailored to your stack and channels.