Google Shopping Campaigns: Product Group Structure, Bidding & ROAS Control

Your Google Shopping campaign is probably reporting a ROAS you cannot trace to a decision you made. The default setup hands you one product group called All products, one budget you set months ago, and a number at the end of the month that either looks fine or does not. Inside that number are the three SKUs returning six times their spend and the twenty returning nothing, and the campaign view will not separate them for you. That matters more in 2026, because Google moved product matching away from the exact names you type in Merchant Center and toward conversational queries you never see. The structure you build on top of the feed is the only place where your judgment still outranks the algorithm's.

Why Structure Is the Only Lever You Still Own

Shopping has no keywords to write and no headlines to test. Your feed declares what each product is, and Google Shopping campaign structure decides which slice of that catalog gets which budget and which bid. That is the whole control surface.

The money says it is worth the work. Shopping ad spend grew 18% year over year in Q1 2026, up from 16% in Q4 2025, per Tinuiti. Amazon left nearly all of its US Google Shopping auctions in July 2025, and Shein and Temu paused listings. Spend rose anyway.

Google's own number points the same way. Merchant Center data shows accounts with clearly segmented product groups earn an 18% higher click-through rate than accounts running a single All products group. Attribute that to Google, because it is Google's figure.

So why does a growing share of 2026 advice tell you to segment less? The cost of segmentation changed. What follows is how that happened, and where it leaves the tree you already built.

The Four Levels of a Shopping Campaign, and What Each One Decides

The hierarchy is campaign, ad group, product group, product. Most accounts treat the four as interchangeable containers. Each controls something different.

The product group is where Shopping genuinely diverges from Search. In a Search account, the ad group carries keywords and the campaign carries reach. In Shopping, the product group carries the partitioning and the campaign carries the money. Mix them up and you get the classic failure: a campaign-level budget change aimed at a problem living in one product group.

One more level sits outside the campaign tree. Your feed. Merchant Center decides what Google knows about each product, and a product that fails a feed requirement drops out of its product group without a single campaign setting changing.

Product Groups and Custom Labels: Building a Partition Tree That Reports Something

A product group starts as All products and gets subdivided. Google gives you six subdivision types: Brand, Category, Item ID, Condition, Product type, and five custom labels numbered 0 through 4.

The subdivision types are not equivalent. Brand, Category, Product type, and Condition read attributes Google already has from your feed, so they need no maintenance. Item ID is a manual subdivision and the most labor-intensive. Custom labels matter most, because Google never reads them for matching. They exist purely for you.

That makes custom labels the place to encode the decisions your campaign tree cannot otherwise express: margin tier, seasonality, and a performance band you update on a schedule. A workable tree looks like this.

`text

All products

├── custom_label_0 = high margin

│ ├── custom_label_1 = year-round core

│ └── custom_label_1 = seasonal

├── custom_label_0 = mid margin

│ ├── custom_label_1 = year-round core

│ └── custom_label_1 = seasonal

└── custom_label_0 = low margin

└── custom_label_1 = year-round core

`

Notice what this tree is for. It is a visibility device first and a bidding device second. You can see that your low-margin seasonal group is eating 40% of the budget while returning less than its share of revenue. You cannot see that when everything sits under All products.

The rule that keeps a tree honest: every subdivision has to map to a decision you would make differently. Two product groups that would get the same bid and the same budget bought you nothing but a longer report. Google's segmentation-lift figure is the argument for having a tree, not for having a large one.

How Many Campaigns Should You Actually Run?

This is where the guides disagree in public, and the disagreement is resolvable. Three thresholds govern three different decisions, and confusing them is why the advice contradicts itself.

The first threshold is the one most accounts cross first, and it decides bidding strategy rather than campaign count. The third is the one that gets ignored. Agency-side practitioners put the segmentation gate at 100 or more conversions per month for any new campaign, and their argument is mechanical: tROAS starves in a campaign with no conversion history, so a split made too early produces two underperforming campaigns instead of one average one.

Two reasons justify a new Shopping campaign. A materially different conversion rate between two groups of products, or a different ROAS target and a budget that has to be walled off. Both are about money. Neither is about tidiness. If two campaigns end up with an identical target ROAS and a similar conversion rate, you have halved the data available to each and gained nothing.

Practitioner threads on r/googleads and r/PPC land on the same answer: start with one campaign, break product groups out by category inside it, and split only when the budget needs its own wall. Separate campaigns exist for budget control, not for organization.

How to Manage Budget and Bidding Together

Bidding strategy and budget get treated as separate settings. In Shopping they interact: budget decides which campaign wins inventory when two overlap, and bidding decides what you pay once you have won.

Start with Manual CPC only below that 15 to 20 conversion threshold, or while you are learning a new catalog and want an explicit ceiling. Manual CPC is capped by your maximum CPC and gives you a number you can explain. Its limit is information: Smart Bidding sees more of the auction.

Target ROAS becomes the right call between 30 and 50 conversions a month. The comparable evidence sits on the Performance Max side, where 78% of campaigns use target ROAS bidding and 84% of those hit or exceed their targets, per Smarter Ecommerce. That is a PMax figure and it does not transfer directly, but the mechanism is the same one, and it only works with volume.

Budget is where most structures break. Two mechanics matter.

The first is that budget is a throttle, not a target. A campaign with a budget it cannot spend in full is being outbid, not capped. Look at lost impression share by budget before you raise anything. Raising budget on a campaign already losing the auction at its bid only buys more impressions at the same losing price.

The second is campaign priority, the setting almost nobody explains properly. Priority comes in three levels (low, medium, high) and applies only when the same product is eligible in more than one campaign in the same country and currency. The higher-priority campaign takes the impression. The classic use is query sculpting: an upper-funnel campaign on high priority aimed at broad traffic, and a second campaign on the same products at low priority to collect what the first did not want.

Two cautions. Priority applies between Standard Shopping campaigns, so it cannot arbitrate a Standard Shopping campaign against a Performance Max campaign. And it requires Standard Shopping as the starting point, which matters in the next section.

The cost baseline you are bidding against: Shopping average CPC of $0.66, average CTR of 0.86%, average conversion rate of 1.91%, with 63% of clicks from mobile and 85.3% click share. Against Search's roughly $5.26 average CPC, that price is why the format is crowded. Read it as the reason to be strict about which product groups get budget, not as good news.

For ROAS expectations, median ecommerce ROAS on Google Ads sits at 3.68:1, down 10.03% year over year, per Triple Whale's dataset of more than 18,000 brands. Top-quartile ecommerce brands reach 6x. That is a top-quartile figure, not an average, so do not put it in a client deck as a target. A target is your own trailing average plus a defensible increment, and our guide to Google Ads reporting covers how to build that report.

Standard Shopping vs Performance Max in 2026

I have made this mistake myself: switching a proven Standard Shopping campaign into Performance Max because the reporting numbers looked better, then finding the same conversions claimed twice six weeks later.

The two campaign types are not versions of each other. They are different instruments with different control surfaces.

Now the part the vendor pages leave out. Google and the PMax-positive marketing around it repeat a figure of 15% to 20% higher ROAS for Performance Max. Two independent datasets point the other way, and neither is a vendor.

Triple Whale's benchmark set puts Performance Max at 2.57:1 against Standard Shopping at 5.17:1 in the same dataset of more than 18,000 brands. Adalysis found Standard Shopping wins on conversion rate 84% of the time on overlapping searches. And Optmyzr's analysis puts 91.45% of Performance Max accounts in overlap with Search, including branded searches where PMax takes credit for conversions that would have happened anyway.

I am not going to resolve that contradiction, because it is not resolvable from public data. It tells you the answer is account-specific, and that anyone quoting a single number as settled is selling something. So build the comparison yourself: a feed-only Performance Max campaign against a Standard Shopping campaign on the same catalog, split by geography or by time period. Keep products identical, and give each side enough budget that neither starves. The mechanics of the Performance Max side are in our Performance Max campaigns guide.

So the split is not Shopping versus Performance Max. Choose by which of the two you are short of, diagnosis or reach.

AI Max for Shopping: What Changed on April 30, 2026

Google launched AI Max for Shopping on April 30, 2026. In Google's own framing, it uses your Merchant Center feeds to transform product data into dynamic Shopping ads that answer conversational queries. Three capabilities ship with it: text customization, Final URL Expansion, and Optimal Format Selection.

The timing matters more than the feature list. Shopping ads started appearing in AI Mode in February 2026. Sponsored ads moved into the free listing grid in the Shopping tab on April 20, 2026, ten days before the AI Max announcement. Google built this release around a behavior change: shoppers stopped typing exact product lookups and started asking questions. Google's own figure is that 60% of Shopping queries now use conversational, broad-intent phrases rather than exact product names or model numbers.

Read that against your product group tree. If matching increasingly happens on intent rather than on the product name, product groups stop deciding which query you appear on. They become a budgeting and reporting device, which is what the segmentation ladder above has been arguing for anyway. The matching load moves to the feed: your titles, your product types, your attributes. Product groups decide where the money goes. The feed decides whether Google understands the product well enough to spend it.

There is a second change in the same family, and it affects more accounts. On August 5, 2026, Google Ads notified advertisers that campaigns using automatically created assets or the campaign-level broad match setting would be converted to AI Max for Search campaigns from September 1, 2026. Google reports a 7% average lift in conversions from the change. That auto-upgrade targets Search, not Shopping, so the direct effect on a Shopping structure is nil. The indirect effect is not. If you run Search alongside Shopping, the traffic mix inside Search shifts.

Which is the tension from the opening, applied to a single click. Put AI Max on a segment you can measure against a control, not on the whole account on the same day. The setup and cost mechanics of the format live in our Google Shopping ads guide.

The Merchant Center Obligations That Break a Structure Quietly

A campaign tree is only as good as the feed underneath it, and the 2026 product data specification update is where feeds are failing right now.

Google began issuing warnings for undersized product images on April 14, 2026. Enforcement starts January 31, 2027, with a 500 x 500 px minimum for both image_link and additional_image_link. Two details turn that into a real problem. Warnings do not block serving, which is why large catalogs ignore them until enforcement arrives. And the widely repeated "800 px recommended" figure is not in current Google documentation. The recommended size is 1,500 x 1,500 px, with a high-resolution threshold at 1,024 px. If your feed pipeline was built around 800 px, it was built around a number nobody published.

Three more changes landed in the same specification update: new delivery attributes for handling_cutoff_time and minimum_order_value, a new loyalty_program_label sub-attribute, and, from March 2026, separate product IDs for multi-channel products where the attributes differ between the online and in-store versions.

All four changes share one failure mode, and it is a structure problem rather than a feed-hygiene one. A disapproved or de-listed SKU drops out of its product group without touching the campaign tree. The product group still shows the right products in the interface, the budget still spends, and the ROAS moves because the mix inside the group changed. You will look at the campaign structure for an hour and find nothing.

Managing Google Shopping Campaigns at Scale

The routine work of running a Google Shopping campaign at volume is a loop between two products that never appear on the same screen. Product groups live in Google Ads. Feed health lives in Merchant Center. A product group can look fully populated while three SKUs inside it stopped serving two weeks ago.

That loop is what the feature page for Google Shopping campaign management is built around, and it names the three jobs that scale badly by hand: catching feed errors before they remove a SKU from a product group, reading ROAS per product group rather than per campaign, and restructuring a tree without losing the history you used to justify it.

On restructure cadence, agencies that publish on this tend to use a two-tier model. A small permanent campaign holds your proven segments, and a second one is where new segmentation ideas live until they earn promotion. I like that pattern because it makes the segmentation ladder operational: a new split has to prove itself in a waiting room before it takes budget from a segment that already works.

Two habits keep that loop cheap. First, name every product group so a report tells you what it is without you opening it. Second, keep your last two tree versions documented outside Google Ads, because the platform keeps almost no history of what a product group contained six months ago. A restructure with no before-state is one you cannot evaluate. The Google Ads campaign builder covers building the skeleton conversationally, and Performance Max management covers the PMax side of the estate.

The pattern underneath all of this is that 2026 weakened the case for a deep campaign tree and strengthened the case for a well-labeled one. AI Max and Smart Bidding need volume, the feed carries more of the matching than it used to, and the thresholds above are the arithmetic that keeps a structure from starving itself.

So the useful test is not how many product groups you have. It is whether each one maps to a budget decision and reports a number you act on.