Performance Max shows no conversions: the real causes and fixes

TL;DR

Performance Max (PMax) reporting no conversions — or numbers that don't match the client's sales — is almost always conversion tracking or goal configuration, not a broken algorithm. The usual causes, in order: no conversion action exists or it isn't firing; the conversion goal isn't assigned to the campaign (PMax counts the goals it's told to); the action is set to Secondary/observation instead of Primary, so it doesn't count; Enhanced Conversions / the tag is misconfigured; or it's just attribution + learning delay on a new campaign. Because PMax is a black box (no search-term or placement transparency), broken tracking is more dangerous than usual — Smart Bidding optimises toward phantom conversions or ignores real ones, and you can't see it in the placement data. So the fix is a config checklist plus validating PMax's numbers independently against GA4 and the CRM. Below: the causes and the order to check them.

---

PMax now eats a large share of Google Ads budgets, and "it's spending but showing no conversions" is one of the most common — and most expensive — issues agencies hit. The instinct is to blame Google's AI. Almost always it's something more boring and more fixable: the campaign either can't see a conversion, or isn't being told to count it.

Why broken tracking hits PMax harder

PMax hands targeting, placements, and bidding to Google's algorithm and gives you very little visibility in return — no search terms, limited placement data, asset-group-level reporting at best. That opacity means a tracking problem doesn't show up as an obvious symptom; it shows up as the algorithm optimising toward the wrong thing while the surface metrics look plausible. With a black box, the conversion signal is the steering wheel — feed it garbage and you can't see the car drifting. So getting conversion tracking right matters more on PMax than on any campaign type where you can still read the placements.

The causes, in the order to check them

1. No conversion action — or it isn't firing

The base case: there's no conversion action, or the tag isn't firing on the completion event. Check: Tools → Conversions → is there an action, and does it show recent activity? Use the action's Diagnostics + Tag Assistant on the conversion page. (This is the general Google Ads "no conversions" diagnosis — start there if nothing's recording at all.)

2. The conversion goal isn't assigned to the campaign

PMax counts the conversion goals it's assigned. If the campaign uses account-default goals and your action isn't in that set — or someone set campaign-specific goals that exclude it — PMax spends without counting the conversion you care about. Check: the campaign's conversion goals settings; confirm your primary action is included.

3. The action is "Secondary," not "Primary"

A conversion action marked Secondary (observation) is tracked but does not count toward the campaign's reported conversions or bidding. A misclassified action looks like "no conversions" when it's really "not counted." Check + fix: set the action that should drive the campaign to Primary / account-default.

4. Enhanced Conversions / the tag is half-configured

PMax leans on first-party signal. Enhanced Conversions toggled on but never implemented, a missing Conversion Linker, or stripped gclid/wbraid all degrade or zero out attribution. Check: the Diagnostics tab's Enhanced Conversions status; confirm the linker + auto-tagging.

5. Attribution + learning delay (often it's just time)

A new PMax campaign in the learning phase, view-through and cross-device conversions that resolve days later, and long lead cycles all mean early "no conversions" can simply be not yet. Check: the campaign's age and the conversion window; don't conclude it's broken in week one — but do confirm #1–#4 so you're waiting on real data, not a broken pipe.

6. GA4-import vs native-tag confusion

If conversions are imported from GA4, there's a delay and a definition mismatch vs a native tag — and using both for the same action double-counts. Pick one source per action (covered in the no-conversions diagnostic).

The part most agencies skip: validate PMax independently

Because PMax is opaque and its numbers won't match GA4 or the CRM (different models, windows, view-through), you can't take its conversion count at face value. The discipline:

• Reconcile PMax conversions against GA4 and the client's CRM/back-office on a cadence. A gap that grows is a tracking problem, not a quirk.
• For real spend, run an incrementality test — PMax is notorious for claiming credit for brand and existing-demand conversions it didn't cause. Attribution flatters it; a holdout tells the truth.
• Treat "PMax says X conversions" as a claim to verify, the same verify-don't-trust posture as everything else — only more so, because you can't see the placements.

The fix checklist

1. Conversion action exists + fires (Diagnostics / Tag Assistant)?
2. The right goal is assigned to the campaign?
3. The action is Primary, not Secondary?
4. Enhanced Conversions implemented + Conversion Linker + auto-tagging intact?
5. Given enough time (learning + conversion window) before judging?
6. One source per action (native tag or GA4 import)?
7. PMax's numbers reconciled against GA4 + the CRM — and incrementality-tested for big spend?

Where this fits

PMax concentrates budget behind an algorithm you can't see into, which makes the conversion signal — and its correctness — the whole ballgame. Phloz models each client's conversion setup (actions, goals, Enhanced Conversions, the GA4/CRM reconciliation) as part of the tracking-infrastructure map with a health state, so "is this client's PMax actually counting real conversions, or steering on noise?" is a view, not a quarter-end surprise. The CRM for PPC agencies and pricing pages cover the workflow — but the rule for PMax is sharper than usual: fix the conversion config, then don't trust the black box's number until you've checked it against reality.