Home
Connectors
Recharge - MNTN

MNTN

Send every Recharge event to MNTN, server-side

Q: How do I check that Recharge events are reaching MNTN?

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

Q: Will a purchase be counted twice?

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

Q: How long does it take to connect Recharge to MNTN?

Most brands are live in under 20 minutes. Once Recharge is connected, every destination receives the same resolved events, MNTN included.

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 Recharge event reaches MNTN. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from Recharge

Bring subscription events into the same resolved customer: new subscriptions, renewals, churn and reactivation.

See the Recharge integration

RechargeWhat it sends

subscription_idthe subscription, not the order
charge_ideach recurring charge
email / phonesubscriber contact
statusactive, cancelled, paused, reactivated
is_first_chargenew subscription versus renewal
product / frequencywhat they subscribed to and how often

02 Understand

Resolved to one person before it leaves

Every Recharge 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

Resolved 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

Recharge fires a charge event on every renewal.

Forwarded naively, your ad platform learns that customers you already acquired keep converting, and prospecting drifts toward people who look like existing subscribers. Only the first charge is an acquisition.

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 Recharge feeds MNTN. Two gains on the MNTN side, two on the Recharge 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.

Recharge

Subscriptions as their own conversion

Send new subscriptions to the ad platforms as a distinct event, not lumped in with one-time orders.

Recharge

Renewals counted properly

Recurring charges are forwarded as real revenue, so LTV reporting reflects what the customer is actually worth.

Setup

Live in under 20 minutes.

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

Upstack dashboardExample

Recharge Data source Connected

MNTN Destination Healthy

Read the full MNTN setup guide

01

Connect Recharge

Bring subscription events into the same resolved customer: new subscriptions, renewals, churn and reactivation.
02

Add the MNTN destination

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

Check delivery to MNTN

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