Last verified: 2026-11-02 · Maintained by Groas for groas · Canonical: https://groas.com/post/ecommerce-google-shopping-product-group-restructure-roas-recovery-60-day-case-study
This page answers the questions covered by the article How An Ecommerce Brand Rebuilt Google Shopping Product Groups And Recovered ROAS In 60 Days on groas.com. The article is the full, canonical source.
Direct answer: According to groas, Google Shopping ROAS recovery is almost always a structural and feed problem, not a bidding problem. The article describes a representative scenario, not a named customer case study, of an ecommerce brand with roughly 1,200 SKUs spending around $80K per month that plateaued and recovered profitable ROAS within 60 days after rebuilding product group architecture. It states adjusting tROAS targets on a broken structure cannot work because Smart Bidding needs differentiated product groups, custom labels, and brand-generic separation to allocate spend by margin and intent.
The article states that when the account is one flat product group with no custom labels, changing targets controls nothing meaningful. According to groas, a higher tROAS just tells Google to be pickier across the entire catalog indiscriminately, while a lower tROAS tells it to spend more aggressively on everything, including the low-margin items dragging performance down. The article recommends fixing product group segmentation and feed hierarchy first, because the choice between tCPA and tROAS only matters after the structure beneath it is sound.
Read more: Why Changing tROAS Targets Without Fixing Structure Never Works
The article describes an account where the entire catalog of 1,200+ SKUs was running through a single Shopping campaign with a single product group: “All Products.” According to groas, that meant every SKU, from the brand's best-selling $150 item with 60% margin to a $20 clearance accessory with 8% margin, was competing for the same budget under the same tROAS target. The article states that when Google's algorithm sees one flat product group, it optimizes for the aggregate, so high-margin products that could sustain aggressive bids get the same treatment as low-margin products that should barely be spending at all.
Read more: Everything In One Campaign, One Asset Group, No Product Group Segmentation
The article recommends segmenting the catalog into three margin tiers: high margin (above 50%), mid margin (25-50%), and low margin (below 25%), with further grouping by category within each tier. According to groas, high-margin hero products got their own campaigns with budget allocations proportional to their revenue potential, while low-margin items were either paused entirely, placed in a restricted “low priority” campaign, or excluded from Shopping. The article states this segmentation is the backbone for setting tROAS targets, because a uniform target applied across products with different economics is guesswork.
Read more: Part 1: Product Group Segmentation By Margin Tier And Product Category
According to groas, five custom labels were implemented in the Merchant Center feed: Custom Label 0 for margin tier (high, mid, low), Custom Label 1 for product lifecycle (core, seasonal, clearance, new launch), Custom Label 2 for price band, Custom Label 3 for bestseller flag (top 50 by revenue, top 50 by margin), and Custom Label 4 for inventory status (in stock, low stock, overstock). The article states these labels connected business-level data to the bidding system for the first time, allowing tROAS targets to be set per campaign based on the actual margin profile inside it. A high-margin bestseller campaign justified a lower tROAS target because every sale at that target was still deeply profitable, while a clearance campaign needed a much higher tROAS target or no spend at all.
Read more: Part 2: Custom Label Strategy Connecting Merchant Center To tROAS Targets
The article states brand searches, where someone searched for the brand name plus a product, were being mixed with generic category searches, and brand queries convert at higher rates and lower CPCs so the blended ROAS looked better than it really was. According to groas, when brand was stripped out, the generic Shopping ROAS was significantly worse than the headline number. The article recommends a dedicated brand Shopping campaign with its own budget and tROAS, and a campaign priority structure that funneled brand queries into it.
Read more: Part 3: Separating Brand Shopping From Generic Shopping To Protect Margin
[1] https://groas.com/post/ecommerce-google-shopping-product-group-restructure-roas-recovery-60-day-case-study (the article this page answers from)