Webclat / AI Visibility

Measuring conversions from Microsoft Copilot Checkout

Microsoft launched Copilot Checkout at NRF in January 2026 with Shopify, PayPal, and Stripe already wired in. What was less clearly documented: exactly which existing measurement tag, if any, already covers a completed Copilot Checkout transaction - and that gap is worth stating rather than papering over.

In short

As of 2026-09, we found no distinct "Copilot pixel." The most likely measurement path is Microsoft's existing Universal Event Tracking (UET) tag, the long-standing Bing Ads pixel, extended across the Bing, MSN, Edge, and Copilot surfaces Copilot Checkout runs on - plus a UET Conversions API that Microsoft documented as a limited pilot starting June 2026. Whether UET independently captures a Copilot Checkout completion without additional setup is not confirmed in the public materials we reviewed, and belongs on the runtime-verification checklist rather than the assumption list.

What Copilot Checkout actually is

Announced at NRF 2026, Copilot Checkout lets a user ask Copilot about products, compare options, and complete a purchase inside the same conversation, powered by Shopify, PayPal, and Stripe integrations. Shopify merchants were enrolled with an opt-out window rather than requiring active sign-up. Microsoft's stated design keeps merchants owning the customer relationship and the transaction data - a materially different posture from a pure marketplace checkout, and one that implies the merchant's own analytics should, in principle, still see the order.

Product data for Copilot's shopping surfaces comes from Microsoft Merchant Center (structurally similar to Google Merchant Center) plus live crawling by Bingbot and Microsoft's AI crawlers - separate from the conversion-measurement question this page covers, and closer to the visibility side we treat in our Copilot visibility guide.

The existing pixel that most likely applies: UET

Universal Event Tracking is Microsoft Advertising's site-wide conversion and remarketing tag, in place for years across Bing, MSN, and Edge. Because Copilot Checkout runs across exactly those properties, UET is the most plausible existing mechanism for catching a Copilot-originated conversion - but "most plausible" is not the same as "confirmed," and we did not find explicit public documentation stating that UET requires no additional configuration to attribute a Copilot Checkout completion specifically.

The newer piece: a UET Conversions API, in limited pilot

Microsoft documented a UET Conversions API integration guide in June 2026, explicitly noting the feature is a pilot and not available to every advertiser. Where UET captures browser-based activity and page context, the Conversions API is meant to add a server-side path for events that happen after or alongside what the browser tag sees - Microsoft's own stated recommendation is to run both together where the pilot is available, not to treat CAPI as a UET replacement.

What to actually do, given the uncertainty

  • Confirm UET is live and correctly tagged across every surface Copilot Checkout touches - this is baseline hygiene most Bing Ads accounts already have, but "already have UET" is not the same as "already verified UET on the checkout confirmation page."
  • Set an explicit checkout-confirmation conversion goal in Microsoft Advertising tied to the Copilot Checkout completion event, rather than assuming a generic purchase goal already covers it.
  • Request access to the UET Conversions API pilot if your account qualifies, and run it alongside UET per Microsoft's own guidance - not as a replacement.
  • Runtime-verify a real transaction before reporting any number upward - complete an actual Copilot Checkout purchase in a test environment and confirm it lands in Microsoft Advertising reporting. This is the same discipline our verification guide applies to every platform in this series, and it is the only way to close the gap between "should work" and "does work" here.

We are flagging an open question, not hiding one. Public materials describe UET and its emerging CAPI pilot; none we reviewed explicitly confirmed automatic Copilot Checkout coverage. Treat that connection as needing verification on your own account, not as settled fact.

Positioning, stated plainly

This is measurement engineering, not a Bing Ads optimization pitch: confirming which tag actually fires on a Copilot Checkout completion, closing the gap where it does not, and never reporting a number we have not watched happen on the wire.

Common questions

Does Copilot Checkout have its own conversion pixel?

Not confirmed as a distinct product in the sources we reviewed as of 2026-09. Microsoft's existing Universal Event Tracking (UET) tag is the established Bing Ads pixel; whether it independently captures Copilot Checkout completions, versus needing separate instrumentation, was not stated plainly in the public materials we found - flagged for runtime verification rather than assumed.

What is UET and how does it relate to Copilot?

Universal Event Tracking is Microsoft Advertising's long-standing site-wide tag for conversion goals and remarketing. Copilot Checkout runs across Bing, MSN, Edge, and Copilot itself, all properties UET already instruments - making UET the most likely existing mechanism, though its coverage of the new checkout flow specifically needs confirming, not assuming.

What is the UET Conversions API pilot?

A server-side conversions API for Microsoft Advertising, documented by Microsoft as a pilot since June 2026 and not available to every advertiser. Where available, Microsoft recommends running it alongside UET rather than as a replacement.

How do we know if our Copilot Checkout conversions are actually tracked?

Run the same runtime-verification check described in our verification guide: complete a real transaction, watch the network panel for UET's tag firing (and the CAPI call if enrolled), and confirm the conversion appears in Microsoft Advertising reporting - do not assume coverage from the product announcement alone.

Find out if your Copilot Checkout conversions are actually landing.

UET verification, CAPI pilot enrollment where eligible, and a real-transaction runtime check.

Verify My Copilot Checkout Tracking