Key Takeaway
The OpenAI guidance cited on August 16, 2026 listed three import methods: manual CSV/TXT uploads, a stable hosted HTTPS feed URL and automated SFTP uploads. Manual uploads suit small catalogs and pilots; hosted URLs suit existing public exports; SFTP suits large, frequently updated catalogs and server-to-server delivery. All require ongoing refreshes: the guidance stated that items expire after two weeks. In the described beta, these feeds made products eligible for ads, not organic ChatGPT conversations. Paid eligibility is not organic shopping exposure or a GEO citation result.
Facts and background
The original August 16, 2026 article recorded a recent-update notice on OpenAI's Create Campaigns from Product Feeds help page. It listed manual CSV/TXT uploads, stable hosted HTTPS URLs and SFTP connections, and stated that items expire after two weeks. Hosted URLs or automated SFTP refreshes were recommended for ongoing campaigns.
Three Import Methods Serve Different Needs
| Import Method | Best suited to | Key validation checks | Main risks |
|---|---|---|---|
| Manual CSV/TXT | Small catalogs, sample validation and infrequent updates | Encoding, column names, required fields, upload history and rejected rows | Inventory and prices are easily out of date owing to manual processes |
| Hosted HTTPS URL | Brands with a stable product export URL seeking less manual work | Public HTTP 200 response, TLS, stable URL, no login, scheduled updates and no WAF challenge | Ads Manager reads old snapshots when source file updates fail or access is limited |
| SFTP | Large catalogs, frequent changes and server-to-server delivery | Account privileges, key rotation, fixed filename, full snapshot, transfer and processing log | Credentials, file partitioning, overwrite policies and job failures add operational complexity |
These are transport options for getting product data into Ads Manager, not substitutes for field governance. The developer documentation cited in August described a Google-compatible base product format and required the canonical ads-eligibility field is_ads_eligible to be set to true. The legacy alias is_eligible_ads was also accepted, but new feeds should use the canonical field; is_ads_enabled was not recognized by Ads feed ingestion.
Keep Paid and Organic Shopping Feeds Separate
The cited help page stated that products uploaded through Ads Manager were eligible for ads during the beta, not organic ChatGPT conversations. Organic shopping data, public product pages, Product Schema and organic feeds support discovery and factual consistency; Ads feeds support paid product selection, targeting and reporting. Both can share a PIM or product SSOT, but eligibility, refresh jobs, review status, budgets and performance metrics must be managed separately.
Ads Manager and Public API Capabilities Differ
The August 16, 2026 source article described manual, hosted-URL and SFTP imports in Ads Manager, while reporting that the public Advertiser API did not create feed connections, list connected feeds or upload catalogs. It described SFTP setup in Ads Manager and Delta Feeds API updates to existing variants' availability or titles. This is a historical account, not current API guidance: the linked developer documentation now includes feed-creation and SFTP-configuration APIs. Recheck account access and documentation before implementation.
Do not assume that every Ads Manager action is available through an API or retire an existing SFTP pipeline merely because a hosted-URL option appears. Check the actual account and current documentation, validate a sample feed, then choose the production transport.
Processing, Eligibility and Delivery Are Separate States
A successful upload only starts processing. Products need valid fields, sale availability, ad eligibility and successful processing and review. Their campaign, ad group and template must also be active and meet budget and other requirements before they can enter an auction. Even is_ads_eligible=true does not guarantee impressions.
The Products tab is a delivery-reporting view, not a complete upload inventory. The cited guidance said products appear after an active feed campaign generates reportable delivery data, potentially taking up to seven hours after delivery starts. Before launch, check filtered product counts during ad-group creation and processing results in Upload History. An empty Products tab alone does not establish feed failure.
Impact on enterprises
First, a feed is an ongoing data service, not a one-time upload. Assign owners, failure alerts and retry procedures for prices, stock, sale regions, destination URLs and eligibility. Two-week expiry does not mean prices or stock may remain stale for two weeks. Second, separate product identity from market-specific eligibility. The same SKU may have different currencies, stock, pages, shipping, promotions and policies by country. Keep stable product and variant keys while defining sale and ad eligibility per market. Third, growth and product-data teams need a shared fact source. Titles, descriptions, images, prices, sale prices, brands and URLs must agree across feeds, websites, checkout and ad templates. Feed optimization cannot justify claims the landing page cannot substantiate. Fourth, measure paid ads, organic shopping and GEO citations separately. Product impressions and clicks belong to Ads reporting; organic shopping presentation needs separate testing; page citations, brand mentions and OAI-SearchBot visits are not ad results. A shared PIM does not imply shared eligibility or ranking mechanisms.
Zhihe Growth's Assessment
Zhihe Growth's assessment is that easier imports reduce connection work, not data-governance requirements. Manual uploads support small pilots, hosted URLs suit stable exports, and SFTP with supported delta updates suits frequent operations. Easier transport can also spread stale prices, unavailable products, incorrect pages and eligibility errors faster. Use one product SSOT with three publishing paths: the website and Schema for public facts, organic feeds for shopping discovery, and Ads feeds for paid candidates and product reporting. Share SKU, variant, brand, price, availability, image and URL facts, while maintaining separate eligibility, refresh schedules, review evidence and metrics. The original August article reported narrower public API capabilities than the current linked documentation. Treat this as a dated implementation account. Record actual account capabilities, the documentation-check date and rollback procedures; do not promise automation that has not been validated in the account.
Recommended action
- Choose and document the transport: manual CSV/TXT for small samples, hosted HTTPS for stable public exports, or SFTP for large catalogs and frequent changes.
- Maintain a product-field SSOT for item ID, variant, title, description, brand, price, sale price, availability, image, destination URL, market and currency. Do not create conflicting facts for ads.
- Use the canonical is_ads_eligible field for ad eligibility. Remove the incorrect is_ads_enabled field; retain the legacy is_eligible_ads alias only where compatibility requires it, after checking the current specification.
- Validate a representative sample of about 100 products for required fields, variants, images, prices, stock, URLs, eligibility and error reporting before uploading the full catalog.
- For hosted URLs, check HTTPS, a stable address, HTTP 200, no login or CAPTCHA/WAF challenge, Content-Type, encoding, update timestamps and complete downloads.
- For SFTP, apply least privilege, key rotation, stable filenames and partitions, overwrite policies, processing logs and failure alerts. An ad-creative upload endpoint is not a product-catalog endpoint.
- Refresh product data as business facts change and before the cited two-week expiry limit. Set shorter freshness thresholds for prices, stock and promotions.
- Validate processing and eligible product counts through Upload History and ad-group creation. Use the Products tab for delivery reporting, not as the sole pre-launch check.
- Verify three outcomes separately: paid product impressions and clicks, organic ChatGPT shopping presentation, and page citations and brand mentions. Success in one does not establish success in the others.
- For each release, retain the feed version, field dictionary, source system, upload time, errors, product counts, campaign and ad-group settings, landing-page samples and reporting window for rollback and reconciliation.
Limitations
This article records the source's August 16, 2026 account of OpenAI guidance. Recent-update notices did not establish that every field first appeared in the preceding 72 hours. Eligibility, markets, import options, formats, APIs, ad formats, review and reporting can change; verify the actual account and current documentation. The source described three Ads Manager import methods and SFTP-focused developer guidance, with no public feed-creation API. The linked developer page now documents feed-creation and SFTP-configuration APIs. Do not treat the historical restriction as current, infer undocumented endpoints or assume equal access across accounts. Two-week expiry is an outer refresh limit, not an appropriate update interval for prices, stock or promotions. is_ads_eligible=true, successful processing or appearance in reporting guarantees neither approval, impressions, cost targets nor incremental sales. Ads feeds do not by themselves place products in organic ChatGPT conversations or establish website indexing, recommendations or citations. These are data-consistency and measurement recommendations, not media-buying, bidding, revenue or performance guarantees. Review advertising, privacy, consent, cross-border transfer, pricing and consumer-protection requirements before activating feeds, Pixel, Conversions API or customer-data transfers.