Microsoft's Conversions API is live: server-side tracking for Bing and Copilot ads
By Alan Magliocca · Published November 2026
Quick answer: On October 28, 2026, Microsoft Advertising made its Conversions API (CAPI) generally available, a server-to-server connection that sends conversions from a website, CRM, app or point of sale alongside the UET tag. For clients advertising on Bing, Copilot and Microsoft's other placements, start with one high-value event such as a qualified lead, send it through a tag manager or a partner, and use a shared event ID so nothing is counted twice.
Key takeaways
- Microsoft's Conversions API became generally available on October 28, 2026.
- It sends conversion data server to server and works alongside the Universal Event Tracking (UET) tag, not instead of it.
- You can connect directly, through Google Tag Manager or through partners such as Segment, Tealium, Stape and HubSpot.
- Use the same event ID, event name and UET tag in both UET and CAPI so Microsoft doesn't count a conversion twice.
- Events must be sent within 90 days, and emails and phone numbers must be normalized and SHA-256 hashed.
What happened
On October 28, 2026, Microsoft Advertising announced in its October product update that its Conversions API (CAPI) is generally available.
According to Microsoft:
- What it is: a server-to-server connection that sends conversion data from a website, apps, a CRM and point-of-sale systems to Microsoft Advertising in real time.
- Why it helps: richer signals for AI-powered bidding, more complete conversion data, and more control over what data is shared.
- How it fits with UET: CAPI works alongside the Universal Event Tracking tag. It covers extra touchpoints and catches activity that browser limits can miss.
- Ways to connect: directly, through Google Tag Manager, or through partners. The post names Adobe Real-Time CDP, Commanders Act, Freshpaint, Invoca, MetaRouter, Segment by Twilio, Stape.io, Switch Growth, Tealium and Zeotap.
- Use cases: higher-quality leads, in-store sales, app engagement and dynamic remarketing.
Microsoft's CAPI developer guide also lists HubSpot among current partner integrations, alongside most of the names above.
Microsoft Advertising ads run on Bing, Copilot, Outlook and other Microsoft properties, so this is the server-side option for all of them.
What it means for agency owners
Browser tags miss conversions. Ad blockers, privacy settings and people who convert later by phone or in person all leave gaps. For a lead-gen client, the most valuable event, a qualified lead or a signed job, usually happens in the CRM days after the click, where no browser tag can see it.
CAPI lets you send that later event back to Microsoft. That gives bidding a better signal than "form filled," and it lets you show a client which Microsoft campaigns produced paying customers.
It also matters more now that Microsoft is pushing AI-run campaigns. Performance Max and AI Max both learn from conversions, as we covered in Microsoft Performance Max now shows search terms. Better data in means better decisions out.
What to do this week
- Confirm the basics in each client's Microsoft account: a working UET tag, defined conversion goals and auto-tagging on so the Microsoft click ID (msclkid) is added to landing page URLs.
- Pick one event to send first. For lead-gen, a qualified lead or booked job. For e-commerce, purchases with value.
- Choose a setup path using the comparison below.
- Get the token. In Microsoft Advertising, edit the UET tag, choose "Use Conversions API" and copy the token. Treat it like a password.
- Set up deduplication before you go live: the same event ID, event name and UET tag in both the browser tag and CAPI.
- Agree consent handling with the client. CAPI treats events as consent granted by default unless you send a denied signal. Check with a lawyer what the client's privacy notice and local law require.
How AIVX Labs helps
AIVX Labs doesn't send conversion data to Microsoft, so this setup happens in the client's tag manager, CRM or partner tool. Once the data is flowing, the monthly client report is where you show the client what changed. Tell RICO "monthly report for a roofing client" and it builds the report in that client's workspace, showing the credit cost before you click Go.
Which setup path fits a small client?
Microsoft's guide describes three paths:
- Partner integration. Best when the client already uses one of the listed tools. If the client's CRM is HubSpot, start with HubSpot's Microsoft Advertising conversion sync. Least custom work.
- Tag manager, including server-side Google Tag Manager. Best for web-focused clients who want a faster setup with little development. You configure triggers, event names and identifiers in the tag manager.
- Direct API. Best when a developer can build and maintain it, or when events come from a custom system. Events go to Microsoft's CAPI endpoint for the client's UET tag, singly or in batches of up to 1,000.
For most small local clients, a partner or tag manager is enough. Save the direct API for clients with their own developers.
What are the technical rules you can't skip?
From Microsoft's developer guide:
- Every event needs at least one identifier, such as the click ID, a hashed email, a hashed phone number or an anonymous visitor ID.
- Store the click ID. Capture msclkid from the landing page URL, keep the most recent one for each visitor (Microsoft suggests 90 days) and send it with later events.
- Hash emails and phone numbers with SHA-256 after normalizing them. Emails are trimmed and lowercased with dots and aliases removed from the name part, and phone numbers go into international E.164 format first.
- Send events within 90 days. Older timestamps are rejected, and the event still has to fall inside the conversion goal's attribution window.
- Use stable event IDs so retries and the browser tag don't create duplicates.
- Correct mistakes with restate and retract, which work when the event carries a transaction ID.
A worked example: an HVAC company's qualified leads
Picture an HVAC client running Microsoft Search ads. The website form fires UET when someone submits it, but only about half the submissions turn into booked visits, and the client's office staff mark those in the CRM.
The setup:
- The landing page stores msclkid with the lead record when the form is submitted.
- When staff mark a lead "visit booked," the CRM or partner tool sends a CAPI event named, say, "qualified_lead," with the stored click ID, a hashed email and phone, and a transaction ID.
- In Microsoft Advertising, "qualified_lead" becomes the primary conversion goal, and the raw form fill becomes secondary.
Now bidding aims at booked visits, not every form. The same pattern works for webinar sign-ups that become attendees; BrightStage's page on analytics tracking covers that side.
Google has a parallel push on first-party data, covered in Data Manager API and Data Strength Uplift. Selling one setup across both platforms is an easy upsell to explain.
Sources
Related
Written by Alan Magliocca, founder of AIVX Labs and BrightStage AI (Podavinci LLC). Written with AI assistance and checked against the linked sources.
Read our featured article on LinkedIn
Get AIVX Labs verified for $1: RICO, your AI operator, with 7 days of full access.
Get AIVX Labs Verified for $1Follow along:LinkedInYouTubeTikTokXFacebookInstagramSkool community
Frequently asked questions
Does CAPI replace the UET tag?
No. Microsoft recommends using CAPI with UET whenever possible. UET captures browser activity and page context, and CAPI adds events the browser can't see.
How do I stop a conversion being counted twice?
Send the same event ID and a matching event name from both UET and CAPI, using the same UET tag. Microsoft uses the shared event ID to recognize the duplicate.
Can I send offline sales and CRM stages?
Yes. Microsoft's guide says CAPI handles website, CRM, offline and app events through one setup, as long as each event is sent within 90 days and carries at least one identifier.
