Aug 1, 2026 · 6 min read
Skip One Account, Keep the Channel
Two Pages on one channel used to mean two pieces, whether you wanted the second one or not. Every connected account now has its own Generate switch — and the count, the estimate, and the draft all follow it.

You connected two Facebook Pages for good reasons. One is the company Page, where the product announcements go. The other is the personal blog you still post to, the one with a different audience and a different voice. Both are legitimately yours, both belong in the app, and both are wired up and ready.
Then you write a campaign about a release, select Facebook, and the app writes for both of them.
So you pick your poison. Either you generate for both and quietly ignore the piece meant for the blog — having paid the tokens to write it, and having read past it every time you scan the campaign afterwards — or you leave Facebook out of the campaign entirely and come back later to do that one Page by hand, which is precisely the errand you bought a campaign tool to stop running. Neither option is wrong. Both are annoying, and both get more annoying every time you connect another account.
What changed
Every connected account now has its own Generate switch. A channel with three accounts can write for two of them and leave the third alone, without you dropping the channel or deleting anything afterwards.
Open a channel's settings in New Campaign and the accounts sit under the channel defaults, each with its own switch. Turn one off and it sits this campaign out.

How it works in practice
Switch off the accounts sitting this one out
Every account starts switched on, so a campaign you don't think about behaves exactly as it always has. The switch is there for the times you do think about it.
Flip one off and the row stops advertising settings it isn't going to use. Where it used to summarise what it would produce — EN · Text only — it now reads Skipped for this campaign. There's no ambiguity about whether the Page is disconnected, misconfigured, or simply not part of this particular launch. It's the third one, and it says so.
The count tells you what will actually run
A channel serving more than one account carries a count in its row: 2/3 accounts, alongside the rest of its configuration summary. The same count appears on the expanded account group.
This is the number that matters, because it's the number of pieces the channel is about to produce. You no longer have to expand a channel and audit the account list to work out whether the campaign got bigger than you meant it to. The channel row tells you before you open it.
The estimate follows the switches
The pre-flight estimate — the one that opens when you hit generate, with input and output tokens and a count of outputs — is calculated from the accounts that are actually switched on.
That matters more than it sounds. The estimate is the last thing standing between you and a run, and an estimate that quietly includes two accounts you're about to skip is worse than no estimate at all: it prices a campaign you're not running. Now the outputs it counts and the tokens it projects are for the pieces you'll actually receive. The number you see before generating is the number you get.
Channel defaults still do the work
The per-account switch didn't turn account setup into a chore. Channel settings still hold the defaults — the languages, the output format — and an enabled account inherits them unless you've deliberately customised it. The account row says Inherits when it's taking the channel's word for it.

So the workflow stays the same shape: set the channel up once, then override only where an account genuinely differs. The switch is one more override, and it's the cheapest one — a single tap that removes a piece from the run.
Turning every account off drops the channel
If you switch off all of a channel's accounts, the channel is skipped entirely. You don't have to go back up and deselect it, and the app doesn't generate an orphan piece with nowhere to go.
The whole arrangement saves with the campaign draft, so a campaign you started on Monday and finished on Wednesday still knows which accounts were sitting out. You set it once, not once per session.
Before vs after
| Before | Now | |
|---|---|---|
| Publishing to one of two Pages | Generate for both, ignore one | Switch one off |
| Cost of the skipped account | Paid for, then discarded | Never generated |
| Knowing how big the run is | Expand the channel, count accounts | Read 2/3 accounts on the row |
| Estimate accuracy | Counted accounts you'd skip | Counts only what will run |
| Skipping a whole channel | Deselect it, remember why | Switch its accounts off |
| Coming back to the draft later | Re-derive which accounts you meant | Saved with the draft |
Taking the media with you, in one go
The other change in this release is smaller and lands at the opposite end of the campaign.
A campaign piece with several images or videos attached now saves them as a single ZIP archive. One button, one save dialog, one file — instead of a save prompt per attachment, each one asking where to put a file you were always going to put in the same folder.

The button says Download ZIP (4) when there are four files, so you know what you're getting before you click, and it reports progress while the archive is built. Files that share a name are numbered inside the archive rather than silently overwriting each other — which is the failure mode you'd never notice until the folder came up two images short. The archive is named after the campaign, so a Downloads folder with a month of exports in it is still navigable.
A piece with a single attachment still downloads as a plain file. There's no ceremony added to the simple case.
Who benefits most
Anyone running a personal account alongside a company one. The two rarely want the same post, and until now the tool treated them as one destination. The switch is the difference between two audiences and one compromise.
Agencies and anyone posting on behalf of clients. Several Pages under one channel is the normal shape of that work, and campaigns almost never target all of them. Per-account control is the difference between a campaign tool and a campaign tool you can bill against.
Anyone watching token spend. Every skipped account is a piece that never gets written. On a local model that's time; on a hosted one it's money. Either way it's the estimate telling you the truth before you commit.
Try it
Open New Campaign, expand any channel with more than one account connected, and turn one off. The row will tell you it's sitting out, the count on the channel will drop, and the estimate will agree with both.
It's a small switch. What it buys you is the ability to connect every account you actually have — without every campaign becoming a negotiation with the ones you didn't mean to include.