ChatGPT Ads Splits Your Brand Name From Your Legal Name, and Opens Up Non-Goal Conversions

An Ads Manager account now keeps three separate names, and changing the public one pauses your ads until it passes review. The conversions API will return attributed events your campaign is not bidding on, which on our own account turned a reported zero into 63. No new countries opened this week, whatever the email's last bullet suggests.

OpenAI sent advertisers a product update on 30 September 2026 with five bullets. One of them is a repeat, three of them are conveniences, and one quietly fixes a real hole in what this channel could measure. Worth separating them, because the email does not.

Three names where there was one

Until 25 September 2026 an Ads Manager account had a single name doing three jobs: labelling the account, appearing next to your ads, and matching your business registration for billing and verification. Those were always three different requirements, and companies whose trading name is not their registered name had to pick which one to break.

They are now separate fields under Settings, then General:

At signup the single advertiser name you type still fills all three, so an account nobody has edited has them identical and nothing has changed for it.

The part to know before you touch it is what each change costs. They are not equivalent:

• Account Name: nothing. It is internal, and OpenAI states plainly that changes do not trigger review.

• Brand Name: brand review, and ad serving pauses until the new name is approved.

• Legal Name: business review restarts, and serving may pause.

So a tidy-up on a live account is a delivery decision. Renaming a brand mid-flight on a campaign that is spending buys you an unknown number of dark hours; doing it in the same pass as verification, before launch, costs nothing. All three are also writable through the Advertiser API on the account brand endpoint, as account_name, brand_name and legal_name, with omitted names left alone. The older single name field still works and sets all three at once, which is now rarely what anyone wants.

Conversions you are not bidding on

This is the change that matters, and the email gives it one line.

A campaign optimises for one event. Everything else a visitor did was, in OpenAI's own reporting, invisible. That is a genuine problem whenever the event you are able to bid on is not the event that pays you, which on this channel is common: custom events can be measured and attached to a campaign but never chosen as its optimisation goal, so sending one bought you a row in the events feed and nothing in attributed reporting.

The conversions reporting endpoint will now return attributed events that are not the campaign's goal. OpenAI's example is reporting attributed purchases while optimising for a different event, without changing the campaign's conversion goal or its optimisation settings.

The size of the gap is easy to underestimate. We ran this against one of our own paused campaigns over a four-week window. Goal-only reporting returned zero conversions. The same request, with the event expansion added and nothing else changed, returned 63 attributed events on the same campaign. Both numbers are correct, they answer different questions, and until this week only the first one existed.

Three qualifiers travel with it, and they are the kind a summary drops:

• Read these reports on ad-event time. Reporting by conversion date has limited coverage of non-goal events, which OpenAI says explicitly.

• An empty result is not proof of nothing. It can also mean the account's event history has not finished publishing.

• A row can show real event activity and zero goal conversions at once. That combination is the feature working as designed.

The same endpoint takes attribution windows: 7, 14 or 30 days on the click side, defaulting to 30, and 0 or 1 day on the view side, defaulting to 1. As in Ads Manager, changing the window changes the report and never the bidding or the billing.

What this changes in practice is which events are worth instrumenting at all. An event the auction will never learn from is now still worth sending, because it can be read back against the campaigns that produced it.

Two conveniences for product feeds

Feed campaigns got the two things people running large catalogues kept asking for. Bulk creation now covers them: multiple product feed campaigns and ad groups can be created from a spreadsheet under Campaigns, then Bulk uploads, then Bulk sheet, with a Product feed template separate from the ordinary campaign schema, and ad templates generated automatically. And the Products tab now carries a review status, so a rejected product finally states its reason where before it simply failed to serve in silence.

Both are Ads Manager features only. The Advertiser API has no bulk creation endpoint and no product review field, and as of this writing OpenAI's own bulk upload checklist and product feed articles describe neither, so the advertiser email is the only account of how they behave. Worth knowing before anyone plans an integration around them.

The structural trade-off that decides whether a feed campaign suits you has not moved: feed campaigns still target at country level, where an ordinary campaign can target regions, cities and postal codes where OpenAI has them.

No new countries this week

The email's last bullet says ChatGPT Ads are live in Indonesia, Malaysia, the Philippines, Singapore, Thailand, Vietnam and Taiwan. That is true, and it has been true since 23 September, when OpenAI announced it and the self-service table went from 56 countries to 63.

We re-read OpenAI's availability page on 30 September and it returns the same 63 countries in the same order. Nothing opened this week. An email restating an announcement reads like news to anyone who missed the original, so the next one is worth checking against the table itself.

The country-by-country reference, with a dated log of every change since August, is on our ChatGPT Ads availability page. The three names and what each change triggers are covered in the business verification guide, the reporting change in the measurement guide, and the feed sheet in the bulk upload guide. The 30-second eligibility checker tells you where your own entity stands.