OpenAI / ChatGPT Ads for PrestaShop
Product feed, measurement pixel and Conversions API
Troubleshooting
No events appear in Ads Manager
Work through it in this order: in the Tracking tab, confirm Tracking is On and a Pixel ID is set; in the Cron tab, confirm the events job has been called by your scheduler recently (an unscheduled queue is the most common cause); then check the Consent tab, because with a banner and no matching signal, events fire but carry no personal data. If the loader option is on, confirm your consent expression really becomes true after accepting the banner: Try it on the storefront shows its value.
The feed imported but the product count is zero
The import succeeded and the file was read, but the products were filtered out. The usual reason is that product image URLs are not publicly reachable. If a firewall, WAF or hotlink protection blocks automated requests, OpenAI cannot fetch your images and drops those products. Image URLs must return HTTP 200 to OpenAI's crawlers; test one with a crawler user-agent, not just in your own browser, since a browser request often passes where a bot request is blocked.
OpenAI cannot connect to the hosted feed URL
Open the URL yourself with the password. If it works in your browser but not for OpenAI, a CDN or bot-protection rule that blocks AI crawlers is blocking OpenAI's fetcher too; allow it. If Basic authentication never succeeds, your hosting may strip the Authorization header before PHP sees it; either enable CGIPassAuth (or your host's equivalent) or set Hosted feed access to No password, the default.
The feed job stops with a timeout or the run log stays empty
This version lifts PHP's execution limit for the cron job itself, so a plain web timeout should no longer happen. If your hosting enforces a hard limit at the web-server level (for example a proxy that drops connections after 60 seconds), the build continues on the server anyway because the job ignores the disconnect; check the run log a few minutes later. If it is still empty, run the cron URL from the PrestaShop Cron Jobs module or from a real system cron instead of a browser tab.
Some events have no customer data
Expected for visitors who are not logged in and have not reached checkout; there is no identity to attach. Coverage rises through the funnel and is highest on completed orders. If coverage is zero even on orders, re-check the Consent tab and use Check now.
Events do not fire on a customised theme
The module renders through standard display hooks. If your theme has removed displayHeader, displayFooterProduct or displayPersonalInformationTop, restore them so the corresponding events can fire. Checkout-started has a fallback that does not depend on the checkout hook, but product views need displayFooterProduct.
The feed push fails
Use Test connection in the Upload tab: its sentence names the problem (host or port unreachable, login refused, folder missing). Re-check the host, port, user, password and remote directory against Ads Manager, and confirm your server allows outbound connections on the SFTP port. The previous good feed is preserved when an upload fails, so a failed run never leaves OpenAI with a broken catalog. If SFTP keeps failing, hosted-URL delivery needs no outbound connection at all. OpenAI reads the file only from the root of the SFTP server: keep the remote directory at /; the test warns you when it is not.
A product's barcode is missing from the feed
With identifiers switched on, only codes that pass the GTIN check are exported: 8, 12, 13 or 14 digits with a valid check digit. Open the product in PrestaShop and compare the EAN-13 or UPC field with the printed barcode; a typo, a leading or trailing space, or an all-zero placeholder is dropped on purpose so that OpenAI does not flag the whole entry.
I changed a setting and nothing happened
A row is saved only when you click Save or press Enter; it then collapses to ✓ Saved. If a row stayed open with a sentence under it, the value was refused and nothing was saved. If you use a page cache module, clear it: the pixel markup is part of the cached page.
Another employee cannot open the setup screen
The setup screen is a hidden back-office page. The installer's profile and SuperAdmin can open it; other profiles may need to be given access. On PrestaShop 1.7, Advanced Parameters → Team → Permissions may not list the page at all; in that case use the SuperAdmin account to configure the module.
“Check the URL answers” or “Pixel on the homepage” says this server cannot reach itself
Both checks make your server fetch its own public address. Some hosts, firewalls or Docker setups block that, which says nothing about whether OpenAI or shoppers can reach it. The screen says so in one sentence. For the hosted feed, open the URL in your browser and, if it downloads the file with the password, save the task The URL opens in my browser: mark this as done. For the pixel, use Check 2 in section 8 instead.