August 17, 2026 - 5 min read
How one PMax campaign can fail in five places at once
A Performance Max campaign reports one blended number, and that number is technically accurate at every level it is asked to summarize -- network, language, asset group, creative mix, search category. It is also exactly why the same campaign can be quietly failing in more than one of those five places at once, with the headline CPA still reading as healthy, because each individual drift is small enough on its own to hide inside an average built to absorb exactly that kind of variation.
Five places to look, not one
Five separate checks catch five separate problems, and none of them share a symptom with the others. A network-level split can show spend drifting toward Display, Video, Discover, Gmail, and Maps without a matching share of conversions. A search-category breakdown can turn up scripts the account was never built to serve -- Cyrillic or Chinese characters inside a campaign targeting a Latin-script market -- with no cost figure attached to flag it, since Google does not report spend at that level. Asset-group spend can concentrate almost entirely into one group, or sit in a second group burning real budget with zero conversions, both invisible at the campaign-level total. A creative mix built entirely from images has nothing to serve well on video-first inventory, a gap that shows up as underperformance with no obvious cause. And a set of search categories, each individually too small to notice, can together account for a real share of impression volume while contributing zero conversions between them.
A worked example that touches more than one blind spot
Illustrative case: a PMax campaign has been running for two quarters with a stable, on-target CPA. A full pass across all five checks turns up two problems at once, not one. First, Display and Discover together have grown from a fifth to nearly half of spend over the two quarters, absorbing cost without a matching share of conversions. Second, the asset group carrying most of that browse-and-discovery inventory is also the group with the fewest video assets in the account -- it is leaning on image-only creative to serve placements that reward video, which is part of why its conversion rate lags the group that still gets most of its reach on Search. Read separately, neither check alone fully explains the gap between spend and return. Read together, they are the same underlying pattern seen from two directions: budget has drifted toward inventory the campaign's own creative mix is not equipped to convert on.
Why the five compound instead of staying separate
The five blind spots are not five unrelated risks that happen to share a campaign type. Concentration in one asset group means that group's own network mix, language drift, and creative gaps now dominate the whole campaign's blended read, since it is carrying most of the spend. A campaign quietly leaning into browse-and-discovery inventory is, by the same shift, more exposed to whatever creative or language gaps exist in that inventory specifically -- the checks are not independent, they are five angles on the same underlying question: where is this campaign's budget actually going, and is what it finds there equipped to convert it.
The order worth checking them in
Not every check deserves equal first-look priority. Concentration and waste at the asset-group level are the fastest read, since spend and performance labels are both visible in Google's own interface without a manual cross-reference -- start there, because a concentrated or wasteful asset group changes what the other four checks even mean: a network-mix drift concentrated inside the dominant asset group is a bigger problem than the same drift spread evenly across a balanced campaign. Network mix and creative coverage follow naturally, since a concentrated asset group's placement mix and creative gaps are now, in practice, the account's placement mix and creative gaps. Language and search-category checks come last, not because they matter less, but because they need a wider data pull -- impressions and clicks with no cost figure attached to either one -- and are better run as a scheduled quarterly pass than a first-response check on a campaign that just missed its CPA target.
When the five are actually unrelated
Not every PMax account with more than one blind spot has a single underlying cause. A campaign can have a genuinely wasteful asset group and, in a completely separate part of the same account, a language-leakage pattern that has nothing to do with the asset-group concentration -- two real problems, two different fixes, no shared root cause connecting them. Treating every combination as one compounding story risks a different mistake: fixing the wrong thing first because a plausible-sounding connection was assumed rather than checked. The compounding pattern in the worked example above is common, not universal -- each of the five checks still needs to be read on its own evidence, not assumed to trace back to whichever problem happened to be found first.
A checking cadence that covers all five
None of the five shows up as a red flag in Google's own interface, because none of them is technically an error -- a network split, a search category, an asset group, and a creative mix are all just PMax doing what it is built to do: expand automatically and report one blended result. That is exactly why a one-time check is not enough. The drift compounds quarter over quarter, and the fix is not distrust of PMax's automation, it is a recurring pass -- network split against conversions, search-category floor for cost-free volume, asset-group balance for concentration and waste, and creative coverage for the placements the mix cannot serve -- run on a cadence the platform itself never prompts, not discovered once and assumed to hold from then on. For an agency running PMax across a whole portfolio, that repeatability matters even more than the individual checks do: a structural, repeatable pass is the only version of this that scales past one account.
Related reading
See how the Decision Framework applies to your own accounts.
Request a demo