Recharge
Bring subscription events into the same resolved customer — new subscriptions, renewals, churn and reactivation.
About Recharge
What Recharge is, and why identity matters to it.
Recharge is the subscription and recurring-billing platform behind a large share of DTC subscription programmes, 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 it works
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, cancelled, 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.
With Upstack Data
Get more out of Recharge with Upstack Data.
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 optimise toward acquiring subscribers instead of re-finding the ones you have, and flows stop welcoming people who have been subscribed for a year.
What you can do with it
Three jobs Recharge does once it is connected.
Capture every order server-side
Recharge events are captured from the server rather than the shopper’s browser, so ad blockers, ITP and consent banners stop deciding which of your conversions get counted. Nothing depends on a script surviving the page.
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 recognised as returning.
Optimise 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 below is already wired.
34 destinations shown
- RechargeMeta Conversions API
- RechargeGoogle Ads Conversions
- RechargeTikTok Events API
- RechargePinterest
- RechargeSnapchat
- RechargeReddit
- RechargeMicrosoft Ads
- RechargeX
- RechargeAppLovin
- RechargeOutbrain
- RechargeTaboola
- RechargeMGID
- RechargeThe Trade Desk
- RechargeCriteo
- RechargeStackAdapt
- RechargeMNTN
- RechargeTatari
- RechargeRevContent
- RechargeTapjoy
- RechargeVibe
- RechargeOpenAI Ads
- RechargeKlaviyo
- RechargeAttentive
- RechargePostscript
- RechargeOmnisend
- RechargeSendlane
- RechargeYotpo
- RechargeOkendo
- RechargeGorgias
- RechargeHubSpot
- RechargePostHog
- RechargeLoops
- RechargeActiveCampaign
- RechargeYour warehouse
Similar integrations
Other Payments & subscriptions integrations.
- SkioSource
First charges and renewals, told apart.
- Loop SubscriptionsSource
Subscription state, not just revenue.
- StripeSource
Payments and subscriptions, captured server-side.
- How resolution worksThe 750M+ device graph, restored click IDs and the identifiers that persist for months.Upstack Signal
- Every integrationSix sources in, eighteen destinations out, and every pairing between them.Browse the catalogue
- What it costsThree plans that scale with your order volume. Same integrations on every plan.See pricing
Get Recharge tracking right.
A 15-minute walkthrough tailored to your stack and channels.