Every ecommerce account I audit has the same question buried in it: should this be running Standard Shopping, PMAX, or both? Most agencies pick one and never revisit it. That's a mistake. The right answer depends on your catalog size, your margin spread across SKUs, and how much control you're willing to give up for reach. I run both in most accounts I manage, but never blindly — the structure matters more than the campaign type.
What Standard Shopping still does better
Standard Shopping gives you a search terms report, negative keywords, and manual control over bids at the product group level. PMAX gives you none of that in a usable form. If you've ever tried to figure out why PMAX spent your budget on a product you didn't want promoted, you already know the frustration.
- Standard Shopping: full visibility into search terms, granular negatives, predictable bid control — but Shopping-only reach, no Display/YouTube/Discover inventory
- PMAX: broader inventory including Search, Display, YouTube, Gmail, and Discover — but a black-box search terms report and asset-driven optimization you can't fully steer
- Standard Shopping wins for high-margin hero SKUs where you want precision and negative keyword control
- PMAX wins for scaling reach on a large catalog where manual management of thousands of SKUs isn't realistic
Performance-based bucketing: the structure that actually works
The mistake I see most is running one Shopping campaign with every SKU thrown in together, all competing for the same budget with no differentiation. Instead, I bucket the catalog by performance and give each bucket its own campaign and its own budget priority. Three buckets, minimum:
- Index (top performers): SKUs with proven ROAS and conversion volume, running in a Standard Shopping campaign with the highest priority and dedicated budget
- Under-index (underperformers with potential): SKUs getting impressions but low conversion — isolate these so they can't drain budget from winners, test tighter bids or exclude entirely
- No-index (dead weight): SKUs with spend and no conversions over a meaningful window — either exclude from Shopping entirely or route them into a low-budget PMAX campaign to test if broader inventory helps
This bucketing does two things a single flat campaign never can: it protects budget for your winners, and it isolates the losers so you can see clearly whether the problem is the product page, the price, or the targeting — not a budget fight hidden inside one campaign.
Running Standard Shopping and PMAX at the same time
This is where most accounts get it wrong. Google's own guidance nudges you toward letting PMAX run everything, but PMAX will happily bid on the exact same high-performing SKUs your Standard Shopping campaign is already winning with — and by design, Google tends to prioritize PMAX in the auction when both target the same product. That's the mechanism behind the cannibalization I've written about in Why Your Performance Max Campaign Is Cannibalizing Your Branded Search, and it applies just as much to Shopping inventory as it does to branded search terms.
If Standard Shopping and PMAX are both eligible for the same product, you're not running two campaigns — you're running an internal auction against yourself.
The fix is exclusion, not hope. In my structure, the Index bucket runs exclusively in Standard Shopping, and I exclude those same SKUs from any PMAX campaign using a listing group exclusion or a separate feed label. PMAX is then reserved for the No-index bucket, new SKUs without conversion history, or genuinely incremental reach on mid-tier products. That way each campaign has a distinct job: Standard Shopping protects proven winners with full control, PMAX explores reach on everything else.
- Use a custom label or feed attribute to tag each SKU's bucket — index, under-index, no-index
- Exclude the Index bucket's SKUs from PMAX using listing group exclusions so PMAX can't compete for your winners
- Give the Index Standard Shopping campaign top budget priority and check the auction insights weekly
- Re-bucket monthly as conversion data shifts — a no-index product today can become a winner after a price change or seasonal demand
- ✓︎Segment your catalog into index, under-index, and no-index buckets by ROAS and conversion volume
- ✓︎Run Index SKUs in Standard Shopping with dedicated budget and manual or tightly capped smart bidding
- ✓︎Exclude Index SKUs from any PMAX campaign so the two don't bid against each other
- ✓︎Route no-index or unproven SKUs into PMAX to test broader inventory without risking your winners
- ✓︎Re-bucket monthly, not quarterly — Shopping performance shifts faster than most people re-check it
None of this is exotic. It's disciplined feed segmentation and campaign exclusions applied consistently. But it's the difference between an account where PMAX and Standard Shopping quietly cannibalize each other's spend, and one where each campaign is doing a job the other can't.