This is for anyone running Google Ads for a group of clinics, a multi-branch hospital or several doctors, where each campaign sees only a handful of conversions a month. Smart Bidding needs conversion history to learn. A campaign with five enquiries a month gives it very little. The question is whether pooling campaigns under one portfolio bid strategy helps, and what you lose if you do.
The method below is a decision framework. It does not assert a gain, because the effect depends on how similar your locations are. It assumes you know target CPA bidding and the basics of campaign structure. For the wider context of paid search for hospitals, our healthcare PPC guide is the broader reference, and the cost data by specialty explains why click prices differ across the groups you may want to pool.
What a portfolio strategy is
Google's help page on portfolio bid strategies describes them as AI-powered, goal-driven bid strategies that optimise bids across multiple campaigns, with one place to change bidding settings for every campaign using the same strategy. Pairing a portfolio with a shared budget is described as best practice. You create them in the Shared library, during campaign setup or in campaign settings, or by changing the bid strategy of existing campaigns.
Two facts from that page constrain the design. A portfolio strategy is not available for Performance Max campaigns. And you cannot change an existing portfolio strategy's type, for example from target CPA to target ROAS; you would need a new strategy of the desired type. Plan the goal before you build.
Google does not spell out on that page exactly how data is pooled, so treat claims about pooled learning as reasonable expectation, not guaranteed behaviour. Test it.
Why thin data is a problem
An automated bid strategy estimates the likelihood of a conversion for each auction, using signals from past conversions. With very few conversions, the estimates are noisy. Bids swing, budgets either fail to spend or spend on poor clicks, and managers tend to react by changing targets, which resets the noise. Pooling gives the system a larger set of conversions to learn from, on the assumption that the campaigns share enough characteristics for the learning to transfer.
That assumption is the whole decision.
When pooling is likely to help
Pool campaigns when they are similar on the things that drive conversion likelihood.
- Same service. Several dental clinics offering the same consultation, or several branches of a diagnostic chain offering the same test.
- Comparable markets. Similar cities or catchments, with similar competition and click prices.
- Same conversion definition, tracked in the same way, with the same value logic.
- Comparable landing pages and booking flows.
- A common target. The business is content with the same cost per qualified enquiry for each member.
A hypothetical example, clearly illustrative: an eight-branch physiotherapy chain across tier-two cities, each branch producing a few enquiries a month, all running one landing page template and one booking flow. A single shared target CPA across the eight Search campaigns is a reasonable first test.
When pooling hides a problem
Pooling averages. An average can conceal a weak location.
- A weak branch rides on strong ones. The shared target is met overall, while one location produces enquiries at a far higher cost. Without per-campaign cost reporting, nobody notices.
- A strong branch is held back. The strongest location could take more budget at a profit, but the shared target moderates its bids.
- Mixed services. Pooling a high-value surgical line with a low-value consultation line makes the cheap line look good and the system favour it.
- Different phone handling. One branch answers calls quickly and another does not. The bid strategy sees only the conversion event, not the quality of follow-up, and rewards both the same.
- Different click prices. If one city costs far more per click, a shared target CPA can starve it of impressions.
Consider keeping separate campaigns where branches differ on service, price, capacity or follow-up. Capacity matters most: a doctor with no appointment slots for three weeks should not be pooled with a clinic that has them tomorrow.
Guardrails to set before pooling
- Define the conversion as a qualified enquiry or booking, not a page view. Pooling a noisy conversion makes the noise louder.
- Choose the target from your own data. Compute the current cost per qualified enquiry across the campaigns you plan to pool, and set the portfolio target near it, not far below. An aggressive target on thin data reduces delivery.
- Set a bid limit. Google's page notes that a maximum CPC bid limit can help prevent sudden CPC spikes when moving to automated strategies, though it names Maximize Conversions as its example.
- Use a shared budget deliberately. A shared budget lets money flow to the campaign with demand. It also lets one campaign consume it all. Decide whether that is acceptable.
- Keep per-campaign reporting. Create a view that shows each campaign's spend, enquiries and booked appointments separately, so a hidden weak location stays visible.
- Record the baseline for each campaign before the change: spend, conversions, cost per conversion and impression share.




