Recharge to Microsoft Ads
Forward every Recharge event to Microsoft Ads 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 Microsoft Ads with Upstack Data
Recharge
Bring subscription events into the same resolved customer — new subscriptions, renewals, churn and reactivation.
Recharge integration
Microsoft Ads
Send identity-resolved conversions to Microsoft Ads, so Bing and the Audience Network optimise on customers rather than on whatever the UET tag survived to see.
Microsoft Ads integrationWhat changes
What changes when Recharge feeds Microsoft Ads.
Server-side delivery
Events reach Microsoft Ads 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 Microsoft Ads 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 Microsoft Ads needs.
Recharge and Microsoft Ads 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 Microsoft Ads 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
Microsoft Ads receives
- hashed email / phone
- Enhanced Conversions matching
- msclkid
- keep Bing paid-search attribution
- conversion value
- value-based bidding
- transaction_id
- dedupe against the UET tag
- conversion_name
- map to the right UET goal
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 Microsoft Ads
Microsoft AdvertisingConversion goalsDiagnostics. The diagnostics view reports the share of conversions carrying usable hashed data.
Related connectors
Other places Recharge can send to.
- RechargeMeta Conversions API
- RechargeGoogle Ads Conversions
- RechargeTikTok Events API
- RechargePinterest
- RechargeSnapchat
- RechargeReddit
- RechargeX
- RechargeAppLovin
Other sources that feed Microsoft Ads.
- ShopifyMicrosoft Ads
- WooCommerceMicrosoft Ads
- BigCommerceMicrosoft Ads
- Checkout ChampMicrosoft Ads
- Custom stackMicrosoft Ads
- FunnelishMicrosoft Ads
- Lasso CommerceMicrosoft Ads
- Phoenix TechnologiesMicrosoft Ads
- SkioMicrosoft Ads
- Loop SubscriptionsMicrosoft Ads
- StripeMicrosoft Ads
- Everything Microsoft Ads can take12 sources feed Microsoft Ads, and the setup is the same for each one.Microsoft Ads 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 Microsoft Ads.
A 15-minute walkthrough of this connector on your own account.