Microsoft CAPI setup is now a front-burner priority for advertisers running Bing Ads — with Microsoft Conversions API reaching general availability in 2026, the window to get ahead of measurement gaps is open right now. This guide walks you through every step of the implementation, from UET tag configuration to server-side event deduplication, so your Microsoft Advertising account captures the conversions that browser restrictions and ad blockers would otherwise erase.
What Microsoft CAPI Setup Actually Solves
Microsoft's Conversions API — often abbreviated as MCAPI — is a server-to-server connection that sends conversion signals directly from your web server, CRM, or data warehouse to Microsoft Advertising's infrastructure, bypassing the browser entirely. Unlike the Universal Event Tracking (UET) pixel, which fires inside the visitor's browser and is vulnerable to Safari's ITP restrictions, Firefox's Enhanced Tracking Protection, and a growing constellation of ad-blocking extensions, MCAPI events originate on infrastructure you control.
The practical impact is significant. A documented retail case study found that an e-commerce client recorded 8,841 conversions with server-side cookies versus 7,466 with client-side cookies — an 18.26% increase in tracked conversions. That gap represents real bidding signal that your Microsoft Advertising smart bidding algorithms never see when you rely on pixel-only measurement.
With MCAPI reaching GA, Microsoft has standardized the event schema, hardened the deduplication logic, and published stable API versioning. Early-adopter workarounds are no longer necessary. The setup process is now deterministic and maintainable, which is precisely why this guide exists.
"Every conversion your pixel misses is a data point your automated bidding never had — and it compounds over every campaign, every month."
If you are also running Meta CAPI or Google Enhanced Conversions, the architectural patterns are similar but the implementation details diverge meaningfully. The broader conversions API implementation guide covers all three platforms side by side, which is useful for teams managing multi-channel measurement stacks.

Prerequisites Before You Begin
Rushing into a Microsoft CAPI setup without the right foundations in place creates debugging nightmares later. Verify each of the following before touching the API configuration.
- Active Microsoft Advertising account: You need an account with at least one active campaign and billing established. MCAPI is available to all account types as of the 2026 GA release.
- UET tag deployed and firing: The Conversions API is designed to complement — not replace — your UET pixel. Confirm the tag fires on purchase, lead, and any other conversion pages using the UET Tag Helper Chrome extension.
- Conversion goals configured: At least one conversion goal must exist in your Microsoft Advertising account before you can associate server-side events with it. Note the conversion goal ID — you will need it during event mapping.
- Server-side infrastructure access: You need a server, cloud function, or tag management server (such as a server-side GTM container or a CDP) capable of making HTTPS POST requests to Microsoft's API endpoint. If this is new territory, start with the foundational concepts in server-side conversion tracking before proceeding.
- First-party data signals: Hashed customer identifiers — email address, phone number, or Microsoft Click ID (MSCLKID) — dramatically improve event match quality. Confirm your site captures and stores MSCLKID in a first-party cookie or your CRM on click.
- Developer or tag manager access: Someone on your team must be able to modify server-side code or configure a server-side tag management container.
Step 1: Enable the Conversions API in Microsoft Advertising
The first action is generating your API credentials inside Microsoft Advertising's UI. This produces the authentication tokens your server will use to send events.
- Log in to Microsoft Advertising and navigate to Tools → Conversions → Conversions API.
- Click Set up Conversions API and review the data processing terms. Accept these to proceed — they govern how Microsoft handles the hashed personal data your server sends.
- Select the UET tag you want to pair with the API connection. Each CAPI connection is tied to a specific UET tag ID, which is how the platform later deduplicates browser and server events.
- Copy and securely store the generated Developer Token and your Customer ID. These are required in every API request header. Store them in your secret manager or environment variables — never in client-side code.
- Note the API endpoint URL displayed in the UI. As of the GA release, Microsoft publishes versioned endpoints (e.g.,
/v13/). Always use the current stable version to avoid deprecation issues. - If your server-side setup uses OAuth 2.0 authentication (recommended for production environments), register your application in the Microsoft Azure Active Directory and obtain a Client ID and Client Secret to generate access tokens programmatically.
Step 2: Configure Your UET Tag for Deduplication
Deduplication is the most technically critical piece of Microsoft CAPI setup. Without it, every conversion fires twice — once from the browser pixel and once from the server — and your reported numbers become meaningless inflated figures that corrupt smart bidding.
- Open your UET tag configuration in Microsoft Advertising or in Google Tag Manager (whichever manages your pixel deployment).
- Enable the event_deduplication_id parameter on every conversion event the UET tag fires. This is a unique string you generate per conversion event — a UUID or order ID works well.
- Pass the same event_deduplication_id value in the corresponding server-side event payload. Microsoft's backend uses this field to identify and discard the duplicate.
- Ensure the deduplication ID is generated at the point of conversion (server-side, ideally) and passed to both the browser tag and the server event. Generating it client-side risks the ID not reaching the server if the page crashes or the user navigates away.
- Test deduplication by intentionally firing a browser event and a server event with the same ID in your staging environment, then confirming only one conversion appears in the UET diagnostics report.
Industry practitioners consistently report that skipping deduplication setup is the single most common cause of inflated conversion counts after a CAPI launch. Budget extra QA time here.
Step 3: Map and Send Server-Side Events
With credentials in hand and deduplication logic wired up, the next step is constructing and transmitting your event payloads. Microsoft CAPI uses a JSON structure that mirrors the UET event schema with added server-only fields.
| Event Parameter | Required / Optional | Description |
|---|---|---|
| MicrosoftClickId (MSCLKID) | Strongly recommended | Auto-tagged click ID from the landing page URL; highest-fidelity match signal |
| hashed_email | Optional (improves match) | SHA-256 hashed, lowercase, trimmed email address |
| hashed_phone | Optional (improves match) | SHA-256 hashed phone in E.164 format |
| event_action | Required | Maps to your conversion goal type (e.g., purchase, lead) |
| revenue_value | Required for purchase events | Numeric order value in the currency of your account |
| event_deduplication_id | Required (for dedup) | Unique ID matching the browser event; enables server/browser deduplication |
| event_time | Required | Unix timestamp of the conversion event; must be within 24 hours of sending |
- Build the JSON payload on your server using the parameters above. Always SHA-256 hash personal data before transmission — Microsoft rejects unencrypted PII.
- Send the payload via HTTPS POST to Microsoft's Conversions API endpoint, including your Developer Token in the
DeveloperTokenrequest header and your Authorization Bearer token. - Handle API responses: a
201 Createdresponse confirms acceptance. Log any400or422errors with the full response body — Microsoft's error messages are specific enough to pinpoint malformed fields. - For high-volume e-commerce, batch events where the API permits it rather than sending individual requests per conversion. This reduces latency and server-to-API connection overhead.
- If you are using a server-side GTM container, Microsoft's official MCAPI tag template (available in the Community Template Gallery) handles payload construction and hashing automatically once you configure the trigger and variable mappings.
Step 4: Validate Events and Monitor Match Quality
Sending events is only half the job. Verifying that Microsoft receives them correctly and that they match to real ad clicks is what determines whether the data actually improves your bidding.
- Navigate to Tools → UET Tag → Diagnostics in Microsoft Advertising. Within 24–48 hours of going live, you should see server-side events appearing alongside browser events in the conversion activity log.
- Check the Event Match Quality score, which Microsoft surfaces as a percentage. A score above 70% is considered healthy. Scores below 50% indicate that your match signals (MSCLKID, hashed email) are missing or malformed on a significant portion of events.
- Audit MSCLKID capture rates. If fewer than 80% of your server-side purchase events carry an MSCLKID, revisit your landing page logic — the click ID must be stored in a first-party cookie on arrival and then retrieved and attached to the order record at conversion time.
- Monitor the duplicate rate in diagnostics. A rate above 5% suggests deduplication IDs are not being passed consistently from the browser tag. Trace back through your tag firing sequence.
- Set up a weekly review cadence for the first month post-launch. API schema versions can introduce breaking changes on Microsoft's platform updates, and the GA release includes a commitment to changelog notifications — subscribe to these in your Microsoft Advertising notification settings.
Common Mistakes to Avoid
Most Microsoft CAPI implementations that fail do so for predictable reasons. These are the patterns that appear repeatedly in post-mortems.
- Skipping deduplication entirely: Some teams send server events and leave the UET pixel running without any deduplication ID. The result is double-counted conversions that mislead smart bidding and make performance reporting useless within weeks.
- Sending events outside the 24-hour window: Microsoft requires that the
event_timetimestamp in your payload falls within 24 hours of the API call. Delayed batch jobs that process orders from the previous day will have events rejected silently. - Hashing email addresses inconsistently: The SHA-256 hash must be applied to a lowercase, whitespace-trimmed email string. Hashing "User@Example.com" instead of "user@example.com" produces a different hash and a failed match. Standardize this in a shared utility function.
- Confusing UET tag IDs across environments: Staging and production UET tags must be separate. Sending production server events to a staging UET tag ID — or vice versa — either pollutes your live data or leaves production with no server signal at all.
- Treating MCAPI as a pixel replacement: The Conversions API is designed to work alongside UET, not replace it. Browser-side events still capture signals CAPI cannot — user agent, viewport data, and page-level engagement. Run both in parallel.
- Ignoring API version deprecation notices: Microsoft follows a deprecation schedule for older API versions. Running on an end-of-life version means events stop processing with no UI warning. Pin your implementation to a specific version and monitor Microsoft's deprecation timeline actively.
Expected Results and Timeline
After a correctly implemented Microsoft CAPI setup, the trajectory of improvements follows a consistent pattern across different account types and verticals.
- Days 1–3: Events begin appearing in UET diagnostics. Expect a small volume gap during the initial data propagation period — this is normal and resolves as Microsoft's attribution engine processes the new signal source.
- Days 3–7: Event Match Quality scores stabilize. This is the right moment to evaluate whether MSCLKID capture needs improvement or whether hashed email coverage is adequate for your traffic mix.
- Weeks 2–4: Conversion volume in Microsoft Advertising typically increases as previously unmeasured conversions are now attributed. Many practitioners report a 10–20% uplift in tracked conversions, though this figure varies significantly depending on how much traffic previously came from browsers with aggressive cookie restrictions.
- Month 2 onward: Smart bidding algorithms accumulate the richer signal. Cost-per-acquisition metrics typically improve once the bidding model has had four to six weeks of CAPI-augmented data. The improvement compounds over time — this is why early implementation matters.
- Ongoing: Schedule quarterly audits of deduplication rates, match quality scores, and API version status. A CAPI implementation is not a set-and-forget deployment; it requires the same maintenance discipline as any data pipeline.
For teams running server-side measurement across multiple ad platforms simultaneously, the operational overhead is manageable when infrastructure is shared. A single server-side GTM container or CDP event stream can fan out to Microsoft, Meta, and Google endpoints from the same conversion event, keeping your engineering footprint lean.
Frequently Asked Questions
What is Microsoft CAPI and how is it different from the UET pixel?
Microsoft CAPI (Conversions API) is a server-to-server connection that sends conversion data directly from your server to Microsoft Advertising's infrastructure, bypassing the visitor's browser. The UET pixel fires inside the browser and is subject to cookie restrictions, ad blockers, and browser privacy protections. MCAPI complements the pixel by capturing conversions the browser tag misses — the two are designed to run in parallel with deduplication logic preventing double-counting.
Do I need to remove my UET pixel when I set up Microsoft CAPI?
No — removing the UET pixel would be a mistake. The Conversions API is explicitly designed to supplement browser-side tracking, not replace it. Your UET tag still captures valuable client-side signals and serves as the deduplication partner for server events. Keep both running and configure event deduplication IDs to prevent double-counting.
How does Microsoft CAPI deduplication work?
Deduplication works by passing an identical event_deduplication_id parameter in both the browser-fired UET event and the server-sent CAPI event for the same conversion. Microsoft's backend identifies matching IDs and counts the conversion only once. The deduplication ID should be a unique string per conversion — an order ID or UUID — generated at the time of the transaction.
What customer data does Microsoft CAPI require, and how should it be hashed?
Microsoft CAPI accepts hashed email addresses and phone numbers as match signals, along with the MSCLKID (Microsoft Click ID) which requires no hashing. All personal data must be hashed using SHA-256 before transmission. Email addresses must be converted to lowercase and stripped of leading/trailing whitespace before hashing. Phone numbers should be in E.164 international format before hashing.
How long does it take for Microsoft CAPI events to appear in my account?
Server-side events typically appear in UET diagnostics within 24–48 hours of your first successful API call. Conversion reporting in the Campaigns interface may take up to 72 hours to fully reflect the new data source due to attribution processing latency. Event Match Quality scores generally stabilize within the first week of consistent event sending.
Can I use server-side GTM to implement Microsoft CAPI without custom code?
Yes. Microsoft's official CAPI tag template is available in the server-side GTM Community Template Gallery and handles payload construction, SHA-256 hashing, and API authentication once configured with your credentials and variable mappings. This is the recommended path for teams without dedicated backend engineering resources. You will still need a server-side GTM container hosted on a subdomain of your own domain to get the full first-party data benefit.
