Budget pacing alerts across every client account: hear about it before the 25th

Written by Uptimal, the team that builds and operates Upbuild and runs marketing analytics for multinational clients across the globe. Everything below reflects how the product actually works, including the parts that are deliberately boring.

It is Friday, 14:30, and the head of reporting at a performance agency is doing what she does every Friday: opening the budget sheet, pasting month-to-date spend for each client next to its monthly budget, and reading down the column for red cells. This week there is one she did not expect. Northwind's generic search campaign spent its whole month by the 14th, the account manager was on holiday, and the client noticed first.

The check itself is not hard. The problem is that it happens once a week, by hand, in one spreadsheet, and a budget does not wait for Friday.

The Friday spreadsheet, and why it is always late

Most agencies with many client accounts run some version of this ritual. Someone exports month-to-date spend per account from Google Ads, Meta and the rest, drops it into a sheet that holds each client's monthly budget, and looks for the rows that are ahead of the calendar. It takes an hour if nothing has changed and half a day if a client added a campaign, a market or a currency.

The ritual has three flaws built in. It runs on the agency's calendar, not the budget's. It covers the accounts somebody remembered to include. And by the time it finds a problem, the money has already gone: a campaign that crosses 90% of its budget on the 12th has made the decision for you.

The fix is not a better spreadsheet. It is a rule that runs every time the numbers change, across every account, and tells a person while there is still something left to decide.

The rule, in one sentence

In Upbuild, with AI Alerts, the head of reporting types the rule the way she would say it to a colleague:

"Tell me when any client has spent more than 90% of its monthly budget before the 25th."

Upbuild AI reads the sentence, sets up the rule and schedules it. From then on it is checked every time the data refreshes, every 30 minutes, every hour or once a day, whichever cadence her organisation runs, and it runs against every account the rule covers. There is nothing extra to connect and nothing to maintain. Alerts sit next to the dashboards and check the same numbers, so the figure in the message and the figure on the client's page can never disagree.

The monthly budget is whatever the plan says it is: the amount set on the campaign, or the figure in the budget sheet the team already keeps, which Upbuild can read as a source alongside the platforms.

When a client crosses the line, the message goes where the media team already looks: a Slack or Microsoft Teams channel, or an inbox. It names the client, the account and the campaign, says how much of the monthly budget has gone and on which day, gives the date it runs out at this pace, and carries a link to the dashboard. The team hears about each problem once, however often the data refreshes. Nobody gets the same warning every half hour.

A Tuesday with the alert in place

Tuesday, 09:15. A message lands in the media team's channel on Teams: Northwind, Search Generic has spent 92% of its €40,000 monthly budget on the 19th. At this pace it runs out on the 21st. Open dashboard.

The account manager opens the dashboard from the link, sees that the overspend is one generic campaign that picked up a competitor's brand term over the weekend, and calls the client before lunch. The client decides: pause the campaign until the 1st, or move €5,000 across from a brand campaign that is under-delivering. Either way the decision is made on the 19th with six days of budget left, not on Friday with none.

That is the whole difference. The alert did not save the agency any analysis. It moved the analysis to the day it was still useful.

What the alert does, and what it never does

An alert tells a person that something has happened, with the number in front of them. That is all it does, and that is deliberate.

It never pauses a campaign, moves a budget, changes a bid or touches an audience. Upbuild reads your ad accounts, your analytics and your tag manager, and alerts are no exception: nothing Upbuild does can change a budget, a campaign, a tag or an audience. The only writes are the exports you schedule yourself with AI Data Exports, into your own warehouse, storage or spreadsheet.

For an agency this is not a shortcoming, it is the contract. A client's budget is a decision that belongs to the client and to the account manager who knows why the campaign exists. An automatic pause on the 19th would be a tidy fix for the wrong problem: the spend was fine, the plan was wrong, and only a conversation can settle that.

One rule, every account the organisation shares with you

The other thing the Friday spreadsheet could never do is cover everything. A rule in Upbuild does, because coverage is not a list you maintain. It follows access.

Everyone signs in as themselves with Google or Microsoft. An admin decides who joins the organisation and shares accounts one person and one account at a time. When the head of reporting writes her budget rule, it covers every account the organisation has shared with her: the clients she reports on today, and the client the admin adds next month, from the day it is shared. She never edits the rule to add an account.

The same model handles the other direction. When an account manager leaves, the admin removes them and their access ends that day. The dashboards, connections, exports and alerts they set up belong to the organisation and keep running for whoever takes over. A budget rule written in March does not die with the person who wrote it in September.

Per-person access also keeps the alerts honest. A rule written by someone who only works on Northwind and Acme only ever watches Northwind and Acme. Nobody is warned about a client they are not allowed to see, and the same is true of the dashboard the alert links to.

Tuning it, and writing the second rule

The first week is noisy in the way first weeks are. Two always-on brand campaigns are designed to run out on the 25th, and a small client's €2,000 budget trips the rule on the 3rd every month because its whole plan is front-loaded.

Tuning is a sentence, not a ticket: "Make it 85%, leave out the brand campaigns, and give Acme its own line at 95%." The change is saved as a numbered version you can restore, so the version that worked in the third quarter is one click away if the new one turns out to be wrong.

Most teams end up with two budget rules. The first is the one above. The second is the one nobody writes until the month a client asks why only 60% of the budget was spent: "Tell me on the 20th if any client is on pace to finish the month under 80% of its budget." Underspend is a quieter problem than overspend, and it costs a renewal just as easily.

Neither rule replaces the head of reporting. They replace the Friday afternoon she spent finding out what the rules now tell her on the day, and they give her the 25th back.

Frequently asked questions