Get your PMax not converting tracking to 95%+ accuracy guaranteed in writing.
Both failures come from the same place: PMax bids on whatever signal you hand it, and most accounts hand it a default pixel with no value, no primary goal and no feedback loop. We rebuild the money event server-side, align it with the feed and your CRM, then reconcile what the campaign claims against what your order table actually contains.
Free30 minutesNo obligation
PMax not converting · what breaks
Why PMax has nothing to optimize toward
- 01
Nothing in the account is set as a Primary goal
Only Primary conversion goals feed Smart Bidding. If Purchase or Qualified Lead sits under Secondary — or the campaign inherited account-default goals nobody reviewed — PMax reports on one thing and bids on another.
- 02
Every conversion is worth the same to the algorithm
When the tag sends value 0, or a hardcoded $50 on every order, Max Conversion Value has nothing to rank clicks by. PMax spreads budget evenly across cheap and expensive customers because it can't tell them apart.
- 03
PMax claims conversions your order table doesn't contain
View-through credit on Display and YouTube inventory, brand search absorbed into the campaign, and a conversion action set to count "Every" instead of "One" all inflate the number. The campaign banks all of it as its own.
- 04
Merchant Center and your purchase event use different IDs
If item_id in the purchase event doesn't match the feed's id or offer_id, including at variant level, conversions never attach to products. Listing groups and asset groups get no product-level feedback at all.
PMax not converting · the fix
What changes once PMax is bidding on something real
One Primary goal that means what you think it means
The campaign optimizes toward the conversion that represents money — not a newsletter signup, not a scroll-depth event someone imported from GA4 three years ago and left as Primary.
Value-based bidding with values that are actually true
Real transaction or contract amounts, in the right currency, on every conversion. tROAS and Max Conversion Value stop being aspirational settings and start ranking clicks by what they're worth.
PMax conversions you can find in your order table
We match campaign-reported conversions to orders by transaction ID and date, then name each gap: view-through, brand overlap, duplicate counting, or genuine data loss. Four different problems, four different fixes.
Audience signal built from customers, not from visitors
A Customer Match list from your actual purchase history — refreshed on a schedule, not uploaded once — attached as asset-group signal, which is the input PMax has the least of by default.
PMax not converting · normal or broken
Week one silence is normal. Conversions your orders can't find aren't.
PMax has two failure modes that look identical on the dashboard and are nothing alike. One is a campaign that hasn't been given enough conversions to learn from yet. The other is a campaign confidently bidding on a signal that isn't true.
Normal, not a fault
A brand-new PMax campaign reporting nothing in week one
Google's own guidance sits around 30 conversions in 30 days per campaign before Smart Bidding has much to work with. Early silence is the ramp. Rebuilding tags mid-ramp just adds a variable you can't isolate later.
PMax conversions will not match GA4 conversions
Google Ads credits the click's campaign inside its own window and can include view-through; GA4 applies its own model to sessions. These two numbers never agree on any account, and a rebuild won't make them.
Spend lands on Display and YouTube you didn't pick
PMax allocates across channels itself. Cheap impressions with few clicks showing up in the asset report is the channel mix doing its job — unless the same campaign is also absorbing your brand search.
Conversions are dated to the click, not the sale
Google reports a conversion back on the day of the click, so yesterday's numbers keep filling in for days afterward. A report that backfills is correct. A report that never backfills is worth a look.
Actually broken
PMax reports purchases your order table has never seen
After you allow for view-through and cross-device, if reported conversions still can't be matched to any order by ID and date, the event is firing on something that isn't a sale — a refreshable thank-you page, or test orders.
Conversion count exactly doubles on a subset of days
Two tags counting the same event, usually a hardcoded gtag left in the theme alongside the GTM tag, both set to count "Every". One order, two conversions, and Smart Bidding believes both of them.
Every conversion carries the same value, or zero
Value-based bidding with a constant value is bidding with no value at all. Max Conversion Value can't rank a $40 customer against a $4,000 one, so it spreads budget evenly and a tROAS target becomes decoration.
Product reporting is empty while purchases record
Purchases are landing but no listing group or individual product shows any conversions. That's item_id in the purchase event failing to match the Merchant Center feed's id, usually at variant level.
PMax not converting · diagnose
Four console checks that separate learning from a broken signal — PMax not converting
All of this is readable inside Google Ads and one spreadsheet, and it tells you whether to wait or to rebuild.
- 01
Open Goals and read what is actually Primary
Google Ads, then Goals, then Summary. Write down every Primary conversion action and whether the PMax campaign uses account-default goals or its own. Anything Primary that isn't money is noise you're paying to optimize toward.
- 02
Check the counting setting on your money action
In the conversion action's settings, "Every" is right for ecommerce and wrong for lead gen. A lead action set to Every counts one person submitting the form three times as three conversions, and PMax bids accordingly.
- 03
Match seven days of PMax conversions to your orders
Download the conversion segment by day, pull the same dates from Shopify, Stripe or your order table, and compare counts first and transaction IDs second. Write the gap down before you theorize about it.
- 04
Split that gap by cause before blaming any tag
Segment the Ads report by conversion action, device and network, then read the view-through and cross-device columns. Model differences explain part of it. Whatever is left over is the technical part, and only that part needs fixing.
- 05
Check brand terms in the PMax insights report
PMax, then Insights, then search categories. If your own brand name is driving a large share of the conversions, the campaign is banking demand you already had rather than creating any.
- 06
Confirm one item_id resolves in Merchant Center
Take a single purchase event out of GTM Preview, copy its item_id exactly, and search Merchant Center for that string. Variant-level mismatches are the common failure and they never announce themselves.
PMax not converting · prove
How we prove PMax is counting sales you actually made
The number that matters isn't in Google Ads. It's in your order table, and every claim we make gets checked against it row by row.
Source of truth
Shopify or Stripe order records · your CRM closed-won
- Place a real test purchase and confirm exactly one conversion arrives with the correct value, currency and transaction_id.
- Match a full week of PMax-reported conversions to order IDs and record the match rate before and after the rebuild.
- Label every unmatched conversion as view-through, cross-device, brand overlap, duplicate counting, or genuine data loss.
- Compare total reported conversion value to your own revenue for the same window, on a cash basis, and explain the delta.
- Check Merchant Center diagnostics for unmatched item IDs once the feed mapping is live, at variant level not parent level.
- Re-run the same reconciliation 30 days later so a silent regression surfaces in weeks instead of at the quarterly review.
PMax not converting · free audit
What we check in the free audit
- Open Goals and read what is actually Primary
- Check the counting setting on your money action
- Match seven days of PMax conversions to your orders
- Split that gap by cause before blaming any tag
- Check brand terms in the PMax insights report
- Confirm one item_id resolves in Merchant Center
Checked against
Shopify or Stripe order records · your CRM closed-won
Free30 minutesNo obligation
PMax not converting · when not to buy
When PMax doesn't need a rebuild
Half the accounts that ask us about dead PMax campaigns have a volume problem or a patience problem, not a tracking problem.
- The campaign launched under two weeks ago with almost no conversions yet. That's learning. Changing the tags now makes it un-diagnosable.
- A week of PMax conversions already matches your orders row for row. The measurement is fine; the problem is the offer, the feed or the creative.
- You're under roughly 30 conversions a month. Consolidating campaigns will move more than re-architecting the data pipeline will.
- You run lead gen with no qualification stage recorded anywhere. Build that first — there is nothing meaningful to send back to Google yet.
PMax not converting · what we deliver
What we rebuild before PMax gets another dollar
A conversion goal audit, action by action
Every conversion action listed with its category, counting setting, attribution window, Primary/Secondary status, and whether the campaign uses account-default or campaign-specific goals.
One money event, fired from your backend
purchase or qualified_lead sent server-side with transaction_id, value and currency, so PMax counts the thing that actually happened rather than a thank-you page someone can refresh.
Enhanced Conversions on every PMax conversion action
PMax has no keyword-level data to work with, so hashed customer data carries more of the matching load here than in Search. Wired for both web conversions and Leads.
item_id aligned to the Merchant Center feed
Purchase and view_item item IDs mapped to the feed's id and offer_id at variant level, then confirmed in the diagnostics panel rather than assumed.
A Customer Match list on a refresh schedule
High-value customer segments pulled from your CRM or order history, hashed, uploaded, and attached as audience signal — with a job that keeps them current instead of a one-time CSV.
A backend reconciliation report
PMax-reported conversions against your own orders for the same window, side by side, with each discrepancy explained. This is the deliverable clients keep coming back to.
Written guarantee
95%+ tracking accuracy
Measured against Shopify or Stripe order records · your CRM closed-won. Miss it and we keep working at no cost.
FAQ
PMax not converting questions, answered
Part of it, today, for free. Go set exactly one Primary goal, check whether your conversion action counts Every or One, and turn on Enhanced Conversions. That's console work and it fixes a real share of dead PMax accounts. What's harder is the part that decides whether PMax ever works: a server-side money event carrying true values, item IDs that match the feed, and a reconciliation you actually trust. If you have a developer who can fire an event from the order backend, you can get most of the way alone.
Usually neither — they're counting different things. Google credits view-through impressions on Display and YouTube placements, counts cross-device journeys your database can't see, and may be absorbing brand searches that would have converted anyway. Your order table counts orders. The useful move isn't picking a side, it's matching them row by row so you know how much of the difference is model versus how much is broken tags.
Defensible, with a caveat. Spending into a broken signal teaches the algorithm the wrong lesson every day, so pausing isn't crazy. But restarting puts the campaign back into learning, so don't pause on Monday and relaunch on Wednesday. If you're going to pause, pause until the rebuild is verified, then relaunch once with the signal correct.
Google's own guidance sits around 30 conversions in 30 days per campaign for Smart Bidding to have something to learn from. If you're well under that, consolidating campaigns and bidding on an earlier pipeline stage will do more than any tagging work. I'd rather tell you that than sell you a rebuild that can't help.
Yes, and the failure is worse there. Lead-gen PMax typically bids on form fills, which is the one signal that's easy to fake and easy to flood. The money event for lead gen is the qualified stage, returned to Google by offline upload. Without that loop, PMax optimizes toward whoever fills forms fastest, which is rarely who buys.
We do, but only on data we've rebuilt and verified — never on inherited numbers. Plenty of clients have us fix the measurement and keep their existing team or agency running the account, and that's a perfectly good outcome. The rebuild stands on its own.
If PMax is hitting a ROAS or CPA you're happy with, and spot-checking a week of reported conversions against your orders lines up cleanly, leave it alone. Also if total account spend is small — at low volume, campaign consolidation and offer work beat re-architecting the data pipeline, and I'd tell you so on the call.
More on PMax not converting
- GuidePerformance Max and Conversion Tracking: Why PMax Lives or Dies on Your Data
- GuideConversions Look Fine but Smart Bidding Performs Badly? Your Data Is Lying
- GuideHow Accurate Is Your Conversion Tracking? Here's How to Actually Measure It
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- LinkedIn CAPILinkedIn tracking that reports pipeline, not form fills
Free · 30 min
Let's find out how many of those PMax conversions are real
Free30 minutesNo obligation
