Most BulkSheet Pro decisions are inclusion decisions. You set a target ACoS and the engine recommends bid changes against it. You add a SKU rule and a specific subset of products gets evaluated against a different target. You harvest a search term and a new exact-match campaign joins the rotation.
Excluding a campaign is the inverse operation. You're explicitly telling BulkSheet Pro: don't recommend anything for this campaign. Not bids, not placements, not negates, not harvest, not term conflicts, not product pauses. The campaign exists in your account, you can see it on the Campaigns page, its metrics still count toward your account's totals — but the rec engine treats it as out of scope.
This is a sharper move than it sounds, and getting the rationale right matters.
How to exclude a campaign
Exclusion happens through Campaign Rules in the Advanced Options panel. A Campaign Rule has two possible actions:
- Use target ACoS — the campaign-matching rule applies a custom target and sensitivity to the matching campaigns
- Exclude from optimization — the campaign-matching rule walls the matching campaigns off entirely
To exclude, add a Campaign Rule, type the words to match in the campaign name (comma-separated), and set the action to Exclude. Click Save (or Re-analyze if you've already run the analysis), and the matching campaigns are now excluded from every rec engine.
The match is whole-word, case-insensitive. A rule with the words "test, sandbox" matches campaigns named "AirFryer-Test", "Sandbox-Q4", or "test-campaign-2026" — but it doesn't match "fastest" (which contains "test" as a substring but not as a whole word).
What changes when a campaign is excluded
The rec engines all check for exclusion before generating recommendations. The full list of effects:
- No bid recommendations for any keyword in the campaign
- No placement recommendations for any placement in the campaign
- No negate recommendations for any search term in the campaign (per-ad-group or cross-campaign)
- No harvest recommendations originating from the campaign's search terms
- No term conflict recommendations involving the campaign's ad groups
- No product pause recommendations for any product ad in the campaign
- The Sankey flow viz shows the campaign's entities in the "Excluded" bucket on the leftmost column
- A small red dot appears next to the campaign name on the Campaigns page so the status is visible at a glance
The campaign is still visible everywhere. It appears on the Campaigns page, in the keyword list, in the search term list. Its metrics still count toward account-level rollups (impressions, spend, sales, account CPO). You can still manually edit its budgets, bids, and placements through the Campaigns page if you want to — exclusion only stops the rec engines from generating recommendations; it doesn't disable your direct edits.
What it doesn't change: anything about the campaign in Amazon. Excluding a campaign in BulkSheet Pro doesn't pause the campaign, doesn't change its bids, doesn't affect its delivery. It only affects how BulkSheet Pro itself behaves with respect to that campaign.
When to exclude
The legitimate use cases share a common pattern: you have a specific, ongoing reason to manage this campaign outside BulkSheet Pro's automatic flow.
Test campaigns. You're running an experiment — testing a new creative variant, a new bidding strategy, a new keyword set — and you want BulkSheet Pro to leave the test alone while you observe what happens. Naming the test campaigns with a "test-" prefix and adding a Campaign Rule that excludes "test" walls them off cleanly. When the test concludes, you can rename the campaigns (or remove the exclusion rule) to bring them back into the rec engine's view.
Tightly-tuned brand-defense campaigns. Your brand-defense campaigns are running at unusual targets you've carefully tuned through manual review. The rec engine, even with a Campaign Rule setting a custom target ACoS, might still suggest moves you'd rather not make automatically. Exclusion takes the engine off the field entirely for these campaigns — you'll manage them manually through the Campaigns page.
Promo-period campaigns. You have campaigns running for a 30-day promotion where the economics are deliberately different from your usual targets. Excluding them for the promo period keeps the engine from "fixing" what's not broken. When the promo ends and the campaigns return to normal performance expectations, remove the exclusion.
Campaigns with intentional special handling. A campaign with a creative partner where bids are negotiated externally. A campaign that's part of an A/B test against the rest of your account. A campaign that's running on a different attribution model than the rest. These all share the property: you have a reason for the campaign to operate outside the standard rec flow.
When NOT to exclude
Exclusion is for campaigns you've decided to manage differently. It's not for campaigns you'd prefer to ignore.
If you exclude a campaign because "I'll figure this out later," you've essentially hidden the work from yourself. The campaign keeps spending whatever it spends; BulkSheet Pro stops surfacing recommendations that could have helped. The "later" tends to extend. The cleaner pattern, when you don't have time for a campaign right now: leave it included, let the rec engine generate its recommendations, and choose to skip them for this cycle. Next cycle you may have time to address them.
Don't exclude a campaign just to make the Recommendations page tile counts lower. The counts reflect work the engine thinks is worth doing. Suppressing them visually doesn't change whether the work is worth doing.
Don't exclude entire ad types. If you have a Campaign Rule with words that match all your SD campaigns, you've effectively walled off SD from the rec engine. That might be fine if you've genuinely decided to manage SD entirely outside BulkSheet Pro — but more often it's a setup mistake. The campaign-type override (the SD Target ACoS field) is the right tool for "manage SD against a different target" — not exclusion.
Exclusion and the rule hierarchy
Campaign Rules sit second in the priority hierarchy (after SKU rules, before keyword rules). If a campaign matches an exclude-action Campaign Rule, the entire campaign is walled off — none of the rec engines run on it, regardless of whether SKU rules or keyword rules would otherwise apply.
This is the correct priority. Exclusion is a per-campaign-name statement of intent ("don't touch this campaign"), and that intent should override any per-SKU or per-keyword behavior that would otherwise apply.
The cache: BulkSheet Pro caches exclusion results per campaign name for performance — checking exclusion happens many times during a cycle, so the cache prevents repeated rule evaluation. The cache is invalidated whenever you change any setting (including the Campaign Rules), so changes always take effect on the next analysis run.
The visual indicator
The red dot next to a campaign name on the Campaigns page is small but important. It's the only place exclusion is surfaced in the UI passively (the Sankey shows it too, but only when you're looking at the flow viz). Without the indicator, an excluded campaign would look identical to any other campaign — and you'd potentially be confused when its metrics drift over time and no recommendations ever appear.
Train yourself to scan for the red dot when something seems off. If you're investigating a campaign that you expected to see in the rec engine's output and don't, check the Campaigns page first — the red dot answers the "why isn't this in the recs" question immediately.
What BulkSheet Pro won't do
It won't exclude based on entity attributes other than campaign name. The Exclude action is part of Campaign Rules specifically — you can't exclude a specific SKU's product ads (only target them with a different SKU rule), and you can't exclude a specific keyword. Exclusion is a campaign-level operation.
It won't remove excluded campaigns from your account-level baseline math. Excluded campaigns still contribute to your account CPO calculation, your total spend, your total orders. The rationale: these baseline metrics are about the size and shape of your account, and the excluded campaigns are still part of that account. The exclusion is about whether the rec engines act on them, not whether they exist.
It won't prevent you from editing an excluded campaign manually. The Campaigns page accepts budget edits, status toggles, and placement adjustments on excluded campaigns just as it does on included ones. Exclusion only affects the automatic rec generation; manual edits stay in your hands.
It won't warn you when you exclude an unusually large portion of your account. There's no "are you sure?" prompt if you set up a rule that excludes 80% of your campaigns. The Sankey will show this — a thick Excluded band on the leftmost column is a visual signal — but BulkSheet Pro doesn't second-guess your intent.
The right rhythm
For most accounts, exclusion is sparing — one rule, maybe two, matching a small subset of campaigns that genuinely deserve special handling. Most accounts use zero exclusion rules and are fine.
Add exclusion rules when you have a clear reason. Remove them when the reason no longer applies. Treat them as decisions to revisit each cycle, not as set-and-forget configuration. A test campaign you excluded six months ago might no longer be a test; a brand-defense campaign you carefully tuned might now be fine to manage automatically.
The right exclusion rule has a clear answer to "why is this excluded?" If you can't answer the question without reaching for "I'm not sure anymore" or "it was a one-time thing," the rule has probably outlived its purpose.