- US device IDs in the graph
- 750M+
- Match rate on events
- 90%+
- Identity window, per customer
- Lifetime
- Most brands are live
- <20 min
How it flows
How a Funnelish event reaches Microsoft Ads. Tracked on the funnel page, resolved to a person, then sent.
01 Capture
Captured from Funnelish
Add the Upstack Pixel to your Funnelish funnels to track what shoppers do there. When Funnelish creates the order in Shopify, Upstack records it like any other Shopify order.
See the Funnelish integration →
FunnelishWhat it sends page / eventsfrom the Upstack Pixel in each funnel’s headfbclid / gclid / ttclidclick IDs kept on the way to checkoutorder_idthe Shopify order Funnelish createsorder sourceshows as Funnelish in Upstack reports
02 Understand
Resolved to one person before it leaves
Every Funnelish event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.
How resolution works →
Resolved before it is sent - IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
customer_typeNew or returning, resolved before send.- DeduplicationBrowser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
- Bot and fraud filteringAutomated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
03 Activate
Delivered to Microsoft Ads
Send identity-resolved conversions to Microsoft Ads, so Bing and the Audience Network optimize on customers rather than on whatever the UET tag survived to see.
See the Microsoft Ads integration →
Microsoft AdsWhat it receives hashed email / phoneEnhanced Conversions matchingmsclkidkeep Bing paid-search attributionconversion valuevalue-based biddingeventIddedupe against the UET tagconversion_namemap to the right UET goal
Which events reach Microsoft Ads
Each Upstack event is mapped to the Microsoft Ads event below before it is sent.
| Upstack event | Sent to Microsoft Ads as | Key data on the event |
| Page view | pageLoad | URL, referrer, user agent |
| Product view | view_item | itemIds, value, currency |
| Add to cart | add_to_cart | itemIds, value, currency |
| Checkout | begin_checkout | value, currency |
| Purchase | purchase | value, currency, transactionId, itemIds |
Every event carries hashed email and phone, the msclkid click ID, IP address and user agent; Microsoft does not support address-level matching. Personal data is hashed with SHA-256 before it leaves Upstack.
The catch
Funnel pages sit outside your Shopify theme, so the Upstack app embed doesn't run on them, and click IDs such as fbclid, gclid and ttclid are easily dropped on the way to checkout.
Add the Upstack Pixel to each funnel and keep the click IDs on the links to checkout. The order itself reaches Upstack when Funnelish creates it in Shopify, counted once per Shopify order ID.
Where to check in Microsoft AdsDelivery you can audit
Microsoft Advertising › Conversion goals › Diagnostics
The diagnostics view reports the share of conversions carrying usable hashed data.
What changes
What changes when Funnelish feeds Microsoft Ads. Two gains on the Microsoft Ads side, two on the Funnelish side.
Microsoft Ads
Server-side delivery
By default Upstack sends events to Microsoft Ads from its servers as well as through the Microsoft Ads tag, so an event an ad blocker or browser privacy setting stops in the browser still arrives from the server.
Microsoft Ads
Identity-resolved events
Events sent to Microsoft Ads carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.
Funnelish
Funnel pages tracked
The pixel loads in the head of every funnel page, so visits and the events you configure are recorded on pages your theme never touches.
Funnelish
One setup, every destination
Connect Funnelish once and forward to every ad platform and email tool you run.
Setup
Live in under 20 minutes.
You need admin access to a Microsoft Advertising account enrolled in Microsoft’s Conversions API pilot, with msclkid tracking enabled on your campaigns.
Upstack dashboardExample
Microsoft Advertising Destination Healthy
Read the full Microsoft Ads setup guide → -
01
Add the Upstack Pixel to each funnel
In Funnelish, add the Upstack Pixel snippet to each funnel as a tracking code placed with Append To Page Head. If the funnel links to Shopify, add the script that keeps click IDs and UTMs on the link.
-
02
Add the Microsoft Ads destination
Under Destinations, add Microsoft Advertising with your numeric UET Tag ID and a CAPI Auth Token generated in your UET Tag settings. The token option appears only once your account is enrolled in Microsoft’s Conversions API pilot.
-
03
Check UET Tag Status
Upstack marks the destination Healthy, and server-side events appear alongside browser events under Tools, UET Tags, Tag Status in Microsoft Advertising. Test with a real ad click and purchase: Microsoft may take a little longer to show it in its own reporting.
FAQ
Questions about Funnelish and Microsoft Ads.
What is the difference between the UET Tag ID and the CAPI Auth Token?
The UET Tag ID identifies your Microsoft Advertising tracking tag, the same ID used for browser-side tracking. The CAPI Auth Token is a Bearer token that authorizes server-side event submission. You need both.
How do I enroll in the CAPI pilot program?
Contact your Microsoft Advertising account manager or Microsoft Advertising support to request enrollment in the Conversions API pilot. Once enrolled, the auth token option becomes available in your UET Tag settings.
Which events does Microsoft Ads receive?
PageView as pageLoad, ViewContent as view_item, AddToCart as add_to_cart, InitiateCheckout as begin_checkout and Purchase as purchase.
Which customer parameters are sent to Microsoft Ads?
Every event carries hashed email and phone, the msclkid click ID, IP address and user agent; Microsoft does not support address-level matching. Personal data is hashed with SHA-256 before it leaves Upstack.
How do I check that Funnelish events are reaching Microsoft Ads?
Upstack marks the destination Healthy, and server-side events appear alongside browser events under Tools, UET Tags, Tag Status in Microsoft Advertising. Test with a real ad click and purchase: Microsoft may take a little longer to show it in its own reporting.
How long does it take to connect Funnelish to Microsoft Ads?
Most brands are live in under 20 minutes. Once Funnelish events reach Upstack, every destination receives the same resolved events, Microsoft Ads included.