Blog · Protocol

ChatGPT Ads API partners that still send Max Bid after November 18 are posting average targets, not auction ceilings.

November 6, 2026 · RTBlint

On November 5, 2026, Search Engine Land published the advertiser email OpenAI sent about ChatGPT Ads bidding changes that take effect Monday, November 9, 2026. New conversion campaigns will default to Target CPA instead of Max Bid. New click campaigns will offer Target CPC instead of Max CPC. Max Bid and Max CPC retire for existing campaigns on January 1, 2027. The same week, OpenAI's Help Center documents a separate API calendar: dedicated Target CPA and Target CPC fields for partners, with legacy Max Bid and Max CPC fields retaining old behavior only until November 18, 2026, after which create and update calls that still use the legacy names submit average-cost targets, not maximum bids.

Ceiling bids and average targets are different contracts

Max Bid, in the language OpenAI used before this rollout, set an auction-bid ceiling for conversion campaigns. Max CPC capped individual click bids. Target CPA and Target CPC are outcome averages the system may exceed or undershoot in any single auction while working toward the goal across spend. OpenAI states explicitly that while Max CPC caps individual bids, Target CPC lets the system bid above or below the target in individual auctions to maximize clicks from budget. That is not a cosmetic rename. It changes what a number in a campaign object means when finance asks whether delivery stayed inside a hard limit.

Trade coverage on November 5 quotes OpenAI telling advertisers to review recent actual CPA or CPC when picking targets, and to confirm Pixel or Conversions API events reach the data source linked to conversion campaigns before migrating. Those recommendations sit on the measurement side. The buy-side integration side is the API field map: partners who automate campaign creation must know whether their JSON still sends max_bid semantics from 2025 or Target CPA semantics from November 18 onward. RTBlint is independent and not affiliated with OpenAI or IAB.

ChatGPT Ads inventory also reaches buyers through partner DSP paths described in earlier industry coverage (Amazon DSP, Equativ, and direct Ads Manager). Whether the bid clears inside a DSP UI or through a partner API, the auction OpenAI documents remains a relevance-weighted second-price design at the ad-group level. Mis-labeled bid controls do not change auction math. They change whether the automation that created the campaign understood the risk envelope.

What the Help Center calendar actually says

OpenAI's bidding strategies article, saved November 5, 2026, lists three API phases. Before November 18, 2026, Max Bid and Max CPC fields keep existing behavior; partners may adopt new Target CPA and Target CPC fields when available. From November 18, OpenAI recommends the new target 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 CPA or Target CPC respectively, and submitted values represent average-cost targets rather than maximum bids. Starting January 1, 2027, Max Bid and Max CPC fields deprecate entirely.

November 9 is the Ads Manager-facing date for new campaign defaults. November 18 is the API-facing date when legacy field names stop meaning ceilings on write paths. Teams that only watch the UI email can miss the earlier API cutoff if their trafficking stack creates ChatGPT lines programmatically. The failure mode is not an OpenRTB parse error. Nothing in imp.video or device breaks. The failure mode is a campaign object whose bid type the platform interprets as Target CPA while the partner dashboard still labels the column Max Bid.

Search Engine Land's November 5 piece also notes OpenAI rebranding maximize-results autobid as intelligent bidding. Autobid strategies that ignore explicit CPA targets remain a third branch. Integrations must distinguish three states: manual target fields, legacy ceiling fields during the overlap window, and legacy fields after November 18 that silently map to targets. A regression test that only checks HTTP 200 on campaign create is insufficient.

Why this belongs in the bidstream conversation

OpenRTB bid requests are not how ChatGPT Ads campaigns are expressed. The programmatic parallel is still supply-path and buy-side automation: who constructs the order object, which field names cross the wire, and whether downstream reporting matches the semantics upstream sent. When Google's remedies order forces AdX and DFP inventory through Prebid-shaped paths, the industry argument was wire consequence despite a different surface API. ChatGPT's API remap is smaller in antitrust scale but identical in integration shape: a calendar flip that redefines payload meaning without changing the consumer-facing product name.

DSP engineers often mirror UI enums into partner APIs. If the UI column reads Max Bid through December 31 while the API already treats the same key as Target CPA on create, two teams can truthfully disagree about whether a $40 value was a cap or a goal. Delivery teams see underspend when targets are too tight. Finance sees overshoot when individual auctions clear above what planners thought was impossible. Neither symptom looks like a malformed bid request. Both look like algorithmic black boxes until someone diffs the campaign JSON against the Help Center phase table.

Conversion-optimized ChatGPT lines depend on signals OpenAI describes in the same November materials: Pixel plus Conversions API, Event Quality Score warnings, and click-through Conversions as the optimization column. A partner that migrates bidding fields but not measurement fields can double-fail: wrong bid semantics and weak conversion feeds that OpenAI warns can leave budget unspent under restrictive targets. Pixellint's post on shop revenue per visit versus platform Conversions is the measurement half of that same week's headlines. This post stays on the campaign API half.

Illustrative partner payload (not OpenRTB)

The block below is illustrative JSON shaped like partner campaign APIs, not an OpenRTB 2.x bid request. It shows the ambiguity integrators must eliminate before November 18.

// Partner create call on 2026-11-20 (after API remap)
{
  "campaign_id": "cmp_8841",
  "ad_group": {
    "bid_strategy": "max_bid",          // legacy field name still accepted
    "max_bid_usd": 42.00,               // platform reads as Target CPA average
    "optimization_event": "order_created"
  }
}

// Same advertiser intent if engineer still thinks in ceilings:
{
  "ad_group": {
    "bid_strategy": "target_cpa",
    "target_cpa_usd": 42.00             // explicit average-cost contract
  }
}

After November 18, the first object's numeric field is an average-cost target whether or not the partner UI calls it Max Bid. Auctions may still pay second price among eligible ads. Individual clearing prices can exceed 42 if the system pursues volume toward the average. Planners who treated 42 as a hard per-auction cap will read delivery logs as runaway bidding when the platform behaves as documented.

OpenAI also documents Target CPC for click campaigns with the same above-or-below per-auction behavior. Click campaigns that route through partner DSPs inherit the same field migration. None of this appears in bidfloor or deal objects on CTV exchanges. It still belongs in the same Monday standup as bidstream quality when your org buys ChatGPT through an API-enabled seat.

Checklist for partner and DSP integrations

Read the Help Center phase table alongside Search Engine Land's November 5 summary of the advertiser email. Treat November 9 and November 18 as different deadlines for UI versus API writes.

Inventory every automation path that creates or updates ChatGPT ad groups (direct API, DSP intermediary, internal trafficking tools).
Log raw request and response bodies for campaign create after November 18 on staging seats; confirm which field names the platform echoes back in the ad group object.
Map legacy Max Bid and Max CPC to Target CPA and Target CPC in your schema before January 1, 2027 deprecation, not on the deprecation morning.
Pair bid migration with conversion signal checks OpenAI lists for Target CPA (Pixel, Conversions API, Event Quality Score), cross-reading shop analytics versus platform Conversions.
Document for finance that Target fields are averages, not ceilings, before QBR slides compare ChatGPT CPC to search campaigns still managed under hard Max CPC elsewhere.

RTBlint validates OpenRTB bid requests and related supply-path JSON. It does not lint ChatGPT campaign APIs. When your org mixes CTV OpenRTB debugging with ChatGPT partner seats, keep the failure modes separate: malformed pod fields drop CTV bids before pricing; mis-migrated bid fields change ChatGPT delivery without touching imp at all.