Recharge to Klaviyo
Forward every Recharge event to Klaviyo 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 Klaviyo with Upstack Data
Recharge
Bring subscription events into the same resolved customer — new subscriptions, renewals, churn and reactivation.
Recharge integrationKlaviyo
Attach re-identified emails to events before they reach Klaviyo, so browse and cart flows fire for people the pixel lost.
Klaviyo integrationWhat changes
What changes when Recharge feeds Klaviyo.
Recover carts you couldn’t email
Anonymous browsers are resolved to a known profile, so abandonment flows can trigger for visitors Klaviyo never identified.
Profiles, not sessions
Events arrive attached to a resolved customer, so flow logic and segmentation work on a person.
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 Klaviyo needs.
Recharge and Klaviyo 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 Klaviyo 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
Klaviyo receives
- email / phone
- the profile key — no profile, no send
- external_id
- tie a browse to a known person
- $value
- flow and campaign revenue attribution
- event properties
- what the flow branches on
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 Klaviyo
KlaviyoAnalyticsMetrics. The event appears as its own metric, and the profile count on it is the number you were losing before.
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 Klaviyo.
- ShopifyKlaviyo
- WooCommerceKlaviyo
- BigCommerceKlaviyo
- Checkout ChampKlaviyo
- Custom stackKlaviyo
- FunnelishKlaviyo
- Lasso CommerceKlaviyo
- Phoenix TechnologiesKlaviyo
- SkioKlaviyo
- Loop SubscriptionsKlaviyo
- StripeKlaviyo
- Everything Klaviyo can take12 sources feed Klaviyo, and the setup is the same for each one.Klaviyo 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 Klaviyo.
A 15-minute walkthrough of this connector on your own account.