Skip to main content
This page compares the OpenAI Ads capabilities represented in the Apostra adapter with what Apostra currently makes available to buyers. It answers a practical question: what can I do through Apostra today, and what would still require another path?
Last reviewed 2026-08-21. This is Apostra’s description of its own adapter, based on the implementation and the linked provider documentation. OpenAI Ads has not reviewed or endorsed this page. Availability can still vary by account permissions, market, and provider access.

​
At a glance

​
How to read availability

  • 🟢 Available — Offered through Apostra now, subject to your ad account’s permissions and eligibility with the provider.
  • 🟡 Partial — Some of the workflow is available; the Comments column explains the boundary.
  • 🔵 Testing — Apostra is validating the workflow before offering it broadly.
  • ⚪ Planned — Not offered through Apostra yet. The provider may still support it directly; Comments explains why and links a roadmap reference.

​
Roadmap

The adapter roadmap is tracked in AI-6371 (a plain-text reference — Apostra’s internal issue tracker is not public). This roadmap tracks OpenAI Ads product completeness, partner feedback, and live readiness. Every row that is not currently available shows that reference or a more specific one in its References column, so customers and partners can quote a stable identifier when asking about a capability.

​
Connection, accounts, and identity

OpenAI Ads connects to Apostra through OAuth or an account-scoped API key. Connecting authorizes Apostra to reach your Advertiser account (each OAuth grant or API key is scoped to one advertiser), which you then map to your advertisers. The mapped account decides which OpenAI Ads tenant a buy runs on: a media buy for an unmapped advertiser fails closed with account_mapping_required rather than silently using another account. Connection, account-discovery, and revocation behavior is the same across ad platforms — see Platform accounts and advertiser mapping for the full model and the OpenAI Ads section of the connecting guide for OpenAI Ads-specific permissions.

​
Campaign products

​
Creative formats

These rows describe Apostra availability, not a claim that the ad platform itself prohibits an unavailable format.

​
What the adapter can do

​
Placement choices

Apostra does not expose a separate OpenAI Ads placement selector.

​
Targeting

​
Reporting

Apostra reports OpenAI Ads delivery day by day (there is no hourly delivery breakdown), aggregated nightly from adapter-reported delivery, in the advertiser’s home currency using the booked or historical exchange rate — any cross-currency rollup is always labeled an estimate and is never used for billing. See Reporting overview for the full model. Apostra does not currently publish an attribution-finality window for OpenAI Ads; the table below lists every metric the adapter surfaces today.

​
Webhooks and async lifecycle

OpenAI Ads does not push status, delivery, or reporting events into Apostra — every campaign product declares supports_webhooks: false.
  • Status. Apostra does not currently poll OpenAI Ads in the background for creative or media-buy status changes; status reflects what the adapter returned on your last call.
  • Delivery. Apostra fetches delivery numbers (spend, impressions, clicks) live from OpenAI Ads on demand, only when you call get_media_buy_delivery directly. The /reporting/metrics endpoints never call the adapter either way — they read from a separately-populated store (see Reporting below), so a reporting request does not itself refresh provider delivery.
This is separate from Apostra’s own buyer webhook subscriptions — an unrelated account-level event feed (currently discovery.revision only), documented in Buyer webhooks.

​
Market and account availability

Apostra does not promise that every feature is enabled for every account or market. The current planning list includes AU, BR, CA, JP, KR, MX, NZ, GB, US; your selected account still determines final availability.

​
Important limitations

  • the ad platform’s API. Initial product-feed connection and full uploads must be completed in OpenAI Ads Manager or by SFTP; the API does not perform that setup.
  • the ad platform’s API. OpenAI Ads does not expose a placement selector, so Apostra does not offer one.
  • the ad platform’s API or your account’s eligibility. Market and geography availability is determined by the selected OpenAI Ads account at request time.
  • both Apostra’s implementation and the ad platform’s API or account eligibility. OpenAI’s Ads reference names an expiring ad-preview operation, but its published OpenAPI schema does not define the operation or response, and Apostra has no verified public HTTPS preview URL to return. The account preview URL is only a favicon preview, and Apostra does not substitute it or an approximate render.
  • Apostra implementation/testing. Apostra has not yet completed end-to-end account validation for these workflows.

​
Technical mapping

Engineering-level detail — raw provider objectives, billing enums, optimization codes, and object-field mappings. Not required reading to understand what Apostra can do with OpenAI Ads; see the tables above for that.

​
Provider documentation