Last verified: September 3, 2026
What You Can Now Do
Context Memo now separates campaign creation from campaign publishing: you draft an ad campaign as an editable object, review it, then sync it to OpenAI as a deliberate second step. Before this, one button did both, and whatever happened after submit happened inside the ad platform where you couldn't see it. The change you'll notice most is that a campaign can exist, be wrong, be corrected, and be approved without a single API call reaching OpenAI. The task it changes: budget sign-off. Your approver reviews a concrete draft instead of reading a form over your shoulder or holding the publish permission themselves.
Where It Is in Context Memo
Drafting and syncing live in the ad campaigns area of Context Memo. A draft appears there as its own object with its own state, so the list shows you what's still in draft, what's approved, and what's been synced to OpenAI. The commits don't fix a menu path beyond that area, so check the campaigns screen in your workspace for the current layout.
How to Use It
- Create the campaign as a draft. Fill out naming, budget, targeting, and creative, then save. Nothing is sent to OpenAI. The draft persists with its own state and stays editable.
- Run validation against the draft. Errors that used to appear after a partial campaign object existed now surface while nothing is live. Fix them in place and re-save.
- Send the draft for approval. Whoever owns spend opens the same object, reads the actual budget and targeting values, comments, and signs off. Writers no longer need the publish permission to get a campaign built.
- Sync the approved draft to OpenAI. Sync does one job: reconcile the approved draft with the platform. It's an explicit action, not a side effect of saving.
- Confirm the synced state on the campaign. The draft record stays alongside the synced result, so you keep a clean record of what was intended versus what shipped.
Why We Built It
Teams told us the same story in different words: they hit submit, something failed halfway (a validation error, a rate limit, an expired token), and they were left cleaning up. Orphaned campaigns. Duplicated ad groups from retries. No reliable answer to "what did we actually launch?" The cost showed up twice, first as wasted hours reconciling the ad platform by hand, then as spend going live on a configuration nobody had formally approved.
The permissions problem was the other half of it. In most B2B teams, the person who writes campaigns and the person who approves the money are two different people. Direct publishing forces a bad choice: give the writer publish rights, or make the approver do data entry. A persistent draft object removes the choice. The pattern is well established in advertising tooling for exactly this reason; Google Ads has supported draft campaigns and experiments for years, and Meta Ads Manager holds unpublished drafts in a review state.
Moving friction left is the whole point. Validation, naming conventions, budget checks, and creative review all happen against a draft. Sync then reconciles an approved object with the platform and nothing else.
What It Does Not Do Yet
- OpenAI is the destination this workflow covers. Other ad platforms aren't part of draft-and-sync yet. If you run campaigns elsewhere, keep building those in the platform's own tooling for now.
- Sync-time failures still exist. Draft-then-sync doesn't eliminate rate limits or expired tokens; it moves them to a single, deliberate step where you know exactly which draft failed and can retry against an unchanged record. That's a cleaner failure, not the absence of one.
- Approval is a workflow, not a hard gate we invented for you. The draft object gives your approver something to review and sign off on. How strictly you enforce that sequence is still a process decision on your side.
- Context Memo is not your CMS or your marketing automation platform. Those tools do more, and we don't try to replace them. Draft-and-sync is built to make campaign publishing auditable, not to become the system of record for everything upstream of it.
If you're mid-quarter and carrying a backlog of campaigns built under the old single-action flow, rebuild the next one as a draft first and compare the two records side by side. The difference in what you can hand an approver is the part that's hard to explain and obvious to see.