What we observed in Microsoft Ads target performance
We run Microsoft Advertising accounts, and one pattern has stood out in some of them: a budget-capped campaign set to a target ROAS delivered above that target during the period reviewed.
We do not have Microsoft's auction internals and this observation does not establish a platform rule. Microsoft describes target ROAS as aiming for an average return, with individual conversions above and below the target. Auction depth or delivery pressure could be part of the account result, but that is a hypothesis, not a fact we can infer from the interface.
What that changes
It changes what we test, not what we claim. We do not import a Google target and assume it has the same effect. We set Microsoft Advertising around the client's objective, watch actual spend and return, and change the control when the account evidence warrants it.
The other useful difference is LinkedIn profile data. Microsoft Advertising lets eligible advertisers adjust bids by company, industry and job function. For Search campaigns this is bid-only, so it changes the bid for matching profiles without limiting delivery to them. It is a B2B signal, not a guarantee that a particular searcher works for the selected company.
How we run it
Build for Microsoft's auction rather than stopping at an import. Capture MSCLKID where available and upload eligible offline outcomes under Microsoft's requirements. If the account receives an eligible promotional offer, treat it only as a contribution to the test. Report Microsoft and Google outcomes in the same warehouse so they are compared on the same commercial definition.
Audience assumptions are a reason to test, not a conclusion. Qualified outcomes and unit economics decide whether the channel stays.