OpenAI Ads update, early October: crawler evidence, geo signal, separate account names and attribution everywhere

OpenAI updated the Ads API specification again in early October. Nothing was removed, there are no breaking changes — but five additions, all pointing toward “more transparency”. We've compared the changes against our integration; here's the overview and our plan.

Crawler evidence per ad

The biggest addition: for every ad you can retrieve what the review crawler saw for the submitted version — fetch status, final URL after redirects, whether robots.txt allowed access (with reason), the user agent used and a screenshot that stays valid for 24 hours. For a landing-page rejection, that's the difference between guessing and knowing. Our plan: as soon as the endpoint answers reliably, the evidence appears right below the rejection reason on the ad detail page.

Signal for blocked geo targeting

Campaigns, ad groups and ads carry a new flag indicating whether serving is blocked because of geographic targeting. Until now that was only recognizable indirectly via the country list. We'll add the signal to the serving chips next to the existing serving notes.

Separate account names

An ad account now has three names instead of one: legal name, account name and brand name. The old name field still sets all three at once; the new fields can be maintained individually but not combined with the old one. For agencies with many accounts, that's a welcome separation of legal entity and brand. The Ad account page in Chatvertise gets the three fields.

Variants and availability in the product feed

A feed's product query now returns variant and availability per product. That makes it visible at a glance in the product list which items are sold out — and lets you restrict a product set to items in stock.

Attribution windows on all insights

Until now, click window, view-through window and time basis could only be set in conversion reporting. Now all four insights endpoints — account, campaign, ad group, ad — accept the same parameters. That's the foundation for a consistent attribution choice across the whole dashboard instead of only on the Conversions page.

And the hotel insights?

The hotel reporting endpoints that appeared in September are unchanged in the specification but remain reserved for accounts enrolled in hotel advertising. For everyone else the API still answers “not found” — nothing has changed there.

As with every update, our rule applies: we only build what we've verified against the real account. The five items are now on the list in this order.