Step-by-step guide on Microsoft Conversion API integration

Microsoft (Bing) has released its Conversion API into closed Beta. For marketers, it means that Microsoft Ads server-side tracking configuration  is available for this platform. Before, the only available option for Microsoft Ads was Microsoft's offline conversion tracking. The tracking method has many disadvantages if used for reporting online conversions, so switching to server-side using this option was not the most effective solution.

In this article, we will explain how Microsoft Conversion API works and how to configure server-side tracking for this platform using Stape's Microsoft Ads UET Conversion API tag.

Using the Conversion API allows you to send a server-to-server signal. Microsoft CAPI can transmit the same events as Microsoft JavaScript (Microsoft's UET tag), but from your cloud server instead of directly through the browser. By using this server-to-server setup, you can benefit from all the advantages of server-side tracking, including greater accuracy and reliability of conversion tracking, even in scenarios where cookies are limited or restricted.

CAPI configuration requires setting up Microsoft’s UET tag. To avoid duplicated events, CAPI also supports event deduplication, allowing you to include identifiers such as a hashed email or phone number. This helps Microsoft connect actions to specific users, resulting in more accurate tracking and better ad targeting later.

To simplify the process of Microsoft CAPI integration, the Stape team has developed the Microsoft Ads UET Conversion API tag.

To set up the Microsoft Conversion API, you will need the following:

1. Add Microsoft Ads Conversion API tag to your workspace. Go to your server GTM container → Templates section → Search gallery → search for "Microsoft Ads UET Conversion API by Stape" → click "Add to workspace".

2. Create a new tag.

In the "Tags "section, click "New" → as tag configuration select "Microsoft Ads UET Conversion API".

3. Configure the tag.

3.1 Select Event Type Setup Method - "Standard" setup method will manually configure events, while "Inherit from client" will automatically map from GA4/Data tag event payloads.

3.2 Add UET Tag ID - the value can be found in the Microsoft Ads account → Conversions → UET tag → Tag ID.

3.3 Authorization Token - enter the auth token generated in your Microsoft Ads account. To get the token value, follow the steps:

3.4 Enable Client-Side ID Sync - strongly recommended. This allows your internal IDs to be mapped to Microsoft IDs for better user matching and remarketing via a browser pixel.

Add Microsoft Customer ID / Manager Account ID - if you have multiple Customer IDs, please use the primary Microsoft Customer ID (the one from the Manager Account). Please note, it's not the same as the UET Tag ID.

You can find the ID by looking for the cid URL parameter when visiting your Microsoft Advertising account.

3.6 Use Optimistic Scenario - if set to true, the tag will call gtmOnSuccess() without waiting for a response from the API. This will speed up sGTM response time; however, your tag will always return the status fired successfully even in cases where it is not.

Here is an example of a field configuration:

3.7 Add at least one User Data Parameter.

User Data Parameters include standard identifiers like Anonymous ID, Click ID, Email, Phone Number, and External ID (User ID). Other identifiers like IP Address and mobile device IDs (IDFA/GAID) can also be sent.

3.8 Anonymous ID and Click ID Settings section.

The tag automatically manages both the Microsoft Click ID (msclkid) and the Anonymous ID.

In this section, you can control whether the tag writes these values to cookies, as well as configure their expiration and domain.

When using server GTM, both identifiers are stored in separate cookies with names distinct from those used by the JavaScript implementation:

3.9 Server Event Data Parameters section.

3.10 Event Parameters section.

In this section, you can specify parameters that will provide detailed information about the user’s actions.

4. Add a trigger for the tag.

5. Test the configuration. You can do it in Google Tag Manager by clicking on Preview. Then trigger the event, and check whether the tag has fired.

Find out more about debugging and monitoring server-side tracking configuration in our guide.

When you send the same conversion event through both the Microsoft UET tag and Microsoft CAPI, Microsoft Ads may receive the event twice. Without deduplication, this can result in duplicate conversions being reported and inaccurate campaign performance data.

Event deduplication allows Microsoft Ads to recognize that events received from different sources represent the same user action and count them only once. This helps keep your conversion data accurate when using both browser-side and server-side tracking.

Event deduplication can be configured via the web and server GTM tags. Follow the instructions below to configure it:

3. As the name, specify eventId as the value, and add a variable for a Unique Event ID.

4. Click “Add”.

5. Go to the server GTM container → open Stape’s tag you’ve configured, “Microsoft Ads UET Conversion API by Stape” → click on the section Server Event Data Parameter → click “Add parameter”.

6. Select Event ID as the parameter name.

7. As a parameter value, add the variable with the following settings:

Variable Type: Event Data

Key path: event_id

We have covered the topic of Microsoft Ads tracking in our other articles. The guides will be helpful for data tracking configuration:

The upcoming release of Microsoft’s Conversion API marks a significant step forward for advertisers looking to improve the accuracy of their tracking setup. By setting up Stape’s Microsoft Ads UET Conversion API tag, you can easily integrate Microsoft CAPI, reducing reliance on browser-based tracking and gaining more reliable conversion data.