Budget & Pacing

Shared Budgets

By the AdFlint research team · Last reviewed July 2026

Google Ads budgets created once and applied across several campaigns, which then draw from the same pool as demand allows.

Instead of guessing a daily amount for each campaign, you fund one pool and let campaigns pull from it, which keeps money from sitting idle in a campaign that cannot spend it. This helps when campaigns are seasonal or unevenly matched to demand. The downside is control: a high-volume campaign can absorb the pool before smaller ones get their share, and per-campaign budget diagnostics get harder to read.

Key takeaways

  • Google reallocates a shared budget pool toward whichever attached campaign has the stronger auction opportunity that day - it does not split evenly or in fixed shares.
  • A shared budget has no per-campaign floor, so don't attach a priority campaign you need protected alongside a higher-volume sibling without monitoring the split.
  • The standard overspend allowance (up to roughly double the daily amount on a high-traffic day, reconciled monthly) applies to shared budgets the same as standalone ones.
  • Removing a campaign from a shared budget reverts it to its own budget, and deleting the shared budget breaks every campaign still attached - check the Shared Library's attachment list before either.

In practice.

A shared budget is created once, in the Shared Library section of Google Ads (or via the API or Google Ads Editor), as a standalone budget object with its own daily amount. Campaigns are then attached to it individually, replacing whatever standalone budget each campaign previously had. From that point, every attached campaign draws from the same daily pool rather than each holding its own separate cap.

Google does not split the pool evenly or in fixed proportions across attached campaigns. Instead it allocates more of the shared amount, in real time, toward whichever attached campaigns are seeing better auction opportunity at that moment, based on the same signals - expected conversions, competition, time of day - that inform normal pacing. This is the entire point of a shared budget: money that a lower-demand campaign would leave unspent on a slow day becomes available to a higher-demand sibling campaign instead, rather than sitting idle.

Shared budgets fit campaigns that are genuinely interchangeable in priority - geo splits of the same offer, match-type splits of the same keyword set, or seasonal campaigns whose demand shifts unpredictably day to day - where the goal is simply not wasting budget that one campaign can't use. They fit poorly when campaigns have different priority levels that need protecting: a brand-defense campaign or a high-margin product line that must get its allocation regardless of what a higher-volume sibling campaign is doing has no guaranteed floor inside a shared budget, since the pool has no per-campaign minimum.

The most common mistake is assuming a shared budget behaves like the sum of what each campaign used to spend separately, then being surprised when one campaign absorbs most of it on a given day. A second is forgetting that Google's normal overspend allowance still applies to the shared pool - a daily amount can be spent up to roughly double on a single high-traffic day, reconciled against the monthly average across all attached campaigns, so a shared budget can produce a bigger single-day swing than any one campaign's old standalone budget would have. A third is unassigning or deleting a shared budget without a plan: removing a campaign from it reverts that campaign to needing its own budget, and deleting the shared budget entirely breaks every campaign still attached to it.

In reporting, the Limited by budget status now describes the shared pool's constraint, not any single campaign's, so a campaign flagged as budget-limited may actually be losing the allocation race to a sibling campaign rather than facing a budget that's too small in absolute terms. The Shared Library's budget view is the place to see which campaigns are attached and how the pool's spend is actually splitting between them day to day, which is the diagnostic step worth checking before raising the shared amount. It's also worth checking that view periodically for campaigns that were attached once for a short-term reason and never removed, since a stale attachment quietly keeps competing for the pool long after the original reason for sharing it is gone.

Worked example

Three geo campaigns on one pool

Say you run three geo-split Search campaigns for the same offer - East, Central, West - each previously funded with its own $50 daily budget, for $150 a day combined. Demand between the three regions varies unpredictably by day of week, so on a given Tuesday East might have strong demand while Central and West are quiet, and the old setup would cap East at its $50 even with room to spend more, while Central and West budget sits partly unused.

After merging the three into one $150 shared budget, that same Tuesday might see Google allocate roughly $85 to East, $40 to Central, and $25 to West - still summing to $150, but now shaped to where the demand actually was rather than split into three fixed $50 caps. The tradeoff is that if East has a strong week for several days running, Central and West could see noticeably less than their old $50 baseline on those days, which is the control being traded away for the improved total utilization.

Shared Budgets compared with

The settings this gets confused with, and how to tell them apart.

Common questions.

Do all campaigns in a Google Ads shared budget get an equal share of the daily amount?

No. Google allocates the pool dynamically toward whichever attached campaign has the better auction opportunity at that moment, so the split can vary significantly day to day and won't match a simple even division.

Can I guarantee a minimum daily spend for one campaign in a shared budget?

No, shared budgets don't support a per-campaign floor. If a campaign needs protected spend regardless of its siblings' performance, give it its own standalone budget instead.

What happens to a campaign's spend history if I remove it from a shared budget?

The campaign keeps its own historical reporting. Going forward it simply reverts to needing its own standalone budget, which you'll need to set to a reasonable amount before it resumes delivering.

Does the usual daily-budget overspend rule still apply once budgets are shared?

Yes. The shared pool can still spend up to roughly double the daily amount on an unusually high-traffic day, with the overage reconciled against the monthly average the same way it works for a standalone daily budget.

You should not need to know this to advertise.

AdFlint handles the settings for you, inside the Google and Meta accounts you already own.

Try AdFlint free