If you scroll r/PPC on a busy week, you will see this question in several flavors: “Should I pause Search and go all-in on PMax?” “Is PMax just Smart Shopping with extra steps?” “My rep says PMax will beat everything.” After managing north of $350M in Google Ads spend across e-commerce, lead gen, SaaS, and local services, my answer is blunt: they solve different jobs. Performance Max is not a replacement for Search any more than a Swiss Army knife replaces a scalpel. The winning setup is usually a deliberate split: Search for intent you can name and defend, PMax for inventory-aware scale and incremental reach—with guardrails so automation does not rewrite your economics in the dark.
Standard Search (and Search with a healthy Shopping layer where applicable) still matters because it preserves query-level accountability. You can see what language people typed, negate junk at the right level, structure match types and ad groups around margin and LTV, and run experiments where the only moving part is not “the entire Google ecosystem.” That matters enormously in lead generation, where one bad informational query can burn a $40–$120 click and pollute your CRM with “students” and “job seekers” disguised as buyers.
Search is also where you isolate brand. I still see accounts where PMax is allowed to harvest branded navigational intent because it is convenient, and finance later asks why blended ROAS looks heroic while non-brand never scales. Separating brand in Search (or a tightly scoped brand strategy) is not pedantry; it is how you keep incrementality honest. When someone insists PMax “just works,” I ask what share of conversions are coming from queries they cannot see or from placements they would not hand-buy. If the answer is “I do not know,” that is not a strategy; it is faith-based budgeting.
Search shines when conversion tracking is imperfect but directionally fixable: you can throttle by keyword, schedule, geo, and ad copy while you repair offline imports or consent gaps. PMax wants volume and clarity; Search tolerates a more manual feedback loop because you can starve the dumb money directly.
Performance Max is best understood as goal-driven portfolio bidding across surfaces with Shopping as the spine for most retailers. When your Merchant Center feed is clean—accurate GTINs, coherent titles, competitive pricing, fast landing pages, and meaningful custom labels for margin or hero SKUs—PMax can outperform siloed Shopping plus Display experiments because Google reallocates budget toward combinations of query, creative, and placement that humans would never stitch in real time.
Where practitioners get burned is mistaking PMax for “set tROAS and go to lunch.” Creative signals, audience signals, listing groups, URL expansion rules, and account-level negatives all change who gets touched. Without them, PMax happily spends on cheap clicks that meet a loose conversion definition. I treat PMax like a leveraged product: upside is real, but drawdowns are faster when governance is weak.
The hot take from the forums—“just run PMax”—often comes from e-commerce operators where Shopping was already doing the heavy lifting. Transplant that advice to a law firm or industrial distributor and you get expensive lessons in relevance and lead quality.
For e-commerce, my default is rarely “Search only.” If the catalog justifies it, PMax (or at minimum Shopping) belongs in the mix for scale, especially when you are willing to run listing groups by margin band and use promotional feeds during peak. Search still handles high-intent non-brand and category head terms where you want tight copy and landing-page alignment. I frequently run non-brand Search alongside PMax with deliberate negatives and campaign priorities so they are not in a knife fight for the same queries without a plan.
For lead generation, I am more conservative. Search with tight themes, offline conversion import, and disqualification signals in the CRM routinely beats PMax on qualified pipeline, even when PMax looks cheaper on front-end CPA. If you must run PMax for leads, use form-quality scoring, call-tracking labels, and delayed conversions; narrow geo; and cap spend until you see SQL data, not just MQL volume. Otherwise PMax will optimize to the lead form your developer built, not the customers your sales team actually wants.
New accounts lack the conversion density PMax uses to stabilize. I almost always start with Search (and manual or semi-automated bidding if volume is low) to force explicit structure: keywords, ads, landing pages, geo, and negatives. You are teaching the account what “good” means. Throwing PMax into a cold start with fuzzy goals produces flashy impressions and fragile learning. Exception: a retailer with a proven feed and immediate transaction volume can sometimes start PMax earlier—still with tight asset groups and brand handled deliberately.
Mature accounts with rich history are where PMax earns its headline. Look for stable seasonal patterns, creative refresh cadences, and enough conversion volume that tROAS or tCPA is not permanently “learning.” In mature setups, I use PMax to capture demand you cannot enumerate as keywords—YouTube and Discover synergies, long-tail retail queries, and dynamic combinations—while Search defends the named intent that boards actually care about in forecasting.
Benchmarks are not promises; vertical, margin, brand mix, and country dominate. Still, after years of audits, I use ranges as tripwires, not targets. In healthy US e-commerce with fair attribution, I often see blended account ROAS in the 3:1 to 8:1 window depending on category; strong PMax retail segments can sit at the high end when feed and promos align, while thin-margin DTC may live closer to 2:1–4:1 even when the account is “good.” Search-only non-brand frequently shows lower ROAS but higher controllable incrementality when measured honestly—another reason blended dashboard worship is dangerous.
For lead gen CPA, sanity bands are wider: local services might land $35–$120 qualified lead CPA on Search when tracking is tight; B2B SaaS with long cycles might show $150–$600 front-end CPL with SQL costs evaluated separately. PMax lead CPA can look 10–30% “better” on-platform while SQL rate collapses; I always reconcile to downstream outcomes monthly.
| Dimension | Search | Performance Max |
|---|---|---|
| Control | High: keywords, match types, ad group architecture | Low–medium: signals, assets, listing groups, exclusions |
| Transparency | Search terms (with gaps), placement controls for partners | Limited; insights and channel groupings, not full query logs |
| Targeting | Intent-first language capture | Audience + asset + feed signals across multiple surfaces |
| Best for | Lead gen, B2B, tight geography, brand isolation | Retail scale, broad catalogs, strong creative + feed |
| Learning appetite | Moderate; works with lower volume if structured | High; hungry for conversions and clean value data |
| Risk profile | Slower to waste at scale if negatives are disciplined | Faster drift if goals or feed quality are weak |
Use the table as a decision grid, not a scorecard. The right choice is often both, with budget weighted by which layer is actually creating customers you would not have acquired in a holdout—not by which campaign type has the prettier screenshot in the interface.
Strong opinions, lightly held on edge cases—but data hygiene comes first. Here is the sequence I use when this r/PPC debate lands on my desk:
Performance Max vs Search is the wrong question if it forces a false binary. The right question is which risks you can afford this quarter: opacity with scale, or transparency with manual labor. I choose both, on purpose, with fences—because neither Google nor Reddit pays your payroll when quarter-end arrives.