Recharge to Taboola
Forward every Recharge event to Taboola server-side, resolved to a person against a 750M+ device graph — with restored click IDs, deduplicated conversions and delivery you can audit.
Connection
Connect Recharge to Taboola with Upstack Data
Recharge
Bring subscription events into the same resolved customer — new subscriptions, renewals, churn and reactivation.
Recharge integration
Taboola
Forward resolved conversions to Taboola through its server-side API, so discovery traffic gets credited for the purchases it actually produced.
Taboola integrationWhat changes
What changes when Recharge feeds Taboola.
Server-side delivery
Events reach Taboola 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 Taboola 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 Taboola needs.
Recharge and Taboola 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 Taboola 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
Taboola receives
- hashed email / phone
- identity matching on arrival
- taboola_click_id
- credit the click that drove it
- external_id
- stable person across sessions
- event_id
- dedupe against the browser pixel
- value / currency
- value-based bidding
Delivery you can audit
How you know it is working.
Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.
Per-event inspection
Every conversion is inspectable from the moment it fires to the moment the platform confirms it.Deduplication
Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.Bot and fraud filtering
Automated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
Where to check in Taboola
Taboola AdsTrackingConversions. The conversions view shows the source of each event, so server-side arrivals are distinguishable.
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 Taboola.
- ShopifyTaboola
- WooCommerceTaboola
- BigCommerceTaboola
- Checkout ChampTaboola
- Custom stackTaboola
- FunnelishTaboola
- Lasso CommerceTaboola
- Phoenix TechnologiesTaboola
- SkioTaboola
- Loop SubscriptionsTaboola
- StripeTaboola
- Everything Taboola can take12 sources feed Taboola, and the setup is the same for each one.Taboola 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 Taboola.
A 15-minute walkthrough of this connector on your own account.