Managing the ad account: a kill switch for all campaigns, additional API keys and the three account names

Most settings in ChatGPT Ads belong to campaigns, ad groups and ads. Three belong to the ad account itself, and those are exactly what the Advertiser API opened in October: a kill switch for the delivery of the whole account, creating additional API keys and maintaining legal name, account name and brand name separately. Chatvertise shows all three on the “Ad account” page. This article explains when you need them and what to watch out for.

The kill switch: one switch above all campaigns

Until now “stop everything” meant pausing every campaign individually or via bulk action. Both change the status of the campaigns, and when restarting you need to know which ones were active before. Pausing the ad account works differently: it stops delivery at account level, the campaigns keep their status. Activating releases them again, and everything continues as before.

• When: a tracking outage, a bug in the shop, a crisis during which no ads should run, or a client who pauses the collaboration.
• Who: in Chatvertise only owners of the organisation, with a two-step confirmation. An accidental click doesn't stop the account.
• What it isn't: the kill switch doesn't replace an account daily limit. The limit caps spend, the kill switch stops it entirely.

For automation: automation rules work at campaign level and are unaffected by the account status. A rule that activates a campaign changes its status, but a paused account still doesn't serve.

Additional API keys

Every Ads API key belongs to exactly one ad account. Until now a new key came only from the OpenAI Ads Manager; now it can also be created via the API and therefore in Chatvertise. The key is shown once and stored nowhere. Revoking still happens in Ads Manager.

• One key per tool: reporting tool, Chatvertise, your own scripts, each gets its own. If one goes away, the others remain.
• Agencies: the client creates the key for the agency and revokes it when the collaboration ends, without losing their own access. The flow fits into onboarding in 30 minutes.
• Rotation: if someone who knew the key leaves the team, you create a new one and revoke the old one.

Not every key may create further keys. If OpenAI answers “not allowed”, the connected key was created without that right; then Ads Manager is the way. Which accounts a key can see at all is shown by the new list “Accounts of this API key”: usually it's exactly one.

Three names instead of one

Since October an ad account has three names: the advertiser's legal name, the account name and the brand name that appears in ads. The old name field set all three at once; now they can be maintained individually, but not combined with the old field. Each name has 2 to 1000 characters without angle brackets.

The important catch: if you change the legal or the brand name, OpenAI pauses the account's delivery until the new name has been reviewed. The account name, on the other hand, is free. Chatvertise sends only the fields you actually changed and warns about the review pause before you save. For agencies with many accounts this is the clean separation of legal entity and brand that was missing before.

What else is on the ad-account page

• Approvals: account review, domain, favicon and payment method, the prerequisites of any delivery.
• Account daily limit and time windows, if the key has admin rights.
• Attribution as an account setting, explained in Setting attribution.

All of the month's changes are in the late-October update.