Field noteNov 8, 20266 min read1 source

OpenAI switches ChatGPT Ads to Target CPA and Target CPC from November 9

In one minute

OpenAI is replacing maximum-bid controls with average-cost targets for new ChatGPT Ads campaigns beginning November 9, 2026. The distinction matters to advertisers: a target CPA or CPC guides auction decisions but does not cap what an individual conversion or click costs, so campaign migration requires measurement and budget checks.

What happened

OpenAI’s Help Center article, “Bidding strategies and how pricing works in ChatGPT Ads,” says the system is evolving to manage more campaign bidding and delivery automatically. Advertisers specify the business outcome they want and either a budget or target cost; the system adjusts bids and delivery toward those goals. The article describes Intelligent bidding, formerly called Maximize Results (Autobid), as the option for pursuing an outcome within a budget without setting a target average CPA or CPC.

For conversion campaigns, Target CPA replaces Max Bid as the option for advertisers creating new campaigns who want to work toward a specified cost per conversion. OpenAI says this starts Monday, November 9, 2026. A Target CPA is an average-cost goal: the system uses the target and available conversion signals to adjust bids and delivery, seeking conversions from the budget while working toward the desired average. OpenAI’s example is a $50 target. Some conversions may cost more and others less, and the actual average may be above or below $50.

For new click campaigns, Target CPC becomes available starting November 9. It similarly guides an average rather than setting a hard ceiling: individual auction bids can be above or below the target, with the system aiming to deliver clicks from the budget while working toward the average. Max CPC, by contrast, caps individual click bids. OpenAI says existing Max Bid and Max CPC campaigns are legacy controls and will retire on January 1, 2027. Advertisers can begin moving campaigns to the new options in Ads Manager from November 9, 2026.

The change also affects API integrations, but on a staged timetable. OpenAI says it is adding dedicated Target CPA and Target CPC fields. Before November 18, legacy fields retain their existing behavior, and partners can adopt the new fields when available. From November 18, OpenAI recommends the new fields; legacy fields remain supported through December 31, but using them to create a campaign or change an ad group’s bid type selects target bidding, with submitted values interpreted as average-cost targets. The legacy fields are deprecated starting January 1, 2027.

OpenAI says the winning auction bid sets the price paid across bidding strategies. A target is therefore not a guaranteed maximum or a fixed price per click or conversion. The article advises advertisers to review recent actual costs for the same conversion event or click campaign, use a consistent reporting period, account for conversion-reporting delays, and consider whether the outcome is worth its cost. It warns that targets below recent performance may restrict delivery. For conversion campaigns, it recommends verifying that real events arrive through the OpenAI Pixel, Conversions API, or both; weak or missing signals can reduce delivery and leave budget unspent.

What the archive adds

New Runtime’s earlier coverage described OpenAI Ads API documentation, including partner setup and campaign creation, as the advertising system entered a developer and account interface. This is a new operational fact on that developing story: OpenAI now documents target-based bidding, campaign transition dates and API field behavior. The earlier coverage does not establish how advertisers will perform under the new targets.

Trend signal

This does not yet fit a pattern New Runtime tracks. The change is a specific advertising-platform control and migration schedule; it does not by itself establish a broader shift in agent economics, runtime architecture or agent interoperability.

Why now

OpenAI’s documentation sets November 9, 2026 as the start date for Target CPA on new conversion campaigns and Target CPC on new click campaigns. It also gives advertisers and API partners a transition window before legacy bid controls retire on January 1, 2027. The article frames the move as a way for the system to manage more campaign work automatically, but does not explain why these dates were chosen.

Why it matters

For advertisers, the practical change is from controlling an auction ceiling to expressing an average outcome cost. That can give the platform room to bid more aggressively in one auction and less in another, but it also means the entered target cannot be treated as a per-click or per-conversion cap. Teams should avoid comparing a target value directly with a guaranteed billable maximum.

The migration has a measurement dependency. A conversion campaign can only be steered usefully if the selected event is actually arriving and its quality is adequate; a tracking setup that exists on paper is not enough. OpenAI explicitly warns that weak or missing conversion signals can reduce delivery and leave budget unspent. Advertisers should review recent actual CPA or CPC, event quality, spend and results together as the campaign learns, rather than lowering targets on the assumption that the target forces lower costs.

For teams using the API, the field transition is also an integration concern. After November 18, legacy fields used for certain campaign creation or bid-type changes select target bidding, and their values mean average-cost goals rather than maximum bids. Code or operational procedures that assume the old semantics could therefore produce a different campaign configuration. The January 1, 2027 deprecation date gives API partners a clear deadline to update integrations.

What happens next

  • Advertisers and API partners will need to transition campaigns and integrations away from Max Bid and Max CPC before retirement. (3 months, 90%). Watch for: Ads Manager migration guidance and use of the dedicated target fields.

Limits and uncertainty

OpenAI does not provide performance results showing whether Target CPA or Target CPC improves outcomes, reduces costs or changes campaign delivery compared with the legacy controls. The article gives illustrative examples, not a measured comparison or a guarantee that a target can be achieved. It also does not quantify how much event volume or what Event Quality Score is sufficient for reliable optimization. Actual costs, spend and delivery will depend on campaign conditions and signal quality. The stated dates and behaviors are OpenAI’s own documentation; they have not been independently tested here.

Skill to build now

Before migrating a conversion campaign, calculate recent actual CPA for the same conversion event over a consistent reporting period and account for reporting delay. Verify that the Pixel or Conversions API is receiving real events, then review event-quality warnings and delivery diagnostics. Set a target in relation to that observed baseline and the value of the outcome; do not use a lower target as a promise of lower bills.

Reader takeaway

Target CPA and Target CPC are steering goals, not hard price caps. Advertisers should prepare for the documented migration dates, validate conversion signals and evaluate actual average costs and delivery together rather than assuming the number entered is the amount each result will cost.

Evidence / sources

  1. 1help.openai.com/en/articles/20001634-bidding-strategies-and-how-pricing-works-in-chatgpt-ads
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicAi Business ModelsExplore the ai-business-models topic hub.
  2. 02topicPricingExplore the pricing topic hub.
  3. 03archiveField NotesOpen the latest editorial analysis.
  4. 04sourcesSourcesSee the original sources this archive cites.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract