Released November 20, 2026.
Release 47 brings two large pieces of work. Campaigns in Engage become a complete workflow, from a one-sentence idea to posts scheduled on your Plan calendar, and you can run every step in Leed, from your own AI tool, or from the leed CLI. Know becomes a section of its own, with a view for each question you ask of your analytics and reading depth as its headline measure.
Campaigns
Start a campaign from one sentence
New campaign now opens a modal with a single prompt. Describe the campaign in your own words, and Leed proposes every key element from your idea and from what’s already in Leed: goal, business stage, KPIs, audience, timing, channels, voice and context sources. Each element is listed once, marked as coming from your idea, suggested by Leed, or needing you, and you can edit any of them. While Leed works, the modal shows the step it’s on. Anything it can’t work out, it asks one question at a time.
Nothing is saved until you confirm. Closing the modal first creates no campaign, and a persona Leed proposes is created only if you keep it. Confirming creates the campaign already set up.
Learn more: Campaigns and Deliverables.
Define everything a campaign needs
A campaign now holds the key elements that say what it’s for: its goal, audience, KPIs, launch date, where its posts go, its channels, voice and context. Fill them in by hand on the campaign page, or have Leed or Claude propose them for you to confirm; either way they land in the same fields. Once they’re set, the campaign is ready to plan.
A progress strip follows each campaign through Defined, Researched, Planned, Drafted, Reviewed and Scheduled, and the campaign page shows what to run next.
Learn more: Campaigns and Deliverables.
A campaign page that matches the rest of Leed
The campaign page now follows the same layout as contacts, accounts and personas. The center shows what the campaign is, why it exists and how it’s doing: its progress, KPI performance, goal, audience and timeframe, positioning, key messages and buyer questions. Steps, References, Authors, Channels, Schedule, Analytics and leads, and Settings open from tabs in the right rail.
The header has one button for the next step. Run in your AI tool…, Duplicate and Delete sit in its menu. Dialogs are compact, with less-used fields under Advanced.
Learn more: Campaigns and Deliverables.
A brief for every campaign
Each campaign now has a brief your team can read and edit on the campaign page:
- Narrative: the campaign’s one story.
- Key messages: what the campaign says, each with its sources.
- Buyer questions: the questions each persona asks at each journey stage, with the planned content that answers each one.
- Research: findings from the web, each citing its sources with the date they were read. A finding older than 90 days is flagged as stale.
Leed checks briefs and campaign posts as they’re saved, and points out problems next to the field, such as a message that needs a source. A change written by AI that fails a check is refused; a person’s edit is saved, with the problem shown as a warning.
Learn more: Campaigns and Deliverables.
Plan deliverables before the content exists
Deliverables are a campaign’s calendar, and you can now plan them before anything is written. Add, edit, reschedule, reorder and reject deliverables, with a reason, right on the Plan calendar and the campaign page. A deliverable records the persona, journey stage and buyer questions it serves; a social post also records its channel, account and copy. Each one shows its persona-review result, and you mark a social post done once it’s out.
Editing an approved deliverable’s copy or target returns it to draft; moving its date does not. Deleting a campaign removes its deliverables.
Learn more: Campaigns and Deliverables, Plan Calendar.
Approving a post schedules it
Approve & schedule on the Plan calendar now does both. Approving a page deliverable schedules its page for exactly the deliverable’s date, with the same checks as scheduling the page by hand, so a missing required field or a date in the past keeps it in draft and tells you why. Moving an approved deliverable moves its page. Rejecting it, returning it to draft or deleting it takes the page off the schedule.
A page’s editor now shows the campaigns and deliverables it belongs to, and the calendar flags a deliverable whose page was rescheduled somewhere else. Social posts stay calendar items: approved means ready for you to post by hand on the date. Documentation pages are never scheduled by a deliverable; they publish with your releases.
Learn more: Campaigns and Deliverables.
Run each campaign step in Leed
Every campaign step now has a button in Leed, so a campaign can go from set up to scheduled without any other AI tool:
flowchart LR
S["Set up"] --> R["Research<br/>(optional in Leed)"]
R --> P["Plan"]
S --> P
P --> D["Draft"]
D --> V["Review"]
V --> C["Schedule"]
A step collects every change it would make into one proposal. You review it and approve it in one go, or drop the items you don’t want and apply the rest; nothing is written before you approve. A step can stop to ask you a question, and it keeps running if you leave the page. Review records the model that actually scored the content, and marks the result as not independent when that’s the same model that wrote it.
Research needs live web search, which Leed’s assistant doesn’t have, so in Leed it’s optional: skip it, or run it from Claude or the AI tool you already use with the Leed plugin. Starting a step that writes needs the Content Publisher role.
Learn more: Running a campaign’s steps.
Campaign skills in the Leed plugin
The Leed plugin for Claude adds a skill for each step, so you can run a campaign from your own AI tool. Every skill writes its work back to the campaign in Leed, where your team sees and changes it, and writes nothing without your yes.
| Skill | What it does |
|---|---|
/leed:campaign-setup | Proposes everything a campaign needs from what’s already in Leed, with the source of each value, and asks only about what it can’t work out. Give it a campaign, or a one-line idea to start a new one. |
/leed:campaign-research | Researches competitors, search results, keywords or a topic on the live web, and adds the findings to the campaign’s brief with every source cited. |
/leed:campaign-plan | Writes the brief’s narrative, messages and buyer questions, then puts search-targeted posts and their social copy on your Plan calendar. |
/leed:campaign-draft | Writes each post into Leed as a draft with its SEO details, and each social post sized for its network, in your team’s voice. |
/leed:campaign-review | Reads each draft the way your buyer would, on a different model from the one that wrote it, scores it against your personas’ questions, fixes the gaps once, and shows the result on the Plan calendar. |
/leed:campaign-schedule | Sets each post’s feature image, checks its required details, adds a tracked short link to every social post, and on your approval schedules each post for its date. |
Learn more: The Leed Plugin for Claude: Skills, Running a campaign’s steps.
Use internal docs as campaign context
A campaign can name internal sets or pages, such as your brand voice, messaging or product specs, as context, and the campaign steps read them. Internal pages created over the CMS MCP now show up in search straight away, and the CLI can search internal docs and lock internal pages:
leed page search "brand voice" --section internal
leed page lock <pageId>Learn more: Internal Content.
Campaign pages built from your site’s templates
Not every page a campaign needs is written in the editor. A comparison page or a landing page built as a template in your site repository can now be a campaign deliverable too, with its file path and, if it belongs in your navigation, the menu it goes in. Leed follows it from your repository to your live site: the Plan calendar, the campaign’s Schedule tab, the page’s Campaigns tab and the CLI show whether it is waiting to be pushed, building on staging, on staging waiting for promotion, or live. It is never shown as published until it is live.
The campaign skills in the Leed plugin can read these pages as context, build a new one, push it to staging and check it there, promote it to your live site once you say yes, and add its menu item. Short links for its social posts are created once the page is live.
Learn more: Campaigns and Deliverables, Running a campaign’s steps.
Know analytics
Know is now a section
Know has its own menu, so each kind of analytics has its own page. Views are grouped by the question they answer: Overview and Releases; Readers (People, Agents, Accounts); Content (Pages, Search & gaps, Conversions); Outreach (Email & social, Campaigns); and Trust (Knowledge health, Agent work), with Saved views and Data access below.
One filter bar works across every view. You can filter by page type, by readers (people or AI agents) and by date, and the filters stay in the address bar, so a filtered view can be bookmarked, shared or reloaded. Every list is a table you can sort by any column.
Learn more: Know.
Reading depth replaces bounce rate
Know’s headline measure is now reading depth: how much of a page’s estimated reading time a reader actually spent on it. Reads that reach 75% or more count as read to the end. Depth is measured against the version of the page that was live when it was read, and it appears in Know, in the page editor and over MCP.
Learn more: Know.
A view for each question
| View | What it shows |
|---|---|
| Overview | How much of your content people read, your traffic with each release marked, and what needs your attention, each item linked to the view that explains it. |
| Pages | How far people read each page and page type, what AI agents read, which pages are rising or fading, and where readers come from and go next, with a detail page for each page and its revisions. |
| People | Who reads your content, where they come from and what they use, with a detail page for each identified reader. |
| Search & gaps | What people and AI agents searched for and never found, what’s rising, and what to write next, with the evidence behind each item. Start a draft page from any gap. |
| Conversions | Which pages, journeys, forms and calls to action lead to form fills, with every filter applied, including page type and channel. |
| Agents | What AI agents read and ask in your documentation, which questions your content doesn’t answer, and who tried to connect without access, with a log of every question. |
| Knowledge health | Pages being edited now, pages with no source commit, open reviews and repeat corrections, broken links over time, and what your next release will publish. Agent calls shows exactly which version of each page an agent was given. |
| Agent work | What AI agents did in your CMS, who ran them, where they ran into trouble, which page versions they worked from, and how many of their suggestions your team accepted. |
| Accounts | Each company’s reading activity across people and AI agents, which accounts are going quiet or asking for access, and which releases each account hasn’t seen. |
| Email & social | How each email and short link performed and what readers did next, grouped by the release an email announced, with the best time to send, unsubscribe and bounce trends, and how your email templates compare. |
| Campaigns | What each campaign sent and published, the visits, leads and accounts it brought in, which channels worked, and the pages its leads read before they converted. |
Learn more: Know Views Reference, Search & Gaps, Knowledge Health and Agent Calls.
Releases, recorded by name
Leed now records each release by name. Pass a release version from your CI job, or let Leed name it by date, and see every page that shipped with it. Each release also keeps a report of every run, dry runs included, so you can see what will publish before it goes live.
Know’s new Releases view shows every release’s pages, how quickly people and AI agents first read them, how reads compare with the previous release, who you told about it, and which customer accounts it reached. All releases also lists documentation pages published outside a release.
Learn more: Releases in Know, Continuous Documentation.
Ask about this view
Ask questions about any Know view in plain language. The assistant starts from the view’s filters, reads the data behind the view to answer, and can’t change anything. It’s open to everyone with access to analytics.
Learn more: Saved Views and Ask.
More analytics in the page editor
The page editor’s Analytics panel now shows AI agent reads beside human reads, how much of the page people read, where sessions start and end, the page’s source and release, and its open comments and suggestions.
Document assets now show their downloads, and email templates show how every email built from them performed.
Learn more: Page Analytics in the Editor, Video, Audio and Document Assets.
Growth views, with a preview on other plans
Releases, Agents, Accounts, Campaigns, Knowledge health and Agent work come with the Growth plan. On other plans these views still open, with their real totals and a blurred preview, never a hidden menu item. Leed can also turn a view on for your company below Growth.
Learn more: Know, When a Feature Is Gated.
CLI and MCP
Read Know from an AI assistant or the command line
AI assistants connected to Leed can now read any Know view, with the same filters and the same numbers as the app, and can read form, short link, email and contact activity analytics. From a terminal, leed know reads any view or saved view:
leed know views # list the views and your saved views
leed know show <view> # read one view, with the shared filters
leed know run <savedView> # run a saved viewKnow’s Data access screen explains the MCP tools and CLI commands and lists recent access.
Learn more: Reading Know from MCP and the CLI, leed know Commands, MCP Tools: Analytics and Introspection.
Manage campaigns from the leed CLI
The leed CLI now manages personas, journey stages, campaigns, their briefs and their deliverables, including approving and rescheduling, and runs campaign steps from the terminal: start a step, answer its questions and approve its changes.
| Command | What it covers |
|---|---|
leed persona | Create and edit personas |
leed journey | Create, delete and reorder journey stages |
leed campaign | A campaign’s key elements, audience and brief |
leed campaign deliverable | Approve, reschedule, reject, mark done and reorder deliverables |
leed campaign run | Start a step, follow it, answer its question, approve or cancel its proposal |
leed page create, leed page meta set | A page’s planned date, journey stage and SEO details |
leed campaign run <campaignId> plan --wait
leed campaign run answer <runId> "LinkedIn first" --wait
leed campaign run approve <runId>Approving asks first at a terminal, and needs --yes under --json. The campaign commands need the Growth plan.
Learn more: CLI Command Reference, Running a campaign’s steps.
Journey stages and short links over MCP
Claude and other CMS MCP clients can now create, delete and reorder journey stages, and create tracked short links tied to a campaign, previewing each change before it’s saved. In Settings, Journey Stages can now be reordered by dragging, and the settings home shows how many stages you have.
Learn more: Journey Stages, MCP Tools: Site Structure, MCP Tools: Publishing, Distribution and Users.
Set a feature image from an asset
Claude and other CMS MCP clients can now set a page’s feature image from an asset in the asset manager. Send update_page_metadata the asset’s id and its alt text as featureImage, and Leed fills in the rest, just as the editor’s image picker does. Image rows from list_assets and get_asset now include the image’s path too.
Learn more: MCP Tools: Pages and Content.
Links for every asset over MCP
list_assets and get_asset now return each asset’s public URL and a ready-to-paste Leed Markdown reference for images, video, audio and documents: the same links leed asset upload shows.
Learn more: MCP Tools: Forms and Assets.
Fixes
Form fills no longer re-subscribe people who opted out
Filling in a form used to make a contact mailable again, even after they had unsubscribed. Now a contact who unsubscribed, asked not to be contacted or was reported as spam stays that way when they fill in a form. Someone who simply unsubscribed still gets the form’s own reply, because it answers the request they just made. A contact who never opted out is opted in by a form fill, as before.
Learn more: Unsubscribes and Opt-Outs, Response Emails and Gated Downloads.
Removed people no longer receive form submissions
A form’s notifications are no longer emailed to people who were removed from your Leed workspace or disabled. The form’s notification card flags any such recipient as not notified.
Link previews on X credit your company and authors
Shared links to your pages now credit your company’s X account, from Settings, and a post’s author’s X account in the link preview. Neither is added when no handle is set.
Learn more: Social Cards and Structured Data.
Correct engaged minutes in Know
Engaged minutes on the Know dashboard are now correct; they were shown about 60 times too low, so expect them to rise. Period-over-period comparisons now use windows of equal length, and the site conversion rate counts every session in the window.