Microsoft Advertising Releases Conversions API Documentation

Microsoft Advertising has published new documentation for its Conversions API (CAPI), a server-side measurement solution that is currently in beta. This new offering allows advertisers to send conversion and customer interaction data directly from their own systems to Microsoft Advertising through a single, unified connection. The Conversions API is designed to support a variety of measurement scenarios, including both online and offline events, aiming to enhance the accuracy of conversion measurement and increase attribution coverage for advertisers.

According to Microsoft, the CAPI facilitates the sending of both online and offline conversion events, thereby reducing the reliance on browser-only tracking methods that have become increasingly limited. The API supports multiple measurement use cases through a single server-side integration, providing advertisers with a more robust and comprehensive approach to tracking customer journeys. Microsoft recommends using CAPI in conjunction with its Universal Event Tracking (UET) system, rather than as a complete replacement. UET continues to capture user activity within the browser, while CAPI establishes a server-to-server connection for transmitting event data directly to Microsoft Advertising. The combined use of both UET and CAPI can offer advertisers more complete measurement coverage, particularly in situations where browser signals may be unavailable or restricted.

The introduction of CAPI provides Microsoft advertisers with an additional method to preserve conversion signals and effectively connect online advertising efforts with actions that occur outside the browser environment, such as offline purchases or interactions. For advertisers who are already investing in server-side measurement solutions across other advertising platforms, Microsoft's CAPI could streamline the process of building a more consistent and unified measurement strategy across various channels. This move aligns with broader industry trends towards server-side tracking as a means to improve data accuracy and privacy compliance in digital advertising.

However, it is important to note that the Conversions API is still in its beta phase and is not yet accessible to all Microsoft Advertising accounts. The implementation of CAPI also requires advertisers to possess the necessary technical resources to establish and maintain a server-side integration. This makes the setup process more involved compared to the simpler installation of a browser tag. Advertisers will need to allocate resources for development and ongoing management of the server-side connection to leverage the full capabilities of the Conversions API.