Skip to main content
Request a demo
  1. Home
  2. Connectors
  3. Stripe - MNTN
Stripe MNTN

Send events from your Stripe-billed app to MNTN

Each event is resolved to a person against a 750M+ device graph before it reaches MNTN, with restored click IDs, deduplicated conversions and delivery you can audit.

Request a demo Start free trial
US device IDs in the graph
750M+
Match rate on events
90%+
Identity window, per customer
Lifetime
Most brands are live
<20 min

How it flows

How a Stripe event reaches MNTN. Sent from your app, resolved to a person, then forwarded.

01 Capture

Captured from Stripe

For apps that bill through Stripe, send payment and subscription events to Upstack with the Upstack Pixel and JavaScript SDK, resolved to a customer before they reach the tools you spend on.

See the Stripe integration
StripeWhat it sends
  • subscription_initial_purchaseyou fire it for the first subscription order
  • subscription_recurring_purchaseon invoice.paid for an existing subscription
  • payment_succeededmaps to invoice.paid or charge.succeeded
  • payment_refundedmaps to charge.refunded
  • amount / currencyamount in cents, with invoiceId and subscriptionId

02 Understand

Resolved to one person before it leaves

Every Stripe event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.

How resolution works
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.

Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.

03 Activate

Delivered to MNTN

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

See the MNTN integration
MNTNWhat it receives
  • 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

The catch

A retried payment produces several Stripe objects for one purchase.

Forwarding each as a conversion inflates reported performance by the retry rate, which is highest on exactly the campaigns bringing in the least reliable payment methods. Fire the Upstack event when Stripe reports the payment succeeded (invoice.paid or charge.succeeded), so only the settled payment becomes a conversion.

Where to check in MNTNDelivery you can audit

MNTN Performance Conversions

Matched conversions report the household attribution window they fell inside.

What changes

What changes when Stripe feeds MNTN. Two gains on the MNTN side, two on the Stripe side.

MNTN

Server-side delivery

Events reach MNTN through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.

MNTN

Identity-resolved events

Events sent to MNTN carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.

Stripe

Subscription purchases as events

Fire subscription_initial_purchase for the first order and subscription_recurring_purchase each time a renewal is paid, so first orders and renewals are reported separately.

Stripe

Payments and refunds

payment_succeeded, payment_failed and payment_refunded each map to a Stripe event (invoice.paid or charge.succeeded, invoice.payment_failed, charge.refunded), so money events reach Upstack when your app fires them.

Setup

Live in under 20 minutes.

Connect Stripe once and every destination, MNTN included, is forwarded the same resolved events.

Upstack dashboardExample
MNTN Destination Healthy
Read the full MNTN setup guide

  1. 01

    Install the Upstack Pixel and SDK

    Add the Upstack Pixel to your app, then fire the subscription and payment events with the JavaScript SDK when Stripe reports them, such as subscription_recurring_purchase when invoice.paid fires for an existing subscription.

  2. 02

    Add the MNTN destination

    Under Destinations, add MNTN. Every resolved Stripe event is then forwarded to it.

  3. 03

    Check delivery to MNTN

    Every conversion is inspectable from the moment it fires to the moment the platform confirms it.

FAQ

Questions about Stripe and MNTN.

How do I check that Stripe events are reaching MNTN?

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

Will a purchase be counted twice?

No. Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.

How long does it take to connect Stripe to MNTN?

Most brands are live in under 20 minutes. Once Stripe events reach Upstack, every destination receives the same resolved events, MNTN included.

Related connectors

See all 408 connectors

Stripe to

All 34 Stripe connectors

MNTN from

MNTN integration

Get Stripe talking to MNTN.

A 15-minute walkthrough of this connector on your own account.

Request a demo Start free trial

21-day free trial, no card. Month to month.