All Docs
a blue background with lines and dots

Ads Suite

Ads Composer: Draft and Apply Edits to Existing Ads

Ads Composer is a draft-based editor for changing existing LinkedIn ad sets, campaign groups, and creatives. Drafts are reviewed against a diff of the live state and applied as partial updates. Learn the workflow, what you can edit, and what falls outside its scope.

2 min read

Ads Composer: Draft and Apply Edits to Existing Ads is part of the authenticated Revenue Proven workspace. Composer supports new campaign drafts plus reviewed edits to existing campaign groups and creatives. New drafts save, validate and submit for approval; only explicit existing-object Apply actions write to LinkedIn. The page is documented against the current production interface rather than a mockup or an obsolete navigation path.

What this guide covers

A Composer draft opens the guided campaign-building workflow with saved values for the selected draft and account. The controls and values shown depend on the signed-in workspace, its connected providers, plan entitlements, member role, and any data already synchronized or seeded for demonstration.

Use this article to understand the page’s purpose, where its data comes from, and the safest next action. Revenue Proven separates read-only analysis from explicit mutations so that opening a page never implies that an external write has occurred.

Current product workflow

A Composer draft opens the guided campaign-building workflow with saved values for the selected draft and account. This screenshot was captured from the current production route while signed in to the populated Shawn Brown demo workspace.

Ads Composer campaign draft wizard showing campaign details and the guided step sequence
Ads Composer campaign draft wizard showing campaign details and the guided step sequence. Captured from /dashboard/ads-composer/9149670d-1fd2-5428-9177-9e20c28d8b8f.

Move through the numbered steps, save locally, validate the complete draft, and submit it for approval. New drafts do not publish directly to LinkedIn from this screen. Interface labels and availability follow the current plan, role, connection, and workspace context.

The screenshot uses a mode=new seeded demo draft. It is safe to view; do not save or submit while documenting unless changing demo workflow state is intended. Confirm the active workspace and understand whether a control reads data, changes local configuration, or calls an external system before using it.

Data, access, and permissions

The screenshot uses a mode=new seeded demo draft. It is safe to view; do not save or submit while documenting unless changing demo workflow state is intended. Real synchronized values can change after a scheduled sync, while seeded demo rows are deterministic examples and must not be presented as customer benchmarks.

Feature availability is enforced on the server. A button may be hidden or disabled when the workspace lacks the required plan, add-on, OAuth scope, account role, owner permission, or rollout flag. Team membership never bypasses owner-only write guards.

Operational guidance

Before changing anything, verify the active workspace, selected account, date range, provider filters, and saved configuration. If a screen looks incomplete, allow asynchronous charts and grids to finish loading and check Workspace > Connections for sync health.

Use read-only preview, filter, export, and drill-down controls freely. Treat controls labelled Save, Submit, Apply, Resume, Sync, Send, Publish, Delete, Reconnect, or Regenerate as state-changing actions and confirm their effect before continuing.