One Product Eats the Whole Budget in PMax
Why Performance Max concentrates spend on a single product and how to diagnose and correct it without losing overall performance.
Written by Mantas Jurgutis — Founder, Adsify — builds the Google & Meta automation merchants use daily
Editorially reviewed by Adsify Editorial on April 8, 2026 — Reviewed against Shopify, Google Ads and Meta official documentation.
This is expected PMax behavior, not necessarily a bug
Performance Max's algorithm optimizes toward the campaign-level goal (conversions or conversion value) across the entire product feed in an asset group, and it will concentrate spend on whichever products it estimates convert most efficiently. If one product genuinely converts far better than the rest, PMax skewing budget toward it is the system working as designed per Google's own documentation. The diagnostic question isn't 'why is this happening' but 'is this the actual best allocation, or is the algorithm being misled by bad signals.'
Check 1: Pull the per-product performance breakdown
In Google Ads, open the PMax campaign and go to the 'Listing groups' or asset-group product-level view (or export via the Insights tab's product-level segmentation). Confirm whether the dominant product actually has a materially better conversion rate and ROAS than the rest of the catalog, or whether it simply has the most impressions with average or below-average efficiency. These are very different situations requiring different responses.
Case A: The dominant product genuinely converts best
If the concentrated product has, say, a 6% conversion rate versus a 2% catalog average, PMax reallocating budget toward it is maximizing the stated goal correctly. The actual problem, if there is one, is that the rest of the catalog isn't getting a fair chance to prove itself, which limits catalog diversification and total addressable revenue even though it's efficient by the immediate metric.
Case B: The dominant product just has better feed signals
Often the 'winning' product doesn't actually convert best — it just has stronger feed data: more reviews synced into the feed, a better product image, more complete GTIN/brand identifiers, or historical performance data (PMax reportedly favors products with an established conversion track record when initially allocating a new campaign). Compare Merchant Center feed quality/diagnostics for the dominant product against three or four other core products to see if this is a data-completeness issue rather than a true demand signal.
Fix for Case B: improve the neglected products' feed quality
Add missing GTINs, improve image quality, ensure size/color variants are structured correctly, and add product ratings/reviews feed integration if not already present, per Google's Merchant Center feed specification. Products with materially weaker feed data than the dominant product will structurally lose the algorithm's confidence regardless of true demand, so equalizing feed quality is often the actual fix, not a budget rule.
Structural fix: split into separate campaigns by product tier
If Case A applies and the imbalance is intentional but you still want other products to get a fair shot, split the catalog into separate PMax campaigns by product tier — for example, a 'hero products' campaign and a 'catalog breadth' campaign — each with its own budget. This is a documented pattern for PMax campaigns with catalogs of meaningfully different margin or conversion profiles, since a single campaign's algorithm can't separately optimize for two very different economics within one asset group.
Worked example: quantifying the concentration
Assume a PMax campaign has 50 products and $1,000 daily budget. If product X alone receives $700/day (70% of budget) and converts at a 5% rate generating $3,500 revenue, while the remaining 49 products share $300/day and convert at a blended 2% rate generating $900 revenue, product X's ROAS is 5x versus 3x for the rest. Redirecting $200 from product X to the rest of the catalog, assuming the same 2% rate holds at higher spend, would generate roughly $500 x 2%/0.02... concretely: additional $200 at 2% conversion and average order value consistent with the $900/300 ratio (~$3 revenue per $1 spend) yields about $600 additional revenue, versus removing that $200 from product X at 5x ROAS which would have generated $1,000. In this case, concentration is mathematically correct and rebalancing would reduce total revenue — always run this comparison before manually intervening.
Use campaign-level exclusions sparingly
You can exclude a specific product from a PMax asset group's listing group if it's cannibalizing budget while genuinely underperforming for reasons unrelated to true demand (for example, a product that's about to be discontinued or is out of stock intermittently). Do this only after confirming via Check 1 that the exclusion target isn't simply your best performer, since excluding your best product to 'force' diversification usually reduces total account revenue.
Set a monitoring cadence, not a one-time fix
Product-level concentration in PMax shifts over time as inventory, pricing, and seasonality change. Review the per-product performance breakdown at least every 2 weeks rather than assuming a fix made once will hold; a product that justified concentration in one season can lose that edge when a competitor undercuts price or when it goes out of stock intermittently, which Merchant Center flags under availability.
Where Adsify fits into this workflow
Adsify's optimizer evaluates profit and POAS at the campaign level every 6 hours using real Shopify cost data, which helps catch a Case A scenario (concentration that's genuinely more profitable) versus quietly bleeding budget on a product whose true margin doesn't match its apparent ROAS.
When to accept the concentration and move on
If Check 1 confirms the dominant product has both better conversion rate and better true margin (not just revenue-based ROAS — see the companion article on ROAS versus profit), the correct action is often to accept the concentration, increase overall campaign budget so the rest of the catalog can still get residual spend, and use a separate campaign only if catalog breadth for its own sake (brand visibility, avoiding single-SKU dependency risk) is a business priority worth some efficiency cost.
Avoiding the common overcorrection
The most frequent mistake here is manually capping or excluding the top-performing product out of a vague sense that 'one product shouldn't get all the budget,' without first confirming via the per-product breakdown whether that concentration is actually the efficient outcome. Always run Check 1 before touching listing groups or exclusions.