Skip to main content
Metrics type: Key Metrics • Category: Ad Platform

​
At a glance

Real-time alert that fires when Microsoft Advertising ROAS falls sharply against its own recent baseline. This is the first number to ping when the “Microsoft is our cheap hedge against Google” narrative is about to look bad in Monday’s report. It compares current ROAS to the prior 7-day, same-day-of-week window so that a normal weekday-to-weekend swing does not trigger a false alarm. A meaningful drop here means revenue per pound is collapsing faster than spend, and the cause is usually tracking, network drift, or a bidding learning phase rather than a real demand change.

​
Calculation

Calculated automatically from your Microsoft Ads (Bing) data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

A UK home-and-garden retailer using Microsoft Ads as the cheaper incremental layer alongside Google. The alert evaluates on the morning of 14 May 26, a Thursday. ROAS has fallen from a stable 5.0x baseline to 3.0x, a drop of roughly 40% on flat spend. The alert fires. What to read into it:
  1. Spend is flat, so this is not a scaling problem. When ROAS drops because you pushed budget into less efficient inventory, spend rises alongside. Here spend held, so the revenue side broke. That points at tracking or attribution, not media buying.
  2. Check the tracking canary first. Open Clicks vs Conversions. If clicks held but conversions cratered, the UET tag broke and the UET Tag Tracking Broken alert should also be lit.
  3. Then check network drift. Microsoft Audience Network is on by default and can find cheap low-quality inventory overnight. Segment by network; if Audience Network share jumped, that is your ROAS leak and Wasted-Spend Burst (Audience Network drift) will confirm it.
  4. Rule out a learning phase. If a campaign was restructured in the last week (new conversion goal, audience swap), Smart Bidding re-enters a 7 to 14 day learning phase where ROAS is unstable. That is a wait, not a fix.
Quick triage shape:
  • ROAS down + spend flat + clicks flat + conversions down = tracking failure (highest priority).
  • ROAS down + spend flat + Audience Network share up = network drift.
  • ROAS down + spend up = you scaled past the efficient frontier; this alert is doing its job.
  • ROAS down + recent campaign edit = learning phase; hold and recheck in a few days.
The point of the same-day-of-week baseline is that a 3.0x reading on a Saturday might be entirely normal, while the same 3.0x on a Thursday against a 5.0x norm is a genuine event worth a Monday explanation.

​
Sibling cards merchants should reference together

​
Reconciling against Microsoft Advertising

Where to look in Microsoft Advertising: Microsoft Advertising → Reports → Performance → Account Summary, with both Spend and Revenue columns visible, segmented by day. Compare today’s ROAS to the same weekday last week. The drop should match what this alert reports to within a couple of percent. Other Microsoft Advertising views that look related but differ:
  • Smart Goals ROAS uses Microsoft’s modelled values rather than UET-measured. This alert uses primary UET-measured, so the absolute ROAS may differ even when the drop direction agrees.
  • Conversion rate alerts in the Microsoft UI track a different metric; a ROAS drop can happen with stable conversion rate if average order value fell.
Why our number may legitimately differ from the Microsoft UI (rare): Cross-connector reconciliation:

​
Known limitations / merchant FAQs

The alert fired but my Shopify orders look normal. What happened? That pattern almost always means the UET tag stopped firing or started under-counting, so Microsoft sees fewer conversions than really happened. Real sales are fine; the measurement broke. Check UET Tag Tracking Broken and run UET diagnostics in the Microsoft UI before touching any bids. Why use a same-day-of-week baseline instead of vs yesterday? Because Bing demand has a strong weekly shape. Desktop-heavy, work-hours-heavy audiences mean weekday ROAS and weekend ROAS differ structurally. A “vs yesterday” check would fire every Saturday and miss real weekday breaks. Matching the day of week removes that noise. My spend is small. Will this alert over-fire on noisy days? The alert threshold is tuned per account, and low-spend days are inherently noisy because one or two outlier orders swing ROAS heavily. On accounts under a few hundred pounds of daily Microsoft spend, treat a single-day trigger as a prompt to look, not a reason to restructure. The multi-day ROAS Trend is the more reliable read at low spend. The drop was caused by a campaign I just rebuilt. Is the alert wrong? No, it is correctly reporting the dip. A restructure puts Smart Bidding back into a learning phase where ROAS is genuinely unstable for one to two weeks. The alert is telling you efficiency fell; the right response is to hold and let the algorithm relearn rather than panic-edit. Can a rising average order value hide a ROAS drop? It can soften one. ROAS is revenue over spend, so if conversion volume fell but the surviving orders were larger, ROAS may hold even as the funnel weakens. Pair this alert with Clicks vs Conversions to see the volume side directly. Does brand search distort this alert? It can. Brand campaigns carry very high ROAS, so if a brand campaign pauses or loses budget, blended ROAS can drop sharply even though non-brand performance is unchanged. When the alert fires, open ROAS by Campaign to separate brand from non-brand before drawing conclusions.

​
Tracked live in Vortex IQ Nerve Centre

ROAS Dropped Below Threshold is one of hundreds of KPI pulses Vortex IQ tracks across Microsoft Ads (Bing) and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.