Microsoft Advertising has published documentation for a new Conversions API, giving advertisers a server-side route for sending conversion data directly to the platform. The feature is currently described as a beta, so it is not a reason for every business to rebuild its tracking tomorrow. It is, however, a useful sign of where advertising measurement is heading.
For businesses in Bath and across the South West, the practical question is not whether server-side tracking sounds more advanced. It is whether better first-party conversion data could make campaign reporting and optimisation more dependable, especially when browser-based tracking misses part of the customer journey.
What Microsoft has introduced
According to Search Engine Land’s report on the documentation, Microsoft’s beta Conversions API lets an advertiser send conversion events from its own server to Microsoft Advertising. This creates an additional route alongside the Universal Event Tracking tag that normally runs in a visitor’s browser.
The basic idea is straightforward. A browser tag records an action on a website, such as a completed purchase or enquiry. A server-side connection can send an event from a business system after that action has been confirmed. That might be an online order, a qualified lead or another outcome the advertiser has defined and can measure accurately.
This does not make browser tracking obsolete. In many setups, the two methods can work together. Microsoft says event identifiers can be used to prevent the same conversion being counted twice when it arrives through both routes. Getting that deduplication right is essential: two data pipes should improve resilience, not double the reported results.
Why advertisers are looking at server-side data
Browser-based measurement has become less complete as browsers, devices and users apply stronger privacy controls. Tags can also fail because of consent choices, technical errors or a customer moving between online and offline steps. A server-to-server connection may recover some legitimately collected events and reduce dependence on a single browser session.
That can matter for local businesses with longer or messier sales journeys. A visitor may click an advert, submit a form and only become a genuine customer after a phone call or appointment. Sending every form submission back as a success can teach an advertising platform to find more low-quality enquiries. Sending a later, properly qualified outcome can provide a more useful signal.
The same principle applies to ecommerce. A server can confirm that an order was completed and not merely that a browser reached a thank-you page. But the quality of the result still depends on the quality of the underlying data. An API cannot fix vague conversion definitions, inconsistent customer records or a checkout that records the wrong value.
This is a measurement project, not just a tag
Implementing a Conversions API usually needs more thought than copying a tracking code into a website. The business needs to decide which events are useful, where the reliable record of each event lives and how identifiers will be generated and retained. Developers, marketers and whoever owns the customer relationship management or ecommerce system may all need to be involved.
Consent and privacy remain central. Server-side does not mean permission-free or invisible. A business still needs a lawful, transparent approach to collecting and using customer data, and should send only the information that the platform requires and that its own policies support. Any implementation should be reviewed against the organisation’s consent process and data responsibilities.
Microsoft’s documentation also deserves careful reading while the product is in beta. Availability, supported event fields and recommended setup may change. Businesses using an agency, tag-management provider or ecommerce integration should ask whether native support is planned before commissioning custom development.
What Bath and South West advertisers should check
- Review the conversions used for bidding. Confirm that each one represents a meaningful business outcome rather than a page view or unqualified action.
- Map where reliable data lives. Identify whether the definitive record is in the website, booking platform, ecommerce system or customer relationship management system.
- Audit existing Microsoft tracking. Check that Universal Event Tracking is firing correctly before adding another layer.
- Plan deduplication. If browser and server events describe the same outcome, they need a consistent event identifier so that one sale or lead is counted once.
- Check consent and governance. Document what is sent, why it is needed, how it is secured and who is responsible for the connection.
- Test before using the data for bidding. Compare API events with the business’s own confirmed totals and investigate gaps or inflated counts.
These checks are part of a broader search marketing measurement setup. The value comes from joining advertising activity to real outcomes, not from adopting a technical feature for its own sake.
Who should act now?
Businesses already spending materially on Microsoft Ads, particularly those with ecommerce transactions or a well-managed lead system, may have a good reason to investigate the beta. Those with small campaigns and simple journeys can monitor it while first fixing basic conversion tracking and lead-quality feedback.
A sensible pilot would use one clearly defined conversion, reconcile the events against internal records and keep the existing tracking in place while accuracy is assessed. Campaign decisions should not be based on the new feed until the figures are stable and deduplication has been proven.
Microsoft’s Conversions API is a potentially useful addition, but it is not a shortcut to perfect attribution. For local advertisers, the immediate opportunity is to review whether the platform is receiving the outcomes that actually matter. A clean measurement plan will make any future server-side implementation far more valuable.
