Recharge to Loops
Forward every Recharge event to Loops server-side, resolved to a person against a 750M+ device graph — so records and reporting reflect the person, not the device.
Connection
Connect Recharge to Loops with Upstack Data
What changes
What changes when Recharge feeds Loops.
Server-side delivery
Events reach Loops through its server API, not the browser — so ad blockers, ITP and consent banners don’t cost you conversions.
Identity-resolved events
Every event sent to Loops carries a resolved customer, matched against a 750M+ device graph.
Subscriptions as their own conversion
Send new subscriptions to the ad platforms as a distinct event, not lumped in with one-time orders.
Renewals counted properly
Recurring charges are forwarded as real revenue, so LTV reporting reflects what the customer is actually worth.
What actually moves
What Recharge carries, and what Loops needs.
Recharge and Loops describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Recharge can put on an event, the right is what Loops can actually use.
Recharge sends
- subscription_id
- the subscription, not the order
- charge_id
- each recurring charge
- email / phone
- subscriber contact
- status
- active, cancelled, paused, reactivated
- is_first_charge
- new subscription versus renewal
- product / frequency
- what they subscribed to and how often
Loops receives
- contact key
- event name
- what the lifecycle message reacts to
- data variables
- personalisation
Records you can audit
How you know it is working.
A CRM is only as trustworthy as its worst duplicate. These controls exist so the record reflects the person.
Per-record inspection
Trace any property back to the event that set it.Deduplication
One person, one record, across devices and identifiers.Bot and fraud filtering
Automated traffic never becomes a contact.
Where to check in Loops
Loopsthe contact's event history.
Related connectors
Other places Recharge can send to.
- RechargeMeta Conversions API
- RechargeGoogle Ads Conversions
- RechargeTikTok Events API
- RechargePinterest
- RechargeSnapchat
- RechargeReddit
- RechargeMicrosoft Ads
- RechargeX
Other sources that feed Loops.
- ShopifyLoops
- WooCommerceLoops
- BigCommerceLoops
- Checkout ChampLoops
- Custom stackLoops
- FunnelishLoops
- Lasso CommerceLoops
- Phoenix TechnologiesLoops
- SkioLoops
- Loop SubscriptionsLoops
- StripeLoops
- Everything Loops can take12 sources feed Loops, and the setup is the same for each one.Loops integration
- How resolution worksEvery event matched against a 750M+ device graph before it is forwarded.Upstack Signal
- What it costsThree plans that scale with your order volume. Every connector is on every plan.See pricing
Get Recharge talking to Loops.
A 15-minute walkthrough of this connector on your own account.