Microsoft Ads and Google Ads in one pacing view: the budget rules, time zones and currencies that differ

Most B2B search programs run on both platforms with one budget approved for search. Finance sees one line; the team manages two consoles. Paced separately, each console looks fine; paced together, you can see when Microsoft is underspending while Google quietly absorbs the difference, or the reverse. For high-spend portfolios that add LinkedIn, see our guide to multi-platform budget management.

The differences are small on any one day and large over a month.

The monthly ceiling difference matters in short and long months. A Google campaign with a daily budget of plan / 31 in a 31-day month can spend up to 30.4 / 31 of plan in theory, about 2% under; in February it can spend up to 30.4 / 28 of plan, about 8.6% over. A Microsoft campaign with the same setting has a monthly limit of exactly the plan.

1. Write one monthly budget per program (for example, North America search) and split it by platform, so each campaign has a plan.
2. Pick one reporting time zone and one cut-off: compute expected spend for both platforms at the same hour.
3. Convert both to one currency at a stated rate before adding totals.
4. Map campaigns to programs the same way on both platforms, using naming or labels, so totals compare like with like.
5. Pace each platform against its own share, then show the program total underneath.
6. Review cost per conversion and, where the CRM allows, cost per opportunity by platform before moving money between them.

A North America search program has US$40,000 for a 31-day month, split US$30,000 Google Ads and US$10,000 Microsoft Advertising. Data is pulled at 6 am on day 12, so 11.25 days have elapsed. Expected spend is US$30,000 x 11.25 / 31 = US$10,887 for Google and US$3,629 for Microsoft.

Google has spent US$12,900, a pace of 118%. Microsoft has spent US$3,100, a pace of 85%. The program total is US$16,000 against US$14,516 expected, a pace of 110%, just at the edge of a 10% band. Reading the total alone, nothing looks urgent. Reading the platforms, Google needs its daily budget cut to (US$30,000 - US$12,900) / 19.75 = about US$866 and Microsoft needs about US$349 a day, plus a check of why it is behind (bids, impression share lost to rank, or a smaller audience).

Our point of view: do not refill Microsoft’s gap with Google budget, or the reverse, on pace alone. If Microsoft’s cost per opportunity is lower, defend its budget and fix delivery; if it is higher, moving money to Google may be right, but that is a pipeline decision, not a pacing one.

With one account on each platform and a handful of campaigns, a shared spreadsheet that pulls both spends once a day is enough. Google’s budget report and Microsoft’s own spend views each forecast their own platform. The native tools stop being enough when you have several accounts, more than one currency, or a weekly forecast to give finance for the whole program.

Pacing Console connects Google Ads and Microsoft Ads with one pre-filled script each, scheduled hourly in your own manager account, and LinkedIn Ads with LinkedIn sign-in, synced daily. Every campaign is paced at the hour the data was pulled, in your time zone, in CAD, USD, EUR, GBP or AUD, and the board shows each platform and the account total side by side.

The daily budget that lands each campaign sits next to the platform setting; on Pro it can be applied in one click or by Autopilot for Google Ads and Microsoft Ads, by your own script. For the Microsoft side in depth, read our article on Microsoft Ads budget pacing.