Connect Microsoft Ads with the Pacing Console script

Paste the pre-filled script from Connect platforms into Microsoft Advertising under Tools, Scripts, Create script, run Preview, and schedule it hourly; it covers one account or every account a manager account holds.

Install the script

1. Copy your script
   In Pacing Console, open Connect platforms. Under Step 2, Microsoft Ads, press Copy script.
2. Open the account
   Sign in to Microsoft Advertising and open the account, or the manager account that holds several.
3. Create the script
   Go to Tools, then Scripts, then Create script. Paste the script and save it as Pacing Console. Authorize it if Microsoft Advertising asks.
4. Run Preview
   Press Preview. The log should show "campaigns sent, response 200" for each account.
5. Schedule it hourly
   Set the schedule to run hourly. The Microsoft Ads card on Connect platforms shows Connected after the first run.
6. Add budgets
   On the Pacing page, press Add budget on each campaign under Spending, no budget yet.

Good to know

• The script updates itself on every run, like the Google Ads script, so you paste it once.
• In a manager account it covers every account it can see. Campaigns that are paused and have no spend this month are skipped.
• The same APPLY_BUDGET_CHANGES and LINK_AUDIT options as the Google Ads script are at the top, in OPTIONS.
• Campaigns on a shared budget can be paced, but queued budget changes skip them with "Uses a shared budget. Change it in Microsoft Advertising."

Related articles

• Connect Google Ads with the Pacing Console scriptPaste the pre-filled script into Google Ads Scripts, authorize, preview and schedule it hourly. It updates itself.
• Pace, forecasts and budget changesHow pace, the month-end forecast and the daily budget to hit are worked out, and how to queue a budget change on Pro.
• Audit the links running in your ad accountsAn hourly read-only script checks every live Google Ads and Microsoft Ads URL against your naming rules.
• Troubleshooting common problemsFixes for scripts that stop reporting, CNAME records that aren't detected, 422 naming errors and the Free user limit.