Skip to main content
Request a demo
  1. Home
  2. Integrations
  3. Recharge
Upstack Data

Recharge integration: every charge captured server-side and resolved to a person

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

Request a demo Start free trial
Role
Source
Category
Payments & subscriptions
Pre-built connectors
34 destinations
Plans
All plans

What Upstack captures

Every Recharge event leaves resolved to a person. Captured on the server, resolved to a person, then sent.

In: from RechargeWhat it carries
  • 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

Subscriptions, renewals and churn as real events.

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 Meta Conversions API1 of 34 destinations
  • em, ph (SHA-256)raise Event Match Quality
  • fbclid / _fbpcredit the click that drove it
  • external_idstable person across sessions
  • event_iddedupe against the browser pixel
  • value / currencyvalue-based bidding

Conversions API with higher Event Match Quality.

See the set-up reference See all 34 destinations How resolution works

About Recharge

Recharge knows the difference between a first charge and a renewal.

Almost nothing downstream does, because both arrive looking like revenue. Upstack reads that distinction and preserves it: new subscriptions can be forwarded as their own conversion, renewals as recurring revenue, and cancellations as state changes rather than silence. Ad platforms then optimize toward acquiring subscribers instead of re-finding the ones you have, and flows stop welcoming people who have been subscribed for a year.

What Recharge is

Recharge is the subscription and recurring-billing platform behind a large share of DTC subscription programs, handling plans, renewals, swaps and churn.

Subscription events are economically different from one-off orders: a new subscription carries a lifetime value a single checkout does not. Treating them as the same conversion is where most subscription brands lose the plot on acquisition.

How Recharge works

Recharge sits alongside the storefront and owns the recurring relationship. When a shopper buys a subscription, Recharge creates a subscription object and then generates a charge on each billing cycle, emitting webhooks for created, updated, canceled, skipped and reactivated states. The subscription and the charge are separate objects, which matters: one subscription produces many charges over its life. Recharge also handles swaps, pauses and address changes, each of which updates state without producing an order in the usual sense.

What you can do with it

Three jobs Recharge does once it is connected.

01

Capture every order server-side

Recharge events are captured from the server rather than the shopper’s browser, so ad blockers and ITP stop deciding which of your conversions get counted. Nothing depends on a script surviving the page.

02

Resolve each event to a person

Every Recharge event is matched against a 750M+ device graph before it leaves, so a phone browse and a desktop checkout resolve to one customer rather than two strangers. Returning buyers are recognized as returning.

03

Optimize on subscriptions, not subscribers

New subscriptions are sent as their own conversion, separate from one-off orders. That is the event carrying the LTV:CAC that makes acquisition spend profitable. A single checkout is not.

Pre-built connectors

Recharge forwards to 34 destinations. Connect Recharge once. Every destination is already wired.

See all 34 Recharge connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for Recharge as a source, next to the Recharge developer docs.

FAQ

Recharge integration questions.

What does Upstack capture from Recharge?

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

Which plans include the Recharge integration?

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

Which destinations can Recharge send to?

34 destinations, including Meta Conversions API, Google Ads Conversions, TikTok Events API, Pinterest, Snapchat and Reddit. 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 sources to connect.

See all integrations

Get Recharge tracking right.

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

Request a demo Start free trial