Campaign priority settings for Shopping
How Standard Shopping's high/medium/low priority tiers work with shared negatives to control which campaign serves which query, the classic tiered query-sculpting structure and its limits.
Campaign priority decides which of your Standard Shopping campaigns serves first when the same product could show for a query. Set high, medium or low, then use negative keywords to push queries down the tiers to the campaign you want. It's the classic tiered structure for sculpting Shopping traffic, and it only works between Standard Shopping campaigns.
What campaign priority actually controls
Priority is a per-campaign setting (High, Medium, or Low) that answers one narrow question: when the same product is eligible in more than one of your Standard Shopping campaigns for the same query, which campaign gets to enter the auction?
Google always picks the higher-priority campaign first, regardless of bid. That's the whole mechanism. Priority does not change your ad rank, your position, or how you compete against other advertisers. It only arbitrates between your own overlapping campaigns.
On its own, priority does nothing useful: a high-priority campaign would simply serve everything. It becomes powerful only when paired with negative keywords, which push specific queries down to lower-priority campaigns. Priority sets the order; negatives decide what falls through.
The values
| Priority | Serves | Typical role in a tiered structure |
|---|---|---|
| High | First | Generic/broad campaign at a low bid; negatives block the valuable terms |
| Medium | After high | Category-level campaign; catches mid-intent queries |
| Low | Last | Brand/high-intent campaign at a high bid; receives only what higher tiers pushed down |
The default for a single campaign is Low. Priority only matters once you run multiple Standard Shopping campaigns over overlapping products.
Deep dive The classic tiered query-sculpting structure
The canonical three-tier structure exists to solve one problem: you want to bid low on cheap generic searches and high on valuable high-intent (usually brand) searches, but in Shopping you can't target queries positively, so you can't just build a "brand keyword" campaign. Priority plus negatives simulates it.
Setup, three campaigns over the same products:
High priority, "Generic", low bid (or low tROAS-equivalent budget). Negatives: your brand terms and any high-value terms. Because the valuable queries are blocked here, only leftover generic traffic serves from this campaign, cheaply.
Medium priority, "Category", medium bid. Negatives: your brand terms. Catches mid-intent queries that the High campaign blocked but that aren't yet brand-level.
Low priority, "Brand / high-intent", high bid. Negatives: none. Serves last, so it only ever receives the queries the two higher tiers pushed down, your most valuable searches, where you're happy to pay more.
How a query flows: a shopper searches your brand name → the High campaign is eligible first but its negatives block brand → it cascades to Medium, also blocked → it lands in Low, no negatives, high bid. Meanwhile a bare generic search hits High, isn't blocked, and serves cheaply. Same products, three bid levels, routed entirely by priority + negatives.
Getting the negatives right is the whole game. A brand term missing from the High campaign's negative list leaks a valuable search into the cheap campaign at the wrong bid. Maintain the brand/high-value negative lists as shared lists so one edit updates every tier: see negative keywords for Shopping for the mining workflow that feeds these lists.
Hard limits to know before you build this
- Standard Shopping only. Priority tiers arbitrate solely between Standard Shopping campaigns. PMax outranks every Standard Shopping campaign for the same product, no matter its priority, so if PMax serves a product, the tiered structure can't sculpt that product's queries. Separate PMax and Standard at the product level instead (each product in one campaign's serving set). See Standard Shopping vs PMax.
- Priority is not position. It never affects where you rank against competitors, only which of your campaigns enters the auction.
- Overlap is required for it to matter. If your campaigns already target non-overlapping product sets (via inventory filters), priority is moot: there's nothing to arbitrate. The tiered structure specifically requires the same products across all three tiers.
- The feed still decides eligibility. Priority routes queries you're already eligible for. If a product's title doesn't match the query in the first place, no priority setting conjures the impression. Priority reshuffles feed-earned traffic; it doesn't create traffic.
When to use it, and when not to
Use tiered priority when you run Standard Shopping, want distinct bids for generic vs brand/high-intent traffic, and are willing to maintain the negative lists that make it work.
Skip it when you run mainly PMax (priority won't touch PMax traffic), your catalogue is small enough that one campaign with clean titles and a shared negative list does the job, or you'd rather separate campaigns by product (inventory filters, custom labels) than by query. For many accounts, product-level structure is simpler to reason about and doesn't leak when negatives fall out of date.
Frequently asked questions
Does higher priority mean higher position in the auction?
No. Priority doesn't affect ad rank or position. It only decides which of your own overlapping campaigns is eligible to enter the auction for a given product and query. Your bid and quality still determine where you actually rank.
What if two of my campaigns have the same priority?
With equal priority for the same product, Google uses the higher bid to decide which campaign serves. That's why the tiered structure relies on distinct priorities plus negatives; leaving it to bids alone makes routing unpredictable.
Does priority work against Performance Max?
No. Priority only arbitrates between Standard Shopping campaigns. PMax takes serving priority over all Standard Shopping campaigns for the same product regardless of their priority setting. To separate PMax from Standard, use product-level splits, not priority.