A New Chapter in Microsoft Ads Conversion Measurement
Microsoft Advertising's Conversions API (CAPI) is now publicly accessible, opening the door to broader server-side conversion tracking for advertisers in 2026.
The public rollout, reported in October 2026, expands access beyond the earlier restricted pilot. Advertisers can use authorized server-to-server event delivery to connect website activity, purchases, CRM milestones and eligible offline outcomes with Microsoft Advertising.
For brands, agencies and marketing teams, this matters because browser-only tracking does not always capture the complete customer journey. Server-side measurement offers an additional way to transmit eligible conversion signals while maintaining control over how event data is collected and processed.
Key takeaway: Microsoft Advertising CAPI complements Universal Event Tracking (UET). It does not eliminate the need for correct attribution, event deduplication, privacy compliance or ongoing data validation.
Quick answer: Microsoft Advertising Conversions API (CAPI) is a server-to-server interface that lets advertisers send eligible conversion events directly to Microsoft Advertising. Its October 2026 public availability expands access beyond the earlier pilot. It complements UET browser tracking and supports website, purchase, CRM and offline event measurement when correctly configured.
Primary technical reference: Microsoft Learn — Conversions API Integration Guide.
What Is Microsoft Advertising Conversions API?
Microsoft Advertising CAPI is a server-side event tracking interface that enables advertisers to transmit conversion events from their own servers, applications or supported integrations to Microsoft Advertising.
Traditional UET tracking generally relies on JavaScript running in the visitor's browser. CAPI can transmit relevant events directly from backend infrastructure, reducing dependence on the browser as the sole event delivery mechanism.
Browser signals and authenticated server events converge in Microsoft Advertising, with event IDs used to avoid duplicate measurement.
Page context, browser interactions and eligible identifiers
UET JavaScriptPurchase, CRM, qualified lead and offline business events
Secure API deliveryTypical events include purchases, lead submissions, qualified leads, CRM updates and offline sales. Actual availability and conversion attribution depend on the configured goals, supported event schema and matching identifiers.
Why Microsoft Advertising CAPI Matters in 2026
Browser tracking is increasingly constrained
Cookie restrictions, privacy settings, ad blockers and technical limitations can affect browser-delivered advertising events. CAPI provides a complementary transmission channel, although it cannot automatically recover missing identifiers or bypass user consent.
Customer journeys extend beyond websites
A B2B lead may submit a form, attend a demo, become sales-qualified and close weeks later. Connecting eligible downstream CRM events can help advertisers evaluate outcomes beyond initial lead volume.
Optimization needs reliable signals
Automated bidding and reporting rely on meaningful conversion data. Accurate events can improve decision-making, but CAPI alone does not guarantee higher conversion rates, lower acquisition costs or better ROAS.
Six Key Benefits of Microsoft Advertising CAPI
More Resilient Measurement
Reduce reliance on browser-only delivery for eligible conversion events.
CRM & Offline Events
Connect qualified leads, sales milestones and downstream business outcomes.
Ecommerce Visibility
Send purchase events, transaction identifiers, currency and order values.
Data Flow Control
Manage event transmission through your own server-side infrastructure.
Optimization Signals
Supply more complete and accurately configured signals for reporting and bidding.
Connected Measurement
Support a consistent event architecture across websites, applications and CRM systems.
Microsoft Advertising CAPI vs. UET
These technologies serve different but complementary roles in conversion tracking.
| Capability | Universal Event Tracking | Conversions API |
|---|---|---|
| Delivery method | Browser-side | Server-to-server |
| JavaScript dependency | Generally required | Not required for server delivery |
| Typical data source | Website and browser | Backend, CRM, application |
| Browser restrictions | Directly affected | Less dependent on browser delivery |
| Offline outcomes | Separate mechanisms may be needed | Eligible CRM/offline events supported |
| Integration | UET tag | API or supported partner |
| Best practice | Use alongside CAPI | Use alongside UET |
What Changed With the Public Rollout?
The October 2026 rollout removed a major access barrier associated with the earlier account-restricted pilot. Publicly documented integration routes include direct API connections, compatible partners and server-side tag management.
- Broader access: Advertisers can pursue CAPI implementation without the former pilot-only enrollment process.
- Authorization: Token-based authentication supports server event delivery.
- Integration flexibility: Direct backend and supported partner implementations can fit different technical environments.
- More business events: Website, purchase, CRM and offline outcomes can contribute to conversion measurement.
Account availability and product details should always be verified against the latest Microsoft Advertising documentation.
How server-side conversion tracking works
A practical four-stage workflow from customer action to advertising measurement.
A visitor clicks an ad, submits a lead form or completes a purchase.
Your website, app or CRM records a permitted event and relevant identifiers.
Your backend or server-side GTM sends the event to Microsoft CAPI.
Microsoft processes eligible signals for matching, reporting and optimization.
Illustrative architecture. Attribution and matching depend on event quality, consent, identifiers and Microsoft Advertising configuration.
How to Set Up Microsoft Advertising CAPI
A reliable implementation starts with conversion strategy and ends with validated reporting—not merely an API request.
Configure UET and Conversion Goals
Identify the correct UET tag and ensure the relevant conversion goals are configured in Microsoft Advertising.
Obtain Your Authorization Token
Use the supported Microsoft Advertising interface or API workflow to generate and securely store the CAPI token.
Choose an Integration Method
Select direct API integration, server-side Google Tag Manager or a compatible partner solution based on your stack.
Define the Event Taxonomy
Map purchases, leads, qualified opportunities and other eligible events to the intended conversion goals.
Capture Eligible Identifiers
Preserve Microsoft Click IDs and other supported identifiers where available and legally permitted.
Send and Validate Events
Transmit schema-compliant requests, inspect responses, test goal matching and monitor data quality.
Deduplicate and Reconcile
Use shared event identifiers for the same browser and server conversion, then compare reporting with internal records.
Documented API endpoint
This is an endpoint illustration, not a complete production request. Refer to Microsoft's latest integration guide for the accepted event schema, validation requirements and authentication workflow.
Technical Requirements That Determine Tracking Quality
| Element | Purpose |
|---|---|
| UET Tag ID | Associates events with the correct tracking configuration. |
| Authorization token | Authenticates event requests. |
| Event name | Maps an event to the configured conversion goal. |
| Event ID | Supports deduplication across browser and server events. |
| Event time | Records the actual occurrence time in the supported format. |
| MSCLKID | Supports matching conversions to Microsoft Ads clicks. |
| Eligible user identifiers | Can help matching when collected and processed appropriately. |
| Consent information | Helps communicate permitted advertising data use. |
Event deduplication
If the same purchase is sent through UET and CAPI, use consistent tag, event name and event ID values so the platform can identify it as one conversion rather than two independent outcomes.
Microsoft Click ID (MSCLKID)
Where available and permitted, capture the click ID from landing page URLs and connect it to subsequent business events. This can support attribution between advertising interactions and conversion outcomes.
Identity synchronization
Microsoft documents client-side ID Sync to connect advertiser-managed identifiers with Microsoft identifiers. Server-side event delivery does not automatically replace every browser-side identity or context mechanism.
Microsoft Advertising CAPI for Ecommerce
Ecommerce businesses can use eligible server-side events to communicate meaningful transaction outcomes from their order processing systems.
These are illustrative commerce milestones. Event names, supported parameters and conversion goal configuration must follow Microsoft Advertising's current requirements.
From the first click to real revenue
Connect eligible CRM milestones with your Microsoft Advertising measurement strategy.
Map each milestone to appropriate goals; do not assume every event is attributable or suitable for bidding.
Track Lead Quality, Not Just Lead Quantity
For B2B advertisers, a form submission is often the beginning of the sales process rather than the final business outcome. CAPI can support eligible CRM milestones to help teams measure higher-value results.
| Sales stage | Example event | Business objective |
|---|---|---|
| Initial inquiry | Lead submitted | Lead volume |
| Marketing qualification | Marketing-qualified lead | Lead quality |
| Sales acceptance | Sales-qualified lead | Sales readiness |
| Opportunity | Opportunity created | Pipeline contribution |
| Proposal | Proposal issued | Sales progression |
| Closed-won | Deal won | Revenue attribution |
CRM systems such as Salesforce, HubSpot, Microsoft Dynamics 365 and custom platforms can be sources for server-side events when supported by a suitable integration. Each stage must be mapped and tested rather than assumed to be a built-in goal.
CAPI With Server-Side Google Tag Manager
Server-side Google Tag Manager (sGTM) offers a centralized event routing architecture. Instead of relying solely on browser-to-platform delivery, eligible events can be collected by a server container and forwarded to Microsoft Advertising.
Illustrative sGTM architecture
Each destination requires its own schema, identifiers, consent handling and supported integration.
This architecture can be useful for teams managing multiple advertising and analytics platforms, but it still requires secure hosting, monitoring and technical governance.
Privacy, Consent and Data Security
Server-side tracking does not create an exemption from privacy laws or advertising platform policies. Businesses must establish an appropriate legal basis for collecting and transmitting event data.
- Collect and transmit only data needed for legitimate measurement purposes.
- Honor consent and applicable user preferences.
- Protect authorization tokens and restrict access to tracking infrastructure.
- Apply Microsoft's documented normalization and hashing rules when eligible customer identifiers are used.
- Review data retention, cross-border processing and applicable regulations.
- Document event sources, destinations and governance responsibilities.
Privacy reminder: Hashing customer information does not automatically make it anonymous or remove regulatory obligations. Consent and other legal requirements remain relevant.
Common CAPI Implementation Mistakes
| Issue | Potential consequence | Recommended fix |
|---|---|---|
| Wrong UET tag | Incorrect goal association | Verify tag and goal mapping |
| Missing event IDs | Double-counting risk | Use stable shared IDs |
| Missing click IDs | Lower attribution coverage | Capture eligible MSCLKID values |
| Invalid timestamps | Event rejection | Validate supported time format |
| Inconsistent event names | Unmatched conversion goals | Standardize event taxonomy |
| Missing consent controls | Privacy and compliance risk | Implement consent-aware delivery |
| No error monitoring | Unnoticed tracking failures | Monitor requests and responses |
How to Measure CAPI Implementation Success
Measure both the technical health of your integration and the quality of the resulting business insights.
Event Acceptance
Share of valid events successfully accepted by the API.
Match Coverage
Availability of eligible identifiers and attributable events.
Deduplication Quality
Correct treatment of the same event sent through multiple channels.
Business Outcomes
Visibility into qualified leads, purchases and revenue where attributable.
Compare performance before and after deployment while considering attribution windows, campaign changes, conversion lag and seasonality. An increase in reported conversions may reflect better measurement rather than additional sales.
The Future of Server-Side Advertising Measurement
Modern advertising measurement is evolving toward architectures that combine browser events, server-side signals, consent-aware identity matching, CRM systems and first-party business data.
The goal is not to collect more information indiscriminately. It is to capture relevant, permissioned and accurate signals that reflect meaningful customer and business outcomes.
For advertisers, the question is shifting from “Is the tracking tag installed?” to “Does our measurement system accurately represent the full customer journey?”
Microsoft Advertising CAPI FAQs
Is Microsoft Advertising CAPI publicly available?
The October 2026 public rollout expanded access beyond the earlier restricted pilot. Check your account and current Microsoft documentation for availability.
Does CAPI replace Universal Event Tracking?
No. CAPI complements UET, and Microsoft recommends using them together when appropriate.
Can CAPI send offline conversion events?
Yes. Eligible offline sales and CRM events can be transmitted through supported integrations, subject to schema and attribution requirements.
Can CAPI improve return on ad spend?
Better conversion signals may support improved optimization decisions, but ROAS improvements are not guaranteed.
Does Microsoft CAPI work with server-side Google Tag Manager?
Yes, through suitable server-side integrations and supported partner configurations.
Can CAPI integrate with Salesforce or HubSpot?
CRM systems can serve as event sources through custom integrations or suitable intermediaries, with proper mapping and validation.
What prevents duplicate conversions?
Consistent tag configuration, event naming and shared event IDs help the platform identify duplicate browser and server events.
Does server-side tracking eliminate the need for consent?
No. Applicable privacy laws, consent requirements and platform policies continue to apply.
Is Microsoft Advertising CAPI free?
Microsoft's integration guidance does not establish a separate usage charge in the referenced materials. Hosting, implementation and third-party service costs may still apply.
Make Every Conversion Count.
Build a more reliable Microsoft Advertising measurement strategy with server-side tracking, event architecture, CRM integration and conversion data validation.
Discuss Your Tracking RequirementsConclusion
Microsoft Advertising CAPI's public rollout is an important step toward more flexible conversion measurement. When paired with UET, server-side event delivery can help businesses connect advertising activity to meaningful website, ecommerce and CRM outcomes.
Success depends on thoughtful event design, accurate identifiers, secure infrastructure, deduplication, privacy compliance and continuous validation. For Microsoft Ads advertisers, this is a timely opportunity to review whether current tracking reflects the customer journey accurately.