Last verified: September 9, 2026
What You Can Now Do
Context Memo now lets you edit ad creative after review and resubmit it without losing progress or triggering a full re-review cycle. A flagged ad stays the same object in your account. You open it, fix the element that was flagged, and send it back. Reviewer notes, version history, and the prior approval state travel with it, so the image, landing page, and disclosure language you already cleared keep their status while the changed line gets re-examined. The practical change for you: when one headline gets flagged, you stop duplicating the creative and re-entering targeting, naming conventions, and assets. You edit in place.
Where It Is in Context Memo
Open any creative in your account that has been through review. The detail view now shows the review state, reviewer notes, and version history on the same screen as the editable fields, with an edit action available on flagged and reviewed items rather than only on drafts. Resubmission happens from that same view. Nothing new to configure and no separate queue to visit.
How to Use It
- Open the flagged creative from your account. The detail view shows which specific elements were flagged and the reviewer notes attached to each one.
- Edit only the flagged element. Leave the untouched assets alone: changing them expands what gets re-evaluated.
- Check the version history panel before you resubmit. It confirms which elements carry their prior approval state and which ones are newly changed.
- Resubmit from the same view. The creative keeps its original identifier, so the record stays continuous instead of forking into a near-identical copy.
- Confirm the review scope on the returned item. Re-evaluation should be limited to what you changed, which is the signal that the edit was scoped correctly.
If the concept itself was rejected and needs a fundamentally different approach, duplicate and rebuild instead. Editing in place is the wrong tool when nothing about the original is being preserved.
Why We Built It
The old pattern was destructive. One flagged headline or an image with too much text meant duplicating the creative, re-uploading every asset, re-entering targeting and naming conventions, and pushing a brand new object into the queue as if it had never been reviewed. Everything review had already cleared got thrown out along with the one thing that failed. Teams running dozens of variants per campaign lost hours to clerical rework, and the audit trail fragmented across near-identical duplicates nobody could later tell apart. That second cost is the one that hurts at scale: when a compliance question comes back weeks later, you need one continuous record per creative, not six orphaned copies with no clear lineage.
Scope is what makes this work. A review system that knows which elements changed can limit evaluation to those elements instead of starting from zero. Revised body copy gets re-examined. The untouched image keeps its prior status. Iteration compresses from a multi-day loop to a same-day one, and the creative keeps a single unbroken history.
What It Does Not Do Yet
A few limits worth knowing before you change your workflow:
- Concept-level rejections still require a rebuild. If the review outcome rejects the underlying approach rather than a specific element, editing in place does not help. Duplicate and start over, and accept the full re-review.
- Scope depends on what you touch. Editing an asset that was previously approved returns it to unreviewed. There is no partial edit of an approved element that preserves its status.
- Approval state is not portable across creatives. Clearing a disclosure line on one ad does not pre-clear the same line on a different creative object. Each creative carries its own record.
If your team's process currently assumes every resubmission is a new object, update the internal runbook before rollout. The most common failure mode we expect is habit: someone duplicates out of muscle memory, and you end up with the fragmented audit trail this release was built to eliminate.
