ChatGPT Ads · Status at source date: Documentation update
ChatGPT Ads sets November target-bidding transition and January retirement
OpenAI documents Target CPA and Target CPC options from 9 November in Ads Manager, with existing Max Bid and Max CPC controls retiring on 1 January 2027. API integrations follow a separate 18 November transition. Targets are average-cost goals, not caps or guaranteed prices. Bidding objective and billing event remain separate.

What changed
OpenAI's help page sets two transition stages. From 9 November 2026, Ads Manager offers Target CPA for new conversion campaigns and Target CPC for new click campaigns. Existing Max Bid and Max CPC controls retire on 1 January 2027. The page calls the automated alternative Intelligent bidding, formerly Maximize Results (Autobid).
The API timetable differs. From 18 November, integrations are advised to use dedicated target fields. Legacy fields remain supported through December, but creating a campaign or changing an ad group's bid type with them selects target bidding and interprets the value as an average-cost goal. Those fields are deprecated from 1 January.
This changes the meaning of a number in a campaign configuration. A target describes an average outcome the system aims for; it does not cap each result or guarantee the achieved average. Choosing a conversion target also does not, by itself, change the billing event to conversions.
For an agency integration, the practical risk is leaving a control labelled as a maximum after its underlying field has acquired target semantics. A client could reasonably interpret that label as a limit. Review the API mapping, interface label and explanation together, then test the supported transition in the intended campaign type. Keep a record of the previous strategy so a performance change can be investigated against the configuration change.
A useful internal handover would identify the campaign owner, the integration owner and the date each route changes. It should also state whether reporting is comparing like-for-like conversion events. These are implementation checks, not a forecast of better performance or a recommendation to raise a particular advertiser's target.
Barry Schwartz reported the change on 5 November. OpenAI's current documentation supports the timetable, but its exact revision date is unverified. The report date should not be mistaken for the date on which the help page first changed. Check the controls available in the account before scheduling a migration.
Sources & contributor credit
- Official sourceOpenAI
Official current guidance reviewed 6 November. Original revision date unknown; Ads Manager and API transitions distinguished.
- Reported by · Barry Schwartz
Original creator unverified
Credits reflect the editor's latest changes. Original authorship has not been independently verified for this version.
Attribution evidence and limitations
Full attribution review pending.
A source link alone does not establish original authorship.
Original image and video creators have not yet been verified.
- Published on this site
- Article updated
This update reflects the dated source reporting. Availability may have changed. Further coverage of this same development will be added to this page.




