OpenAI / ChatGPT Ads for PrestaShop
Product feed, measurement pixel and Conversions API
Verify everything works
Four checks, in order. The first is the module's own list; the other three confirm, from the storefront and from OpenAI's side, what the module cannot see.
Check 1 — the module's own list
Proves: every part of the setup is in place. Open the Health tab or the wizard's last step: the checks that never ran start by themselves, and Run checks refreshes the rest. Every line should be ticked. A warning is not an error: it names something the module could not confirm, such as a scheduler that has not called yet or a check your server could not run on itself. Fix → on a line takes you to the step that fixes it.
Check 2 — the pixel is on your storefront
Proves: the module is rendering and your Pixel ID is set. Open any product page and view the page source (Ctrl+U). Search for oaiq. You should find a script loading OpenAI's SDK, a call to oaiq('init', …) carrying your Pixel ID, and an oaiq('measure','contents_viewed', …) call whose contents ID is the product ID, or product and combination IDs joined by a hyphen. If all three are present, the browser side is working. With “Load the pixel script only after consent” on, the SDK script tag appears only after you accept your cookie banner; the init and measure calls are queued until then.
Check 3 — events reach OpenAI
Proves: data is arriving in your ad account, not just being emitted. In Ads Manager open Conversions → Event Stream, then browse your store in another tab. Events should appear within a minute or two; server-side copies arrive after the next run of the events job.
Check 4 — the feed is delivered and accepted
Proves: your catalog reached OpenAI and passed its processing. In Ads Manager open Feeds and confirm the import is listed with a product count greater than zero. A successful import with zero products almost always means image URLs are unreachable; see Troubleshooting. For hosted delivery you can also open the Hosted feed URL in your browser with the password: it must download a compressed file, not an error page.
What gets tracked
| Store action | OpenAI event | Sent from |
|---|---|---|
| Product page view | contents_viewed | Pixel |
| Add to cart | items_added | Pixel + Conversions API |
| Checkout started | checkout_started | Pixel + Conversions API |
| Order confirmed | order_created | Pixel + Conversions API |
| Account created | registration_completed | Pixel + Conversions API |
| Newsletter signup or contact form | lead_created | Pixel + Conversions API |
| Other key pages | page_viewed | Pixel |
Events sent from both channels share a deterministic event ID, so OpenAI merges each pair into one conversion rather than counting the sale twice. Orders use order_ followed by the order number; add-to-cart uses the cart, product, combination and resulting quantity, computed identically in the browser and on the server; checkout-started is generated on the server and handed to the browser.
Attribution to the ad click
When a shopper arrives from a ChatGPT ad, OpenAI's script stores the click reference in the __oppref cookie. The module reads that cookie and forwards it with every server-side event, so conversions reported through the Conversions API attribute to the click even when the browser pixel was blocked. Nothing needs to be configured for this.