Recharge to Your warehouse
Forward every Recharge event to Your warehouse server-side, resolved to a person against a 750M+ device graph — as a full-fidelity event stream you can query yourself.
Connection
Connect Recharge to Your warehouse with Upstack Data
Recharge
Bring subscription events into the same resolved customer — new subscriptions, renewals, churn and reactivation.
Recharge integrationYour warehouse
A clean, resolved event stream into BigQuery, Snowflake or Redshift — the same data your dashboards run on.
Your warehouse integrationWhat changes
What changes when Recharge feeds Your warehouse.
One resolved event stream
The same identity-resolved events that reach your ad platforms, landed in your warehouse.
Nothing sampled
Full-fidelity events, not an aggregate or a sample.
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 Your warehouse needs.
Recharge and Your warehouse 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 Your warehouse 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
Your warehouse receives
- event_id
- primary key you can join on
- resolved person ID
- stitch sessions to customers
- full property payload
- nothing dropped, nothing sampled
- ingest timestamp
- rebuild any point-in-time view
A stream you can audit
How you know it is working.
Warehouse data is only useful if you trust it enough to base a decision on it. These controls exist so you can reconstruct how any row got there.
Full lineage
Every row traceable to the event that produced it and the time it landed.Deduplication
Stable event IDs, so re-runs and backfills do not double rows.Bot and fraud filtering
Filtered before load, with the filter decision recorded.
Where to check in Your warehouse
Query the events table directly: count distinct resolved person IDs against count distinct sessions, and compare the ratio to what your analytics reports.
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 Your warehouse.
- ShopifyYour warehouse
- WooCommerceYour warehouse
- BigCommerceYour warehouse
- Checkout ChampYour warehouse
- Custom stackYour warehouse
- FunnelishYour warehouse
- Lasso CommerceYour warehouse
- Phoenix TechnologiesYour warehouse
- SkioYour warehouse
- Loop SubscriptionsYour warehouse
- StripeYour warehouse
- Everything Your warehouse can take12 sources feed Your warehouse, and the setup is the same for each one.Your warehouse 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 Your warehouse.
A 15-minute walkthrough of this connector on your own account.