ChatGPT Ads oCPC: How Server-Side Events Feed Conversion Bidding
What oCPC Optimizes - and What It Bills
Conversion-optimized cost-per-click - oCPC - is OpenAI's middle ground between buying traffic and buying outcomes, documented in the Ads developers' guides as bidding_type: "conversions". The goal table makes the ladder explicit: impressions campaigns buy reach per 1,000 impressions, clicks campaigns buy engagement per valid click, and conversions campaigns keep paying per valid click while delivery favors clicks more likely to lead to your selected conversion event. OpenAI notes oCPC is in open beta for both standard and product-feed campaigns, so the surface is live but still moving.
Billing is where expectations get calibrated: an oCPC campaign never charges per conversion. An auction determines the actual CPC, OpenAI charges only when a valid click occurs, and the CPA bid functions as an optimization input - how aggressively the campaign competes for clicks likely to convert - rather than a price tag on outcomes. Setup of tracking, if you have not built it yet, is covered in the ChatGPT Ads conversion tracking guide.
The Prerequisites: One Standard Event, Reliable Tracking
Campaign creation has two gates. First, enablement: the ad account must support conversion bidding, and a 403 with Conversion bidding is not enabled means contacting your OpenAI partner representative rather than retrying. Second, the optimization target: exactly one active standard conversion event, owned by the current ad account and connected to one active conversion source. Custom events cannot serve as oCPC goals, and the goal cannot be changed after campaign creation - picking the event is a one-way door, which makes the choice worth a moment.
The tracking layer matters as much as the event choice. OpenAI's prerequisite list accepts the JavaScript pixel, the Conversions API, or both - and states plainly that the Conversions API is the more reliable tracking source than the pixel alone. For an affiliate funnel where the conversion fires on a page you do not control, server-side delivery is not an enhancement but the only complete path; the conversions API pattern is the same one used across networks. Running pixel and API together calls for the usual event_id deduplication so optimization reads one conversion, not two.
Create the Campaign and Set the CPA Bid
OpenAI's documented sequence starts with a paused creation: build the campaign with bidding_type: "conversions" and the conversion_event_setting_ids array holding your chosen event setting - the identifiers look like order_created, lead_created, or registration_completed - and a budget block. Ad groups then carry the bidding configuration: billing_event_type set to click, and max_bid_micros holding the CPA bid even though billing stays click-based - the docs' example sets 100000000, a $100.00 CPA bid on a USD account.
That inversion - a CPA number on a click-billed line item - is the mental model of the whole feature. The bid expresses what a conversion is worth to you; the billing expresses what you actually pay for. Ads are added as usual, and the campaign activates only after all child resources are ready. Product-feed campaigns follow the same shape with mode: "product_feed" and a linked feed, with product sets for filtering.
Feed It Server-Side Events
The Measurement Pixel fires browser events via oaiq("measure", ...) after initialization - fine for pages you control - and OpenAI pairs it with the Conversions API for server-side delivery. Delivery quality consumes the combined signal: oCPC uses the selected conversion event together with ad quality, relevance, click likelihood, and conversion likelihood to favor clicks that convert. Gaps in the signal become gaps in the optimization - a conversion the pixel never saw and the API never received simply never happened as far as bidding is concerned, which is why deduplication discipline matters before scaling spend.
Attribution has one trap worth knowing. View-through conversions, when available for the account, use a fixed one-day window after an eligible impression, are reported as a separate campaign-level metric, and are explicitly excluded from the Conversions total - CPA, post-click CVR, bidding, billing, and conversion optimization all remain click-through-based, and the click takes precedence when a conversion qualifies for both. Reading view-through numbers as if they fed bidding will overstate what the optimizer sees.
MOST delivers tracker postbacks to OpenAI's Conversions API alongside Meta, TikTok, Reddit, Pinterest, and Snapchat, and the free Pixel Activator covers OpenAI delivery for a single landing - either keeps the oCPC signal complete without a custom pipeline.
Read the Reports Right
OpenAI's reporting guidance for oCPC names the hierarchy: because delivery optimizes toward the selected event, conversions are the primary outcome to review, with impressions, clicks, spend, CTR, and average CPC read alongside. Cost per conversion is not a billing line - you calculate it by dividing spend by conversions, and the Insights endpoints return the delivery metrics programmatically.
Two early-tuning habits follow. When conversions stall while clicks flow, the first suspects are signal-side: the single allowed standard event misconfigured, or a tracking source that misses most conversions. And when conversions flow but the cost per conversion drifts above your CPA bid, remember the bid is a competitiveness input - the auction sets actual CPCs - and adjust it like a dial, not a contract.