Prepare your catalogue for ChatGPT Ads product campaigns in 2027: reliable data, eligible products, updates and a purchase you can measure. This planning edition uses documentation reviewed on 14 October 2026; account access must be confirmed.
The business decision is which part of the catalogue merits investment and how its result will be checked. This guide connects that decision with the technical requirements. Our ChatGPT Ads ecommerce service turns it into a defined catalogue, measurement and management project.
A product feed organises catalogue data for product ads. The work starts with store data and ends with the relationship between ad, product page, checkout and order. That chain needs to remain coherent when products change.
OpenAI’s Product Feeds documentation describes the workflow for accounts with access. Confirm the account, markets and enabled features before committing to a launch date.
The product schema separates advertising eligibility from search eligibility. is_ads_eligible controls Ads processing in the OpenAI format and does not replace search settings.
Plan separate objectives: the catalogue to advertise, the customer’s destination and how organic presence will be assessed. Campaign delivery measures advertising; it does not establish that a ChatGPT answer recommends the brand.
| Data | Responsible source | Useful check |
|---|---|---|
| ID and variant | Catalogue or PIM | The identifier retains the same product |
| Title and description | Product team | The customer understands what is sold |
| URL and image | Ecommerce | Destination and image represent the variant |
| Price and currency | Commercial system | They match the product page |
| Availability | Agreed inventory source | The ad does not promise unavailable stock |
| Eligibility | Campaign owner | The selection is approved for the market |
This is a working checklist, not the complete ingestion contract. Check required fields and values against the current schema. Assign an owner for each issue before automating.
The Advertiser API workflow describes feed creation, SFTP configuration and compatible file ingestion. Confirm available Ads Manager options in the account; this guide does not assume every account has the same interface.
For 2027 planning, define the ongoing operation: who generates the catalogue, detects failures, submits corrections and confirms processing. One accepted file does not establish that prices or stock stay current. Consult the ingestion workflow.
The Delta Feeds API updates data for existing products. Use the identifiers required by its contract and inspect the response; a partial update should not be treated as creation of a new catalogue.
Agree frequency around how quickly your data changes. Daily promotions need a different control from stable prices. Keep representative before-and-after records to verify a correction alongside the processing log.
Resolve column, value and format failures using ingestion diagnostics. Check processed counts and issues, and distinguish imported products from those matching the campaign selection.
OpenAI’s feed troubleshooting helps locate failures. Also review the customer experience: an accessible page, correct variant, useful image, current price and coherent availability. Technical validation does not replace that commercial review.
Ad groups can restrict feed products using filters. Verify that a selection returns the intended items before activation. ads_metadata must use keys configured for the integration; do not invent filters the account cannot recognise.
Choose groups the team can assess by range, proposition, availability and margin. Avoid copying hundreds of categories without a budget decision. References: product selection and advertising metadata.
A template uses selected product data. Review representative cases before launch: a long title, a variant with a different image, a promotion and an unavailable product. The commercial owner should understand the proposed message and destination.
Inspect campaign, ad group and ad before activation. Catalogue availability, review and budget matter to delivery. The feed campaign workflow explains that hierarchy.
Define what counts as a purchase and which source confirms it. A campaign optimising for conversions needs the appropriate conversion configuration. Conversion optimisation does not mean payment only for purchases: review the conversion and billing requirements.
Product reports help review delivery and clicks; conversions and value require their attribution reading. Reconcile that reading with actual orders. For implementation planning, use the OpenAI Pixel and Conversions API guide and official reporting documentation.
Prepare a catalogue sample, platform, markets, priority ranges, update frequency and order-confirmation source. Include available Ads Manager access and data ownership. This lets us separate catalogue cleanup, integration, campaigns and measurement into a reviewable scope.
The ecommerce service covers commercial work. The tracking service covers purchase signals. Request a catalogue and measurement assessment before defining a launch.
Formats, expiry, filters, ads_metadata, reporting and ecommerce operations.
The schema separates Ads and search eligibility. Review their settings and objectives separately; advertising delivery does not establish organic visibility.
Account access and features, markets, file schema, data sources and update ownership. Confirm availability before setting a launch date.
The documentation covers ingestion and updates to existing products. Choose the account-compatible process, then assign ownership, frequency and checks after changes.
A compatible export from WooCommerce or another platform can be assessed. Data, variants, format, access and maintenance need checking; an export plugin alone is insufficient.
Find the price source, correct the product using the supported mechanism and check processing and the product page. Decide which selections can continue advertising while the issue is resolved.
The intended products should match, using supported fields and configured keys. The team needs a commercial selection it can explain and maintain.
No. It is an optimisation configuration. Access, data, selection, creative, purchase experience and measurement require verification, with outcomes assessed against business evidence.
It supports 2027 planning using documentation reviewed on 14 October 2026. Implementation requires checking the account’s current access and requirements again.
This guide covers feed mechanics. Our ecommerce service handles which products to activate, how to group them, what product experience they need and which orders or revenue justify scale.
What you sell, which markets you work in and what you want to learn from the first pilot. If the scope is not clear yet, we will define it with you.