For about a decade, "where does a PrestaShop sale begin?" had a boring, stable answer: someone typed a query into Google, saw an ad or a Shopping card, and clicked. That answer is now splitting in two directions at once. As reported in 2026, OpenAI has begun putting paid placements inside ChatGPT and started rolling out a self-serve ads manager to selected US advertisers; Anthropic has done the opposite, publicly committing that Claude will stay ad-free and running a Super Bowl spot to say so out loud. Two of the most widely used AI assistants took opposite bets on advertising within the same stretch of 2026.
This post is specifically about what those two announcements mean for the marketing decisions you make inside your PrestaShop store this year — not a general "AI is changing everything" essay. We'll look at how ChatGPT ads actually behave (they are not search ads), why Claude's ad-free stance still affects you even though you can't buy anything there, and what concretely changes in your back office, your product feed and your measurement setup. The how-to of Google Ads itself lives in its own cluster; we'll point you to those guides rather than rehash them here.
What ChatGPT ads actually are (and why they aren't Google Ads)
ChatGPT ads went from a closed test in early 2026 to a self-serve ads manager that selected US advertisers can access during the rollout. The mechanics matter, because they're different enough from Google that copying your Search strategy across will misfire:
- They're triggered by intent, not an exact keyword. A Search ad fires on a query string you bid on. A ChatGPT placement surfaces when the conversation has commercial intent — the customer might describe a problem ("my checkout keeps losing mobile customers"), a budget, or a comparison, never typing a product name. Early reports suggest the targeting is more contextual than keyword-exact, leaning on broad thematic signals rather than an exact-match keyword list.
- The format is a sponsored block inside the answer. Reported formats are a short "Sponsored" text unit (a headline of roughly 40 characters, a description around 150) and, for product-style queries, a shopping card with price and availability. Product-style formats look likely to require structured product data or a feed integration once OpenAI documents the requirements.
- Advertiser reporting looks more aggregated than Google Search. Expect measurement that is more privacy-limited than the granular query reports you're used to in Google Ads, with chat content staying inside ChatGPT. Measurement comes from a site-side pixel and a server-side Conversions API that report events (purchase, signup, lead) — closer to a privacy-walled feed than a search-terms report. Check OpenAI's official ad measurement documentation for the specifics as they are published.
- Paid subscribers don't see ads. As of 2026, ads are limited to the free and lower tiers, so the addressable audience sits there rather than across paid plans.
The "so what?" for a store owner: this is a channel where your product data and landing pages do the selling, because you can't lean on tight keyword control or rich audience signals to compensate for a weak page. That is the opposite of where most under-pressure ad accounts hide their problems.
How ChatGPT ads compare to the channels you already run
Before you decide whether to touch this, it helps to see where it sits next to the Google surfaces you (hopefully) already understand. None of these replaces another — they capture demand at different moments.
| Channel | Triggered by | Targeting control | Data you get back | What it's best at |
|---|---|---|---|---|
| Google Search Ads | An exact query a person types | High — keywords, match types, negatives | Rich — search terms, devices, audiences | Capturing explicit, in-the-moment demand |
| Google Shopping / Performance Max | Product-intent queries, fed by your Merchant feed | Medium — driven by feed quality + signals | Moderate — increasingly aggregated | Putting products in front of comparison shoppers |
| ChatGPT ads | Commercial intent inside a conversation | Low — broad thematic context, no exact keywords | Minimal — pixel/Conversions API events only | Reaching buyers mid-research who never type a product name |
| Claude | n/a — no ad inventory | None to buy | None | Influence flows only through your public, machine-readable content |
Read across that bottom-right column and the strategy writes itself: in three of these four surfaces, the lever you most control is the quality and machine-readability of your product data and pages. That's the work that pays off everywhere, which is where a PrestaShop merchant should spend first.
Why Claude's ad-free stance still affects your store
It's tempting to file "Claude won't run ads" as someone else's business model and move on. Don't — because it tells you how customers will reach you through an assistant you can't buy your way into. If Claude (and any assistant that follows its lead) surfaces products without sponsored placements, then the only way your store appears in those answers is through your public footprint: structured product data, clear descriptions, clean canonical URLs, an accurate feed, and content that genuinely answers the buying question. There is no ad budget that shortcuts it.
So the two announcements point at the same conclusion from opposite directions. ChatGPT ads reward stores with strong product data (because the page does the selling). Claude's ad-free model rewards stores with strong product data (because that's the only way in). For a merchant, that convergence is clarifying: the unglamorous work of getting your catalogue clean and readable is now the highest-leverage marketing investment you can make, and it pays across paid AI, ad-free AI and Google alike.
Don't declare Google Ads dead
None of this is a reason to pause a profitable Google account. Google still captures the clearest signal in commerce — a person typing an exact product, part number, module name or local service is telling you precisely what they want. AI ads may grow fast, but they don't erase the value of keyword structure, product feeds, landing pages and conversion tracking. The practical mistake would be moving budget out of a channel with measurable profit into one you haven't measured yet because it's new.
If you're still building the Google foundation that every one of these surfaces depends on, start there rather than chasing the AI headline:
- New to paid search entirely? Google Ads for beginners: your first campaign without wasting money.
- Your product feed is the raw material every shopping surface (Google and ChatGPT) consumes — get it right with Google Merchant Center feed optimization for PrestaShop, and fix rejections via fixing Merchant feed errors and disapproved products.
- Deciding between Search and Shopping, or how they work together: Google Search Ads alongside Shopping campaigns and why exact keywords are gold for niche stores.
- Letting Google's automation spread budget across surfaces: Performance Max for PrestaShop.
- Sizing the spend before you add any new channel: choosing the right Google Ads budget.
What to fix in PrestaShop before you test any AI ad
Because ChatGPT placements lean on product data and a measurement pixel, and because Claude-style assistants lean on your public content, the prep work is concrete and lives mostly in your back office. Here's the PrestaShop-specific checklist:
- Conversion tracking that you can trust. Before you judge any new channel, your existing numbers have to be reliable. In PrestaShop that means the order-confirmation tracking fires once and only once. The common front-office confirmation hook is displayOrderConfirmation, fired by the OrderConfirmationController on the genuine order-confirmation page, not on a "thank you" CMS page a customer can refresh — though that page can still be reloaded, so server-side purchase tracking should deduplicate by order ID and may use validateOrder or other order-lifecycle hooks. If GA4, Google Ads and your server-side events show large unexplained gaps, investigate that first; small differences are normal, since these systems use different attribution windows, consent handling, deduplication and processing rules. A new ad surface layered on broken measurement just produces confident nonsense.
- A feed that explains products, not just names them. Google Shopping consumes structured product data from your Merchant Center feed; ChatGPT's product-style cards look likely to rely on structured product data too, though the exact feed requirements aren't established yet and may differ from Google's. Either way, clean product data is the prerequisite. In PrestaShop, that means filling Catalog → Products properly: real titles, the identifier fields PrestaShop actually exposes — EAN-13/UPC, ISBN, MPN and Reference on the product's Details tab (and per-variant on the Combinations tab) — accurate stock and price, and categories that actually describe the product. A feed module that maps these PrestaShop fields cleanly to feed attributes does the heavy lifting. Provide a GTIN (EAN/UPC) whenever the product has one; if it genuinely has no GTIN, provide brand plus MPN where applicable, and set identifier_exists correctly only for truly identifier-free products. Missing or inconsistent identifiers are a common reason products go unmatched in Shopping.
- Landing pages that answer the buying question. Conversational discovery starts with a problem ("which payment option is safer for my customers?"), not a SKU. A product page that only repeats the manufacturer blurb gives an assistant nothing to work with. Use PrestaShop's full description (not just the short one) to answer who the product is for and when it's the right choice — the same depth that helps a human helps a machine summarize you fairly. (This is also exactly the discipline our feed optimization guide argues for from the Shopping side.)
- Trust signals visible before checkout. Delivery, returns, support and payment methods should be on the page, not buried in a CMS footer link. An assistant summarizing your store and a shopper arriving from any ad both look for the same reassurance.
- Technical SEO hygiene. Canonical URLs, hreflang for multi-language stores, schema markup and a fresh sitemap are important hygiene when public content is the interface to your store across discovery systems — including the ad-free ones — and they reduce ambiguity for crawlers and assistants. PrestaShop's Shop Parameters → Traffic & SEO covers canonical and URL settings; structured data usually comes from your theme or a dedicated module.
Notice how much of that is the same list whether the next click comes from Google, ChatGPT, Claude or a comparison site. That's the point: you're not building four marketing stacks, you're making one store legible to all of them.
How to actually test ChatGPT ads without betting the budget
If your fundamentals are solid and you want to experiment, treat it as a measured trial, not a strategy shift:
- Install the measurement first. Set up the site-side pixel and the Conversions API before the first dollar — for a server-side store that means firing the purchase event from the order-confirmation flow, so it survives ad-blockers and matches what your PrestaShop back office actually recorded as a valid order.
- Group products by buying intent, not by category tree. Conversational queries cluster around problems and use-cases; a campaign structured the way your PrestaShop category nesting happens to be won't map to how people ask.
- Ask the incrementality question, not the replacement question. The test isn't "can this replace Google?" It's "does this bring demand I wouldn't have reached through Search, Shopping, email or direct?" Compare assisted as well as last-click revenue — AI ads may influence research that converts elsewhere.
- Protect brand trust. Don't let an ad promise stock, delivery, support or compatibility your store can't actually honor. A returning customer who got burned once costs you more than the click saved.
The merchant takeaway
The genuinely useful read on these two announcements isn't "pick an AI company." ChatGPT now has ad inventory; Anthropic currently positions Claude as ad-free and has publicly committed to keeping it that way for now; both raise the value of the same boring, durable work. Customer attention is going to keep splitting — across ad-supported AI, ad-free assistants, Google Search and Shopping, social, marketplaces and direct traffic — and no single channel is safe to depend on. The stores that adapt easily will be the ones whose product data is clean, whose pages answer real questions, and whose tracking produces numbers you can act on.
If your PrestaShop store already has that discipline, AI advertising is simply another opportunity to test on your terms. If it has broken feeds, messy analytics and thin product pages, AI won't fix that — it'll just make the weaknesses more visible to more discovery systems at once. So the winning setup for 2026 looks reassuringly unfashionable: clean data, clear pages, reliable tracking, and careful budget control. Build that, and you're ready for whichever way the next assistant bets.
Comments
No comments yet. Be the first!
Be the first to ask a question or share useful feedback.
Leave a comment
Share a question, an installation detail, or feedback that could help another reader.