Recharge to Criteo
Forward every Recharge event to Criteo 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 Criteo with Upstack Data
Recharge
Bring subscription events into the same resolved customer — new subscriptions, renewals, churn and reactivation.
Recharge integration
Criteo
Send resolved conversions to Criteo so retargeting stops re-serving people who already bought, and starts optimising on the ones who did.
Criteo integrationWhat changes
What changes when Recharge feeds Criteo.
Server-side delivery
Events reach Criteo 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 Criteo 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 Criteo needs.
Recharge and Criteo 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 Criteo 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
Criteo receives
- hashed email
- match the buyer for suppression and matching
- criteo_click_id
- credit the click
- event_id
- dedupe against the OneTag
- value / currency
- value-based bidding
- product ids
- suppress the exact items already bought
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 Criteo
Criteo Management CenterAssetsEvents. The event log shows server-side arrivals and the identifiers they carried.
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 Criteo.
- ShopifyCriteo
- WooCommerceCriteo
- BigCommerceCriteo
- Checkout ChampCriteo
- Custom stackCriteo
- FunnelishCriteo
- Lasso CommerceCriteo
- Phoenix TechnologiesCriteo
- SkioCriteo
- Loop SubscriptionsCriteo
- StripeCriteo
- Everything Criteo can take12 sources feed Criteo, and the setup is the same for each one.Criteo 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 Criteo.
A 15-minute walkthrough of this connector on your own account.