Campaigns Overview

Overview

Campaigns are company-scoped containers for time-bound communication initiatives that may span one or many workspaces (brands, regions, or client properties). Where the evergreen content strategy + calendar drives ongoing editorial rhythm inside a single workspace, campaigns add a coordination layer: one name, one date range, optional source documents, a shared parent strategy, and child strategies per target workspace that inherit objectives while adapting products, audiences, channels, and destinations locally.

CntX reuses the same ContentStrategy model for campaigns—typed as campaign / one-off mode—rather than maintaining a simplified parallel planner. That design keeps generation contracts consistent: goals, pillars, content types, funnel mix, and channel effort behave like recurrent planning, but recurrence controls and auto-brief schedulers are hidden where inappropriate.

A typical campaign lifecycle moves through Documents → Strategy → Plan → Review: attach messaging inputs, generate and edit strategy (shared tab plus per-workspace tabs), produce plan slots and briefs into each target calendar, then approve or remove briefs in Quick Review before production. Multi-workspace campaigns suit agencies, holdings, and product families launching together; single-workspace campaigns still help when you need document grounding, bounded dates, and dedicated review queues for a launch.

When to use

Choose campaigns when you:

• Run an initiative across multiple brands or clients under one company with shared messaging but local execution.
• Need source documents (decks, research, legal copy) attached at the initiative level, not scattered in workspace folders.
• Want Quick Review and campaign-scoped generation status instead of hunting evergreen calendar items.
• Operate on a fixed window (product launch, event, seasonal push) with a clear end date.

Stay with evergreen content strategy + calendar when publishing is continuous, not bounded, and only one workspace is involved.

Before you start

• Configure Your Company Context in each participating workspace—child strategies bootstrap from local products and audiences.
• Create or confirm workspaces for every brand that must publish; campaigns do not copy briefs to untargeted workspaces.
• Decide campaign name, start/end dates, and which workspaces become targets.
• Align on calendar capacity policy if your build exposes it—some campaigns count against editorial cadence, others stack additively (affects conflict warnings).
• Identify approvers per workspace; generation creates briefs, but local editors must approve before production.

Steps

Understanding the campaign architecture helps before you click Create:

1. Campaign shell — Metadata at company level: name, description, dates, status, links to documents, strategy, plan, and generated items.
2. Campaign targets — Each row connects the campaign to a workspace. Targets determine where child strategies and calendar briefs land.
3. Shared parent strategy — Cross-workspace objectives, key messages, and shared pillars edited on the campaign strategy Common tab.
4. Child strategies — Per-target ContentStrategy records linked to the parent; local products, audiences, channels, and destinations differ per brand.
5. Plan generation — Produces dated slots and briefs into each target workspace calendar, tagged to the campaign.
6. Review and production — Approve briefs per workspace, generate content, publish via connected CMS integrations.

Operational sequence (detailed in linked guides):

1. Create a Multi-Workspace Campaign with targets and dates.
2. Add Source Documents to a Campaign when messaging inputs exist.
3. Generate and Edit a Campaign Strategy on shared and workspace tabs.
4. Generate Campaign Plans and Briefs into calendars.
5. Review, Approve and Remove Campaign Briefs before content generation.

Expected result

You can articulate how one initiative flows across brands: shared story centrally, localized execution per workspace calendar. Campaign detail shows connected targets, strategy state (pending, in progress, ready), document list, and generation progress.

After plan generation, each targeted workspace calendar contains campaign-tagged items with briefs aligned to both parent messaging and local context. Evergreen calendar items may still exist alongside; use filters to focus review.

Tips

• Do not duplicate strategy manually — Edit the campaign-linked strategy, not orphaned workspace strategies, or briefs will diverge.
• Add targets before strategy generation — Late targets require re-running strategy bootstrap for the new workspace.
• Context-empty workspaces produce empty child strategies — Run Context Discovery per brand first.
• Overlapping campaigns — Two active campaigns with the same targets and dates flood review; archive obsolete campaigns.
• Single-workspace campaigns — Valid for document-heavy launches without multi-tab complexity.
• Calendar vs campaign — Evergreen rhythm stays in content strategy; bounded coordinated pushes use campaigns.
• Regenerate stale plans — When dates or strategy shift materially, use regenerate flows rather than editing dozens of briefs by hand.

Next step

Create a Multi-Workspace Campaign with your workspace targets and date range, then attach documents or proceed directly to strategy generation.