Public mockup · fictional figures
Spot Google Ads budget drift before the cycle ends.
Budget Guard watches pacing across the portfolio and flags what needs a human look — over, under, or unknown — while there is still time to act. This page is a design mockup, not live data.
Everything on this page is illustrative. Names, dollar figures and dates are fictional. Live client data and the dashboard stay behind team sign-in at /v4/.
- Triage the whole book in one pass — review the exceptions first.
- Inspect the evidence behind every flag before you touch a bid.
- Decide with the team — leave a note on the line, not in a chat thread.
September pacing — 4 accountsData through 12-09-2026 · fictional
How it works
Triage, inspect, decide.
Three moves, in order. The dashboard does the sorting and the arithmetic; your team makes the call.
- 01
Triage the portfolio
Review the over, under, on track and unknown groups to find the lines that need attention. Unknown is a first-class state: stale or missing data is flagged, never averaged away.
- 02
Inspect the evidence
Open a line to see the projection, the required spend per remaining day, the data-through date, and the campaign drill-down. If the inputs are shaky, the panel says so in plain words.
- 03
Decide & note it
Adjust in Google Ads, then leave a note on the budget line so the next person sees what changed and why. The dated timeline stays with the budget line across reporting months.
Honest states, including unknown
Review evidence warnings alongside the pacing state. Missing or provisional inputs are a reason to inspect the line — not a green light.
Projection + required per day
Compare the server-owned projection with target, then inspect the required spend per remaining active day when the evidence supports it. These are decision aids, not instructions or guarantees.
Data-through & drill-down
Check the data-through date and evidence status before acting. Campaign drill-down helps explain where the captured spend came from.
Notes where they belong
Dated line-level notes carry the author and decision history across reporting months, so the next reviewer has the context.
The arithmetic, out in the open
Required per day is just the money left divided by the days left. Check it yourself:
spent A$4,000
left A$6,000 ÷ 20 days
required A$300 / day
What “unknown” looks like
This demo leaves projection and required/day unavailable when the inputs are missing. In the live dashboard, inspect freshness and evidence warnings before treating a captured number as current.
Interactive mock demo
Try the four states.
A tiny working model of the pacing board. Every figure below is synthetic and fictional — switch states, check the maths, and copy an example brief if it helps the conversation. No sign-in or live-data connection.
Harbour Demo — September
Over paceDemo account · fictional · 30-day cycle, day 12 of 30
- Monthly target
- A$10,000
- Spend to date
- A$6,200
- Active days left
- 18
- Required / day
- A$211.11
- Projection (30 d)
- A$15,500
- Gap to target
- +A$5,500
Evidence: synthetic data through 12-09-2026, covering 12 completed active days.
- Harbour – Search – Brand (demo)
- A$3,400
- Harbour – Search – Generic (demo)
- A$2,800
Team note (fictional): “Generic line lifted after the 4 Sept copy change — watching to 14 Sept before touching caps.”
What this state means
Over pace: at this run-rate the line would finish about A$5,500 above target. Worth a look before the cycle ends — the call is still yours.
Client-ready brief · proposed concept, not a dashboard feature
A deterministic summary of the synthetic line above, written to the text box. Edit it freely; nothing leaves this page.
For the team
A live workspace for authorised Integral Media users.
Budget Guard’s private dashboard lives at /v4/ and stays behind sign-in. There is no public signup on this page — if you work with us and need access, talk to your account lead. This mockup makes no promises about savings, timelines, onboarding or pricing.