Shared Negative Lists vs Campaign-Level Negatives: When to Use Each
A practical decision rule for where to put a negative keyword, plus the match-type mechanics that make it stick.
The short version
- Choose by scope: irrelevant everywhere goes in a shared list, wrong-here-only goes at campaign level.
- Blocking is additive across both sources, so there's no override and no reason to duplicate a term.
- Negatives never match close variants, misspellings, or plurals: enumerate the ones that matter.
- Over-broad words in a widely-applied shared list silently starve campaigns; keep the shared bar strict.
- Wait for roughly 100 clicks (or 3x CPA in spend) before trusting a zero-conversion cut on contextual terms.
Use a shared negative keyword list when the term should never trigger an ad anywhere in the account (brand terms you don't sell, competitor names, obviously irrelevant modifiers like 'free', 'jobs', 'DIY'). Use a campaign-level negative when the term is fine somewhere but wrong here (a term that should route to a different campaign, or intent that fits one product line but not another). The two are additive, not exclusive: a search term is blocked if it matches a negative from either source, so the real question is scope, not priority.
The one-line rule, then the reasoning
The decision comes down to a single test: if this term is irrelevant everywhere, it belongs in a shared list. If it's only wrong for this campaign, it belongs at the campaign level. That's it. Everything else is detail about how to apply that cleanly.
The reason scope is the deciding factor is that Google evaluates all applicable negatives together at match time. There is no hierarchy where a campaign negative overrides a shared list or vice versa. If a search term matches any negative that applies to the campaign it would have served in, the ad is suppressed. So you never gain blocking power by duplicating a term in both places, and you never lose it by choosing one. You only change how many campaigns the block reaches.
This matters for maintenance more than for performance. A term buried in one campaign's negative tab is invisible to your other campaigns and easy to forget. A shared list applied to 12 campaigns updates all of them the moment you add a word. The tradeoff is bluntness: a shared list cannot be surgical, because it hits every campaign it's attached to.
- Irrelevant everywhere: shared list.
- Wrong here, right elsewhere: campaign level.
- Blocking is additive across both sources, so there is no override to reason about.
Where to attach the shared list (and where not to)
You can apply a shared negative list at the campaign level only. In the UI it lives under Tools > Shared library > Negative keyword lists, and you attach it from the list's 'Apply to campaigns' action or from a campaign's Negative keywords > Use negative keyword list. You cannot apply a shared list to a single ad group. That's the first structural constraint that decides placement for you: if the exclusion needs ad-group granularity, a shared list is off the table.
A common clean setup is one master 'account junk' list (free, cheap, torrent, salary, login, complaint) applied to every campaign, plus a small number of themed lists (competitors, off-topic verticals) applied selectively. Keep the master list tight enough that you'd defend every word in it against any campaign in the account. The moment you're tempted to add a word that's only bad for search, not shopping, or only bad for one product, stop: that's a campaign-level negative.
Ad-group negatives exist for the tightest case of all, keeping a term inside the right ad group when you're deliberately routing traffic (for example, 'cheap' should serve your budget-line ad group but be excluded from your premium ad group). Those can only be entered directly, never through a shared list.
Match types are the same everywhere, and they are the real trap
Negative keyword match types (broad, phrase, exact) work identically whether the keyword sits in a shared list or a campaign. The placement decision and the match-type decision are independent, so decide scope first, then decide breadth.
The critical mechanical difference from positive keywords: negatives do not match close variants. A negative for 'free' will not block 'freee' or a plural you didn't list. A negative phrase 'car insurance' will not block 'insurance for cars'. This is deliberate, so you don't accidentally suppress traffic you wanted, but it means your negatives are more literal and more brittle than your positives. You must enumerate the variants that matter.
Negative broad match blocks a query only if it contains every word in the negative, in any order (so negative broad 'used cars' blocks 'buy used cars' and 'cars used cheap' but not 'used trucks'). Negative phrase requires the words in order. Negative exact blocks only the exact query. Practical default: use negative phrase for multi-word junk you're confident about, negative broad for single throwaway words like 'free' or 'jobs', and negative exact when a term is fine in one context and bad in a narrow one and you must not over-block. Also remember the 10-word cap per negative keyword; longer strings get rejected.
- Negatives never match close variants: no misspellings, no plurals, no reordering unless broad.
- Negative broad = all words present, any order. Phrase = in order. Exact = the whole query only.
- Single junk words: negative broad. Confident multi-word junk: phrase. Surgical exclusions: exact.
The failure mode: over-broad shared lists silently starving campaigns
The trap that burns experienced managers is applying a broad negative to a shared list that reaches campaigns it shouldn't. You add negative broad 'business' to your master list to kill 'business loan jobs' noise in a consumer campaign. Weeks later your B2B campaign's volume has quietly fallen, because negative broad 'business' now blocks every B2B query containing that word. Nothing errors out. Impressions just stop, and the shared list is the last place most people look.
Because the block is additive and silent, you cannot see from a campaign's search terms report that a shared list is the cause of suppression: suppressed queries don't appear as served terms. Diagnose it by checking Tools > Shared library > Negative keyword lists to see which campaigns each list is attached to, and by reviewing a suspect campaign's full negative set (Negative keywords tab, then expand the shared lists). If volume dropped on a specific date, cross-reference the change history for list edits.
This is why the 'irrelevant everywhere' bar for shared lists must be strict. A word that's junk in nine campaigns and valuable in one does not belong in a list applied to all ten. Split the list, or move that word to the nine campaigns individually, or (cleaner) attach the shared list only to the nine.
Deciding when a term is safe to cut at all
Placement aside, the harder judgment is whether a term deserves a negative yet. The safe heuristic: wait for roughly 100 clicks on a search term before trusting a zero-conversion verdict. Below that, a single missed conversion swings the read, and the cost of waiting is usually smaller than the cost of cutting a term that would have converted. Above 3x your target CPA in spend with zero conversions, cut it regardless of recency, because the meter is running.
Recency matters for the reverse case. If a term last converted more than 30 days ago and has since spent past your CPA target with nothing, it's fair to cut. If it converted recently, hold, even if the recent run looks weak, because you're seeing noise on a proven term.
Some negatives are universal (a term nobody in your account sells) and some are contextual (a term whose fit depends on the campaign). The universal ones are exactly your shared-list candidates and they need almost no data: 'jobs', 'salary', a competitor you don't resell are safe on sight. The contextual ones are where you owe the term some clicks before deciding, and where campaign-level placement gives you room to test cutting it in one campaign while leaving it live in another. Tools like QueryCut can surface candidate negatives from your search terms report, but the scope decision (shared vs campaign) is still yours: the tool tells you a term looks wasteful, not whether it's wasteful everywhere.
Questions people also ask
Does a campaign-level negative override a shared negative list?
No. There is no priority between them. Google evaluates every applicable negative together, and a query is blocked if it matches any of them. Placement only changes how many campaigns the exclusion reaches, not whether it wins a conflict.
Can I apply a shared negative keyword list to a single ad group?
No. Shared lists apply at the campaign level only, via Tools > Shared library > Negative keyword lists or a campaign's negative keywords settings. If you need ad-group granularity, add the negative directly to the ad group's negative keywords tab instead.
What match type should I use for negative keywords?
Use negative broad for single throwaway words like 'free' or 'jobs' so any query containing them is blocked. Use negative phrase for multi-word junk you're confident about. Use negative exact when a term is fine in most contexts and you must avoid over-blocking. Remember negatives don't match close variants, so list plurals and misspellings explicitly.
Why did my campaign lose traffic after I edited a shared list?
A broad negative added to a shared list applies to every campaign the list is attached to, and suppressed queries never appear in a served search terms report, so the cause is invisible there. Check which campaigns the list is attached to under Shared library, review the campaign's full negative set, and cross-reference change history against the date volume dropped.
How many clicks should a term get before I add it as a negative?
For universal junk (terms nobody in your account sells), add them on sight with no data needed. For contextual terms, wait for roughly 100 clicks before trusting a zero-conversion verdict, or cut sooner if spend exceeds about 3x your target CPA with no conversions and no recent conversion within 30 days.