Performance Max for B2B: The Exclusion Stack That Stops the Waste
Performance Max isn't a black box anymore, but its defaults still punish long sales cycles. Here's the exact exclusion, conversion-feedback and value-tier stack B2B accounts need before letting PMax spend a dollar.

Performance Max stopped being a black box some time ago. Most B2B accounts are still running it like one.
The 2026 control surface — campaign-level negative keywords, brand exclusions, channel reporting, expanded search themes — exists precisely because the default PMax behaviour is hostile to long sales cycles. Left alone, the campaign optimises toward the cheapest conversion event it can see. In B2B that event is almost always a form fill from someone who will never buy: a student, a job seeker, a competitor doing research, or a bot. Google's own lead-gen guidance is explicit that you should optimise toward a lead-gen-specific goal like "qualified lead" or "converted lead" rather than raw volume, according to Google Ads Help.
So the question is not "does PMax work for B2B." It is: what has to be true before you let it spend? Here is the stack, in the order it should be built.
Layer 1: Close the loop before you launch, not after
PMax optimises against what you feed it. If the only signal reaching the platform is an on-site form submission, the algorithm's definition of success is "more form submissions," and it will get very good at finding them from the wrong people.
The fix is offline conversion import or enhanced conversions for leads, wired from your CRM back into Google Ads with a qualified-lead or opportunity event. Google recommends upgrading offline conversion imports to enhanced conversions for leads because it relies on first-party data rather than the Google Click ID, per Google Ads Help. Practically: capture the identifier at form submit, stamp it on the CRM record, and push the qualification event back on a daily cadence — Google's guidance is to upload conversion data regularly, ideally daily (Google Ads Help).
There is a volume floor here too. The conversion action you bid toward should have generated at least 15 conversions in the last 30 days at account level, according to Google Ads Help. If your qualified-lead count can't clear that, PMax has nothing to learn from. Run Search until it can.
This is the same discipline that makes any paid programme legible — see our write-up on designing a geo-holdout test on a constrained budget for the measurement side of the same problem.
Layer 2: The exclusion stack
Four exclusions, all of which now exist natively. Configure all four before the campaign goes live.
Brand exclusions. PMax will happily bid on your own brand name and bill you for traffic your Search brand campaign already owns, inflating its reported efficiency. Google's lead-gen guidance names brand exclusions as the control for avoiding serving on unwanted branded queries (Google Ads Help). Add your brand list at campaign level. If you run a dedicated brand Search campaign — and you should — this single setting is the difference between PMax reporting real incremental leads and reporting a laundered version of your brand traffic.
Campaign-level negative keywords. Since Google's 2025 control release, campaign-level negatives and search terms reporting are available in PMax, per Google's Performance Max update. Build four working lists rather than one: careers intent ("jobs", "salary", "internship"), free/DIY intent ("free", "template", "open source", "tutorial"), education intent ("course", "certification", "what is"), and competitor-research intent where you do not want to pay for it.
Placement exclusions. Display and app inventory is where PMax budget goes to die in lead gen. Apply an account-level placement exclusion list covering mobile game categories and made-for-advertising domains, and review the placement report weekly for the first month.
URL expansion. Turn it off, or restrict final URLs to pages you have actually optimised for conversion. Otherwise PMax will route paid traffic to your careers page, your pricing FAQ, and your blog archive.
Layer 3: Steer with search themes and value tiers
Search themes are the closest thing PMax has to keyword input. The limit was raised to 50 themes per asset group, up from the previous cap, according to JumpFly. Use them for category and problem language your landing page does not already contain — the themes are directional, not exact-match triggers.
Then tier your conversion values. Not every qualified lead is worth the same, and value-based bidding lets you say so: assign distinct values and use Maximize conversion value or target ROAS, per Google Ads Help. A workable starting tier for a B2B SaaS account: demo request from a target-account domain at the top, demo request from anyone else below it, content download well below both, and everything unqualified at zero. Zero is a real value — it tells the algorithm to stop chasing that shape of lead.
Firmographic value tiering only works if you know which accounts matter. If that definition is fuzzy, start with the buying-committee rebuild before you touch bid strategy.
What to actually do this week
- Audit whether your PMax campaign has a qualification event flowing back from the CRM. If not, pause it. Everything else is decoration.
- Add brand exclusions today. This is a ten-minute change and it is the single largest source of overstated PMax performance in B2B accounts.
- Build the four negative lists and attach them at campaign level.
- Open the channel report and check how much spend sits in Display and app inventory versus Search. If Display dominates and your qualified-lead volume is flat, your exclusions are not tight enough.
- Judge the campaign on cost per qualified lead and pipeline contribution, not cost per form fill — and give it a longer evaluation window than an ecommerce account would, because the qualification event arrives weeks after the click.
The operators getting value out of PMax in B2B are not the ones who trust it more. They are the ones who narrowed what it is allowed to see.