Recharge to Omnisend
Forward every Recharge event to Omnisend server-side, resolved to a person against a 750M+ device graph — so flows trigger on a known profile rather than an anonymous session.
Connection
Connect Recharge to Omnisend with Upstack Data
What changes
What changes when Recharge feeds Omnisend.
Server-side delivery
Events reach Omnisend 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 Omnisend 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 Omnisend needs.
Recharge and Omnisend 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 Omnisend 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
Omnisend receives
- email / phone
- contact key
- event properties
- workflow triggers
- cart / order value
- revenue attribution
Sending you can audit
How you know it is working.
Messaging mistakes are expensive and public. These controls exist so a flow never fires against a profile that should not have received it.
Per-profile inspection
Trace any event to the profile it resolved to, and see why.Deduplication
One order produces one event, so a single purchase cannot trigger the same flow twice.Bot and fraud filtering
Automated traffic never becomes a profile, so list quality and deliverability are not paying for it.
Where to check in Omnisend
OmnisendAudiencethe contact's activity, and the automation's own trigger log.
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 Omnisend.
- ShopifyOmnisend
- WooCommerceOmnisend
- BigCommerceOmnisend
- Checkout ChampOmnisend
- Custom stackOmnisend
- FunnelishOmnisend
- Lasso CommerceOmnisend
- Phoenix TechnologiesOmnisend
- SkioOmnisend
- Loop SubscriptionsOmnisend
- StripeOmnisend
- Everything Omnisend can take12 sources feed Omnisend, and the setup is the same for each one.Omnisend 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 Omnisend.
A 15-minute walkthrough of this connector on your own account.