Fix: Too many Performance Max campaigns competing for the same conversions

Running ten Performance Max campaigns when your account only generates 120 conversions a month is the structural mistake that keeps every campaign starved — Google's matching engine never sees enough volume per campaign to exit its learning window, so each one runs on partial signal forever. Consolidate before tuning anything else.

Why this matters

Performance Max relies on per-campaign conversion volume to train its Smart Bidding and creative-assembly models. Google's own documentation states the account cap is 100 PMax campaigns but recommends "consolidating your Performance Max campaigns where possible" for best performance.[1] The mechanism is straightforward: each campaign maintains its own bidding signal and learning state, so 10 campaigns sharing 200 monthly conversions train on 20 conv/campaign — well below the Smart Bidding learning phase exit threshold of ~50 conv/30d for Max Conversions and 30/wk for tCPA.

The cost compounds. Each starved campaign continues serving impressions but optimizes against noise; cost-per-conversion drifts upward because the matcher cannot stabilize. Optmyzr's analysis of thousands of accounts found the typical performant structure was 3 PMax campaigns per account, and that campaigns failing to clear 60 conversions in a 30-day window underperformed across the board.[2] The same study found 4 asset groups per campaign as the typical-account median — over-segmentation at the campaign level usually drags asset-group sprawl along with it (see the sibling Fix: PMax asset group consolidation, which handles asset-group-level segmentation as a distinct unit of analysis).

The Whitead rule fires when an account has 5 or more active PMax campaigns and the median per-campaign monthly conversion count falls below 60. Both conditions must hold — 5 campaigns each clearing 60+ conversions is a healthy segmented account (likely splitting by margin tier or geo), not a finding.

How to verify the issue

1. Open Campaigns → filter by campaign type = Performance Max → status = Enabled. Count the active rows.
2. Add the columns Conversions and Cost / conv. and set the date range to the Last 30 days. Note the per-campaign conversion count.
3. Compute the median. If 5+ campaigns have a median below 60 conversions, signal pooling is broken.
4. Check Status column for each campaign — Eligible (Learning) on a campaign more than 14 days old usually means it never accumulated enough signal to exit learning. See the Fix: Campaign stuck in Smart Bidding learning finding for the related single-campaign symptom.
5. Open Insights → Audience insights per campaign. If overlapping audience segments appear across multiple PMax campaigns, you are forcing Google to allocate the same in-market user across competing auctions you own.

If steps 1-3 confirm 5+ campaigns and median conv/30d below 60, the finding is real. Step 5 reinforces the diagnosis by showing audience-level overlap.

How to fix it

The fix is structural, not configurational. Plan a 2-3 hour session with stakeholders before pausing or merging anything.

1. Map every PMax campaign to its conversion goal and margin tier. Two campaigns with the same primary conversion action and the same margin range are consolidation candidates. Two campaigns with distinct tROAS targets (e.g., 400% for high-margin SKUs, 200% for clearance) are NOT — the bid strategy itself differentiates them.
2. Score each campaign for splitting justification. Valid reasons to keep separate: (a) distinct margin tier or tROAS target, (b) distinct geographic budget pool, (c) distinct conversion action (e.g., lead-gen vs ecommerce purchase), (d) distinct ad-policy constraint (e.g., regulated product in one geo only). If a campaign fails ALL four tests, it is a consolidation candidate.
3. Merge consolidation candidates into the most established campaign. Pick the campaign with the longest history and highest conversion volume as the survivor. Move surviving asset groups, search themes, and audience signals into it — but do NOT duplicate asset groups verbatim. Use the consolidation moment to also prune to 3-5 asset groups per campaign, per the Fix: PMax asset group consolidation guidance.
4. Pause (do not delete) the merged-away campaigns. Pausing preserves history for change-tracking and lets you revert if the consolidation tanks performance. Wait at least 21 days before deletion.
5. Re-baseline the budget on the survivor. Sum the daily budgets of the consolidated campaigns minus 10-15% (you typically need less total spend once signal pools, because CPA stabilizes). Set the new budget on the survivor and let it run through a full Smart Bidding learning phase before judging.
6. Verify exit from learning. After 14 days, the survivor should show Eligible (not Eligible (Learning)) in the Status column with conv/30d above 60.

"You can create up to 100 Performance Max campaigns in your Google Ads account. For the best performance, we recommend consolidating your Performance Max campaigns where possible."
— Google Ads Help, About Performance Max campaigns [1]

Edge cases — when NOT to consolidate

• Distinct margin tiers or tROAS targets. A 600% tROAS premium-product campaign and a 250% clearance campaign cannot share a bid strategy — keep them separate even at lower per-campaign volume.
• Geographic budget separation required by stakeholders. Country-level budget pools (US vs EU vs APAC) often must stay split for billing or regional-team ownership reasons.
• Distinct conversion actions with different values. Lead-gen (cost-per-lead $80) and ecommerce purchase (AOV $250) are different optimization surfaces — do not merge.
• Regulated-product constraints. If one campaign serves a category restricted in certain geos (e.g., financial services, alcohol), keeping it isolated simplifies policy management even at the cost of signal pooling.
• Account is freshly launched. If every PMax campaign is under 14 days old, the audit does not yet have enough history to call this — wait for the learning phase baseline.

Industry benchmarks

• 3 PMax campaigns per account = typical healthy structure across Optmyzr's sampled dataset.[2]
• 60+ conversions per 30 days = minimum for a PMax campaign to perform effectively.[2]
• 4 asset groups per campaign = typical median; accounts exceeding this saw worse performance metrics.[2]
• 100 PMax campaigns = absolute Google account cap, not a target.[1]

How to confirm the fix worked

Diagnostic checklist — run 14-21 days post-consolidation

• Active PMax campaign count is 5 or fewer (or, if more, every campaign clears 60 conv/30d).
• Median conv/30d per campaign ≥ 60 across all active PMax campaigns.
• Surviving campaigns show Status: Eligible (not Eligible (Learning)).
• Cost-per-conversion on the survivor is within ±15% of the pre-consolidation weighted-average (no runaway CPA from the merge).
• No two active PMax campaigns share the same primary conversion action AND same margin tier — splits that remain are intentional.

If all five pass, re-run the audit — the pmax_over_segmentation rule moves from failed → passed.

Related rules + concepts

• Performance Max — the campaign type this finding restructures.
• Fix: PMax asset group consolidation — sister finding at the asset-group level (within-campaign segmentation, not campaign-count).
• Fix: Campaign stuck in Smart Bidding learning — the single-campaign symptom that over-segmentation causes at scale.
• Smart Bidding learning phase — the mechanism that breaks when per-campaign signal is starved.
• PMax low ROAS diagnostic — broader playbook when over-segmentation is one of several root causes.

Sources

1. Google Ads Help — About Performance Max campaigns. https://support.google.com/google-ads/answer/10724817 (accessed 2026-05-27)
2. Optmyzr — Performance Max Study: Evaluating Popular Strategies For ROI. https://www.optmyzr.com/blog/performance-max-study/ (accessed 2026-05-27)