Google Data Studio budget pacing dashboard vs a pacing tool: how to build one, and where it stops

Both names point to the same product. Google renamed Looker Studio back to Data Studio on April 10, 2026, with a free Data Studio and a paid Data Studio Pro, and moved existing reports, data sources and users over automatically. Searches for a Google Data Studio budget pacing template and a Looker Studio pacing dashboard are looking for the same thing.

1. Create a Google Sheet with one row per campaign and month: campaign name or ID, month, monthly budget, flight start and end, and whether it runs weekdays only.
2. Add a Google Ads data source. With a manager account, one data source can include up to 50 sub-accounts; viewers need access to the manager account and every selected sub-account.
3. Blend the Google Ads source with the budget sheet on campaign and month. A blend can hold up to five tables, so Microsoft Ads and LinkedIn Ads sources (through third-party connectors) can join the same view.
4. Add calculated fields: days elapsed, days in period, expected spend to date, pace, budget left, daily budget to hit and month-end forecast.
5. Build one table sorted by the absolute gap to expected spend in dollars, with conditional formatting outside your tolerance band, and a scorecard for the account total.
6. Share it with the paid media team and set a habit: someone opens it every morning and acts on the top rows.

Write these as calculated fields in the blend, using the function names your Data Studio version offers for today’s date and date differences.

Example inputs: a campaign with a US$45,000 budget in a 30-day month spends evenly, about US$1,500 a day. At 2 pm on day 10 someone opens the dashboard. The Google Ads data was last refreshed some hours ago and covers spend through the end of day 9: US$13,500.

The whole-day formula counts 9 days elapsed, expected spend US$13,500, pace 100%. That looks right only because the campaign is perfectly even. If the campaign had doubled its spend since yesterday morning, a common result of a mid-month budget change, the dashboard would still say 100% until the next refresh. For a monthly report that is fine. For catching a campaign spending twice its plan before the day is over, it is too late.

• Freshness: Google Ads, like other Google ad and measurement sources, refreshes every 12 hours, and Google says that rate cannot be changed. Editors can refresh manually, once a minute at most.
• Platforms: the Google Ads connector covers Google Ads only. Microsoft Ads and LinkedIn Ads need partner connectors, with their own refresh rates and prices.
• Missing rows: campaigns and ad groups with zero impressions do not appear, so a campaign that stopped delivering can vanish instead of showing as underpacing.
• Currency: revenue fields convert to the manager account’s currency when sub-accounts use different currencies.
• No action: a dashboard does not email you the three campaigns that need a change, and it does not apply a budget.
• Upkeep: the budget sheet has to be maintained by hand, and every mid-month budget change has to be typed in.

For monthly reporting to leadership, for one or two Google Ads accounts with stable budgets, and for teams that already live in Data Studio, the dashboard is enough and costs nothing beyond the time to build it. Keep it. Add a pacing tool when the daily decision matters: when budgets are large enough that a few days of drift costs real money, when several platforms share one plan, or when nobody opens the dashboard every morning. Our guide to what a budget pacing report should show lists the columns worth keeping.

Pacing Console pulls Google Ads and Microsoft Ads spend every hour through a script that runs in your own account, or daily when you connect by sign-in; LinkedIn Ads connects with LinkedIn sign-in and syncs daily, with Sync now any time. Pace is judged at the hour the data was pulled, in your time zone, with weekday schedules and flight dates, and the morning email lists only off-pace campaigns with the daily budget to set.

If you still want the numbers in Data Studio or a sheet, every table exports to CSV, and one IMPORTDATA formula keeps a Google Sheet in sync. Our comparison of Pacing Console and Looker Studio covers the trade-offs in detail.