BigCommerce to Microsoft Ads
Forward every BigCommerce 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 BigCommerce to Microsoft Ads with Upstack Data
BigCommerce
Server-side capture of BigCommerce storefront and checkout events, resolved and forwarded downstream.
BigCommerce 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 BigCommerce 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.
Every event, server-side
Storefront and checkout events are captured from BigCommerce on the server, independent of the browser.
One setup, every destination
Connect BigCommerce once and forward to every ad platform, email tool and warehouse you run.
What actually moves
What BigCommerce carries, and what Microsoft Ads needs.
BigCommerce and Microsoft Ads describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what BigCommerce can put on an event, the right is what Microsoft Ads can actually use.
BigCommerce sends
- order_id
- BigCommerce order
- email / phone
- checkout contact
- customer_id
- BigCommerce customer record
- products
- catalogue items on the order
- total_inc_tax
- order value
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 BigCommerce can send to.
- BigCommerceMeta Conversions API
- BigCommerceGoogle Ads Conversions
- BigCommerceTikTok Events API
- BigCommercePinterest
- BigCommerceSnapchat
- BigCommerceReddit
- BigCommerceX
- BigCommerceAppLovin
Other sources that feed Microsoft Ads.
- ShopifyMicrosoft Ads
- WooCommerceMicrosoft Ads
- Checkout ChampMicrosoft Ads
- RechargeMicrosoft 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 BigCommerce talking to Microsoft Ads.
A 15-minute walkthrough of this connector on your own account.