Standard Shopping

Standard Shopping runs on a mechanism unique among Google campaign types: instead of keywords, the unit of targeting is the product, pulled directly from a Merchant Center feed. Google reads your feed's titles, descriptions, images, prices, and attributes, and matches search queries to individual products based on that feed data rather than any keyword list you write. This means the feed itself functions as your targeting layer - a product titled "Women's Running Shoe" with no brand or color attributes will simply not match queries containing those terms, regardless of how relevant the product actually is, because there is nothing in the feed for Google to match against.

Bidding happens at the product group level, which you build by subdividing your full catalog using feed attributes (category, brand, product type, custom labels) into groups you can bid on independently. This is the core control Standard Shopping offers that Performance Max does not: you can bid a high-margin product group more aggressively and a low-margin or clearance group more conservatively, and you can see exactly which product groups are spending what and converting at what rate. Negative keywords work here too, layered on top of product-level matching to exclude specific irrelevant queries the same way they do in Search Campaigns, and the search terms report shows you exactly which queries triggered which products, giving Standard Shopping the same transparency Performance Max deliberately withholds.

The feed quality problem is the mechanical center of everything that goes right or wrong with Standard Shopping. Titles that front-load the terms customers actually search (brand, product type, key attribute, then descriptive filler) match more queries than generic marketing copy. Missing or thin attributes (no color, no size, no material) shrink the query space a product can match at all. Low-resolution or non-compliant images can get products disapproved outright by Merchant Center policy review, which removes them from eligibility before Standard Shopping ever gets a chance to bid on them. None of this is optional configuration the way ad copy tweaks are in a Search Campaign - a Standard Shopping campaign with a thin feed has a structurally smaller addressable query space no matter how well the bidding is tuned.

Advertisers choose Standard Shopping specifically when they need product group-level control or margin protection that Performance Max won't give them, since Performance Max pools Shopping inventory in with every other surface and gives far less visibility into per-product performance. The tradeoff is that Standard Shopping only reaches Search and the Shopping tab, missing the Display, YouTube, Discover, and Gmail inventory Performance Max can also serve, and generally requires more hands-on management of product groups and negatives to perform well. It is a reasonable default for catalogs with meaningfully different margins across products, or for merchants who have been burned by Performance Max spending disproportionately on their lowest-margin SKUs with no way to see it happening.

In reporting, product group-level performance is where Standard Shopping earns its keep - segment by product group or by custom label (a feed attribute you can set specifically for reporting buckets like margin tier or seasonality) to see whether spend is landing on the products you actually want to move. A campaign-level ROAS that looks healthy can hide a handful of product groups burning budget at a loss while a few high-margin winners carry the average; that pattern is invisible at the campaign level and only shows up once you break out by product group.