- US device IDs in the graph
- 750M+
- Match rate on events
- 90%+
- Identity window, per customer
- Lifetime
- Most brands are live
- <20 min
How it flows
How a Recharge event reaches Vibe. Captured on the server, resolved to a person, then sent.
01 Capture
Captured from Recharge
Bring subscription events into the same resolved customer: new subscriptions, renewals, churn and reactivation.
See the Recharge integration →
RechargeWhat it sends subscription_idthe subscription, not the ordercharge_ideach recurring chargeemail / phonesubscriber contactstatusactive, cancelled, paused, reactivatedis_first_chargenew subscription versus renewalproduct / frequencywhat they subscribed to and how often
02 Understand
Resolved to one person before it leaves
Every Recharge event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.
How resolution works →
Resolved 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.
03 Activate
Delivered to Vibe
Send resolved conversions to Vibe so streaming TV campaigns are attributed to the orders they drove.
See the Vibe integration →
VibeWhat it receives hashed email / phonematch a purchase to an exposed householdip / user_agenthousehold matching for a no-click channelorder timestampplace the order inside the campaign windowvalue / currencymeasure streaming on revenueevent_iddedupe against site-side reporting
The catch
Recharge fires a charge event on every renewal.
Forwarded naively, your ad platform learns that customers you already acquired keep converting, and prospecting drifts toward people who look like existing subscribers. Only the first charge is an acquisition.
Where to check in VibeDelivery you can audit
Vibe › Campaigns › Conversions
Matched conversions report the campaign window they were attributed inside.
What changes
What changes when Recharge feeds Vibe. Two gains on the Vibe side, two on the Recharge side.
Vibe
Server-side delivery
Events reach Vibe through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
Vibe
Identity-resolved events
Events sent to Vibe carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.
Recharge
Subscriptions as their own conversion
Send new subscriptions to the ad platforms as a distinct event, not lumped in with one-time orders.
Recharge
Renewals counted properly
Recurring charges are forwarded as real revenue, so LTV reporting reflects what the customer is actually worth.
Setup
Live in under 20 minutes.
Connect Recharge once and every destination, Vibe included, is forwarded the same resolved events.
Upstack dashboardExample
Recharge Data source Connected
Vibe Destination Healthy
Read the full Vibe setup guide → -
01
Connect Recharge
Bring subscription events into the same resolved customer: new subscriptions, renewals, churn and reactivation.
-
02
Add the Vibe destination
Under Destinations, add Vibe. Every resolved Recharge event is then forwarded to it.
-
03
Check delivery to Vibe
Every conversion is inspectable from the moment it fires to the moment the platform confirms it.
FAQ
Questions about Recharge and Vibe.
How do I check that Recharge events are reaching Vibe?
Open Vibe › Campaigns › Conversions. Matched conversions report the campaign window they were attributed inside.
Will a purchase be counted twice?
No. Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
How long does it take to connect Recharge to Vibe?
Most brands are live in under 20 minutes. Once Recharge is connected, every destination receives the same resolved events, Vibe included.