Google AI Mode Ads Serve Only PMax and AI Max – Both Need Clean Signals

Which campaigns can appear in AI Mode, and which cannot

The eligibility rule is a campaign-type split, and it excludes the campaign type most WooCommerce stores actually run.

Google’s April and May 2026 announcements turned AI Mode into a paid placement surface. The detail that changes account structure is not the format list – it’s who qualifies. Performance Max is eligible. AI Max for Search is eligible. Standard Search, Display and Video campaigns are not eligible for AI Mode placement at all.

Google’s own framing is consistent with that. Announcing Conversational Discovery ads, Highlighted Answers and AI-powered Shopping ads, its guidance was to build a foundation with AI Max for Search, AI Max for Shopping campaigns and Performance Max. Not “consider”. Build.

Campaign type	AI Mode placement	Bidding requirement
Performance Max	Eligible	Smart Bidding (tCPA / tROAS)
AI Max for Search	Eligible	Smart Bidding; manual CPC not eligible
AI Max for Shopping	Eligible	Smart Bidding, Merchant Center feed
Standard Search (keyword)	Not eligible	n/a
Display and Video	Not eligible	n/a

There’s a deadline attached, too. Campaigns using Automatically Created Assets and the campaign-level broad match setting auto-upgrade to AI Max from September 2026, with upgrades expected to conclude by the end of that month. The broader Dynamic Search Ads sunset was pushed back to February 2027 after advertiser feedback, but the September date for those settings still stands.

Google AI Mode ad placements are served only by Performance Max and AI Max campaigns; standard Search, Display and Video campaigns cannot appear there at all.

You may be interested in: Google Is Auto-Upgrading Your Dynamic Search Ads to AI Max in September 2026

What the placement looks like – and what eligibility actually means

Eligibility is not targeting: you cannot bid for AI Mode directly, so the lever you control is the quality of the signal you bring to it.

Be careful with the word eligible. Advertisers cannot currently bid specifically for AI Mode placements. Enabling an eligible campaign type makes your ads available for that inventory, and Google decides what appears. Ads above and below AI Overviews are available across the 200-plus markets where AI Overviews run, while ads inside AI Overviews and in AI Mode started in the US and have been expanding through 2026.

On what the inventory behaves like, the only figures available are third-party tracking rather than platform-confirmed numbers, so treat them as directional: April 2026 tracking suggested advertiser-filled placements in roughly 25.5% of AI Mode results, with engagement around 18% above legacy Search inventory and CPC roughly 35% higher than the standard Search baseline.

Higher engagement at a higher click price is a familiar trade. It resolves on conversion rate and on whether your account can measure it. Paying a 35% CPC premium for inventory you cannot measure accurately is the most expensive version of this transition.

Both eligible types are signal-hungry by design

Performance Max and AI Max replace keyword control with intent inference, which means your conversion data becomes the steering mechanism.

Here’s the thing that makes this a data-infrastructure story rather than a campaign-settings story. AI Max works alongside broad match and Smart Bidding, and manual CPC campaigns are not eligible. Performance Max has always run on Smart Bidding. So the two campaign types that can reach AI Mode are precisely the two that decide where your money goes based on the conversions you report back.

In a keyword campaign, bad tracking mostly produced bad reports – you still controlled which searches you bought. In an AI-driven campaign type, the same gap changes what gets bought. The optimiser cannot know a conversion happened if the conversion never arrived, so it quietly reallocates spend towards the segments whose conversions did register. Blocked and privacy-restricted traffic is not evenly distributed across audiences, so that reallocation is biased rather than random.

Google reports AI Max for Search campaigns averaging 7% more conversions or conversion value at a similar CPA or ROAS when the full feature suite is enabled – search term matching, text customisation and final URL expansion – compared with search term matching alone. That upside is contingent on the optimiser seeing your results.

In an AI-driven campaign type, incomplete conversion tracking no longer just distorts reporting – it redirects spend, because the optimiser reallocates towards whichever conversions happened to register.

The three signal layers Google now expects

Delivery, matching and consent are separate systems, and each one has moved in 2026.

Delivery. The conversion has to reach Google. Client-side tags are intercepted by ad blockers running on 37% of US desktop users, shortened by Safari’s tracking prevention and silenced by consent refusals. Analysis of 18 accounts put server-side conversion capture at 62% to 96%. Sending the purchase from your server rather than the visitor’s browser is the layer everything else sits on.

Matching. Enhanced conversions attach hashed first-party data – email, phone, address – so Google can match conversions that cookies would lose. Advertisers typically see a 5% to 15% increase in reported conversions, and match rates above 50% produce visible Smart Bidding improvement, with US accounts commonly landing between 55% and 70%. A match rate of 0% means enhanced conversions added nothing at all, which is worth checking rather than assuming.

Consent. This is the layer that silently voids the other two. Hashed data only reaches Google when ad_user_data consent is granted, and since 15 June 2026 ad_storage has been the single switch governing advertising cookie collection, cross-device linkage and the signal flow Smart Bidding trains on. Older integrations frequently pass only ad_storage and analytics_storage, omitting ad_user_data and ad_personalization entirely. A consent platform configured with one global default instead of jurisdiction-specific rules can suppress your entire measurement pipeline while every dashboard still renders.

Sitting alongside all three: Google migrated offline conversion imports and Enhanced Conversions for Leads uploads to the Data Manager API on 15 June 2026, and accounts that had not actively used the legacy Google Ads API path are now blocked from it.

You may be interested in: Why Plugin-Based WooCommerce Tracking Undercounts 30-40% of Conversions

What a WooCommerce store should build before September

The sequence matters more than the tooling: fix delivery, then matching, then consent, then measure long enough to trust the result.

The question isn’t whether to move to AI Max. For accounts running Automatically Created Assets or campaign-level broad match, September decides that. The question is what your conversion data looks like on the day the upgrade lands.

A workable order of operations:

• Send Purchase server-side from the order record, not from a script on the confirmation page, so the event exists regardless of what ran in the browser.
• Attach hashed customer data for enhanced conversions, then check your actual match rate rather than assuming the feature is working.
• Audit all four consent parameters, confirming ad_user_data and ad_personalization are present in both default and update calls, with jurisdiction-specific defaults.
• Migrate offline conversion uploads to the Data Manager API if you send back lead quality or downstream revenue.
• Hold the setup for a full month before judging CPA. Smart Bidding needs time to relearn, and a fortnight of data is how good implementations get reverted.

The inPIPE plugin captures the WooCommerce order through server-side hooks and sends it by API to Transmute Engine™, a dedicated Node.js server running first-party on your own subdomain rather than as a WordPress plugin. It hashes identifiers to each platform’s requirement and routes the same validated event to Google Ads, GA4, Meta CAPI and BigQuery together, so the signal feeding Smart Bidding is the same signal you report on.

Enhanced conversions lift reported conversions by 5% to 15% on average, but the hashed data only reaches Google when ad_user_data consent is explicitly granted.

Key Takeaways

• Eligibility is a campaign-type rule: only Performance Max and AI Max campaigns serve AI Mode placements; standard Search, Display and Video cannot.
• September is a real date: Automatically Created Assets and campaign-level broad match auto-upgrade to AI Max from September 2026, with the wider DSA sunset moved to February 2027.
• Eligible is not targetable: you cannot bid for AI Mode directly, so the controllable variable is the quality of the conversion signal you bring.
• Signal steers spend now: both eligible types run on Smart Bidding, so incomplete conversion data redirects budget rather than merely misreporting it.
• Three layers, three failure modes: delivery (37% of US desktop users block tags), matching (aim above a 50% enhanced conversions match rate), and consent (ad_user_data gates the hashed data entirely).
• The API moved on 15 June 2026: offline conversions and Enhanced Conversions for Leads now go through the Data Manager API, with legacy access blocked for inactive accounts.

Frequently asked questions

References

• Google. “We’re upgrading Dynamic Search Ads to AI Max.” blog.google, April 2026.
• Google. “A new generation of ads for the AI era of Search.” blog.google, May 2026.
• Leadgen Economy. “AI Mode ads are becoming a PMax and AI Max surface.” leadgen-economy.com, May 2026.
• TAGGRS. “Google Enhanced Conversions: complete guide.” taggrs.io, June 2026.
• MB Advertising. “Google Ads conversion tracking and attribution.” mbadv.agency, June 2026.
• Notice Me Senpai. “Google Signals June 15 change: consent mode audit guide.” noticemesenpai.com, May 2026.

If September’s auto-upgrade is going to hand your budget to an optimiser, it’s worth checking what data that optimiser can actually see – Seresa builds the first-party layer that feeds it.