Amplify UP
← All docs

Release notes/2026

October 2026 release

Journeys and personas include all your recent visitors · Preview editing only accepts changes from Amplify UP · Ask questions about your data from your own dashboards · Help text, icons and required fields · Content edits and publishing stay within your workspace · Build a journey/funnel by hand · Add off-site steps to your journeys · Create, edit and publish pages from your AI assistant · Your AI assistant finds what it can do, in the right organization and site · Sites are protected from request floods · Form field tracking no longer records what visitors type · Visitor activity is no longer lost when a site sends its own event ids · Ask your AI assistant about your campaigns · Page loading errors no longer show technical details · Publishing tells you when content is still in Draft · Workflow notifications are sent reliably and only to secure public addresses · Publish articles that started as drafts in your content source · A failed publish no longer leaves your site on the new version · Adding a form webhook no longer leaves a half-saved one behind · Add images to text in Composer · The text editor stays open after you save · Composer no longer loads internal network addresses · Invited teammates can join, and only the invited person can · Draft pages stay private to your team · Zone publishing works only on your own sites · Sites work in every organization you belong to · Zone lists show only your own site · Composer preview shows only your own site · Refresh preview keeps your selection · A pricing page with a monthly bill estimate · Creating a page in Composer keeps what you type · Tasks and an assistant for work across your sites · Signing in after leaving an organization · A simpler start for new organizations · Faster goals, experiments and campaigns pages · Content releases on your dashboard · A cleaner Composer top bar · Ready-made form and layout components for your site · A fresh dashboard home · Mark pages Ready, schedule them, and see what will publish · Workflow gets its own panel in Composer · Start new pages in Composer · One name for Entities · Dialogs keep your work · Tidier Composer side panel

Feature

  • Ask for visits, page views, visitors and events by day, hour, page, country and more, across the sites a connection can reach.
  • Detailed questions, such as breaking events down by your own event properties, show an estimate and ask you to confirm before they run.
  • Run a detailed question once, or save it so its result stays up to date without asking again.
  • Add traits, signals and audiences to the people in a result, and filter on them.
  • Your organization has a daily allowance for detailed questions; when it is reached, a task tells you.
  • An AI tool now starts each session already knowing your organization, your sites and what you have set up.
  • Add help text, an icon and a Required flag to page fields, taxonomy fields, content type fields and component settings.
  • Editors see the icon and help text next to each field in Composer and the content editor, with a mark on required fields.
  • Mark Ready is refused while a required field is empty, and the message lists exactly which fields to fill in.
  • Create a journey/funnel from a blank map: name it, pick a goal, then add stages made of pages, on-site events, and off-site steps.
  • Reorder stages and the steps inside them, and see each step marked Tracked or Planned as you build.
  • On-site events now count as steps, so a stage can be reached by an event as well as a page.
  • Add off-site steps (call center, email, CRM or in store) to any journey stage, next to its pages.
  • See at a glance which steps are Tracked and which are still Planned, on the journey map and in the stage details.
  • Journeys with an off-site step follow each person across visits, so a call followed by a visit to your pricing page counts as one path.
  • See your site's pages from your AI assistant, and the newest pages of any collection, such as your articles.
  • Ask what a new article needs before creating it, then create it as a draft in your connected content source.
  • Edit a page, move it to Ready, and publish it, with the same drafts, Ready and Live steps you use in the dashboard.
  • A page cannot be marked Ready while required fields are empty, and your assistant is told which ones.
  • Your AI assistant finds what it can do by searching, then reads how an action works before running it.
  • Switch between the organizations and sites you belong to without leaving your AI assistant.
  • Connect tools that cannot sign in with your account by using an organization API key.
  • Connect Claude, Cursor and other AI assistants to Amplify UP by signing in with your account.
  • List your campaigns across every site you can access, or narrow to one site.
  • Open any campaign to see its status, priority and dates.
  • You only see campaigns from organizations you belong to.
  • Add an image to rich text from the new Image button: upload a file, paste a link, or choose from your media library.
  • Paste or drop an image file straight into the text editor to upload and place it where you pasted it.
  • Select an image in the text to edit its alt text or remove it.
  • A new Pricing page shows the Cloud plan, founder pricing, and everything included each month.
  • Estimate your monthly bill by adjusting sites, seats, events, and AI credits.
  • Compare what the Cloud plan and the upcoming Perpetual License include, side by side.
  • New Tasks page under Organization: track to-dos with a status, assignee, due date and checklist steps.
  • Link a task to one site, several sites, or none.
  • Each task gets a short number like TASK-14, so it is easy to mention.
  • See just your own tasks or everyone's, and filter by site.
  • New Assistant panel on your dashboard home, with your tasks one click away beside it.
  • Suggested next steps on the dashboard, based on your last 7 days of visitors.
  • Chat with the assistant to plan a goal: it checks what your sites already have and proposes a task with steps.
  • Create the proposed task, or add a suggested step to an existing one, with one click.
  • Apply a step's change with one click, such as turning on a trait, creating a campaign or goal, or tracking a new event. Nothing changes until you apply it.
  • Mention a task like TASK-14 in the chat to pick up where you left off.
  • Your chats are saved, so you can reopen any of them from the Chats tab or from a task.
  • A new Content releases card on the dashboard shows pages and social posts published in the last three weeks, tagged with their campaign.
  • The same card lists upcoming scheduled page and social post releases, soonest first, so you know what goes out next.
  • Add forms built in Amplify UP to any page by installing the forms package; it handles fields, validation, submission and the Form Submit event.
  • Install the layout package to get a Grid and a Container in Composer when your site has no layout components of its own.
  • Component libraries can describe their components once so every site that installs them can use them in Composer.
  • Mark a page Ready for Publish, then publish it now or schedule it for a date and time; cancel or publish early whenever you need to.
  • Before you mark Ready, publish or schedule, see each component's content and what happens to it — components that would show empty are highlighted.
  • Layers in Composer show each component's content status and how many pages share it; click it to open that content's versions.
  • Content Ops shows each page's status and scheduled time, lets you filter by Scheduled, and flags pages that need attention — such as a page published with empty content — with the content, the reason and who caused it.
  • Campaign contributions delivered as a Composer page now follow that page's status; a page scheduled on or before the contribution's date counts as Live.
  • Roll a page back to any earlier publish from its version history: see what goes live first, then the page and its content return to how they were.

Improvement

  • When your content source's required setting differs from yours, the field shows a short note. Your setting still applies.
  • The new Create menu starts a journey/funnel from the explorer or from a blank map.
  • Editing stages opens the full builder instead of a small window.
  • Every action runs in a single organization and site, so you never see another organization's campaigns by mistake.
  • Listing campaigns and opening one campaign are now a single action.
  • Pages, forms and personalization requests now have a per-site and per-visitor limit. If a site or a single client sends far more requests than normal traffic, the extra requests are answered with "Too many requests" and can be retried a few seconds later, so one flood can no longer slow down other sites.
  • Requests that name a site that has never published anything are now refused with "Unknown site".
  • The Pricing links in the header, footer, and home page now take you straight to the full pricing details.
  • New organizations go straight to creating their first site, without a fixed checklist that may not match how you plan to use Amplify UP.
  • Goals, the goal catalog and individual goals open instantly when you return to them.
  • Publishing, pausing, archiving or restoring a goal updates your goals list and the Journeys goal picker right away, with no page refresh.
  • Experiments open instantly when you return to them, and finishing an experiment from its page or from Composer updates both right away.
  • Campaigns, the planner, the schedule and contributions open instantly when you return to them.
  • Adding, editing, moving or deleting a contribution updates the campaign, planner, schedule and content views together, with no page refresh.
  • Workflows open instantly, and new or renamed steps show up in contribution forms and the planner right away.
  • The Composer top bar now shows just your page name and undo/redo, so there's more room to focus on the page.
  • Page status, version and content readiness now live only in the Workflow and Page info panels on the right, so you no longer see them in two places.
  • The Pages, Layers and Zones panel on the left is a little wider, so longer names are easier to read.
  • The Components list shows whether each component comes from your site's code, an installed package or the dashboard.
  • Components removed from your site's code stay listed with when they were removed, instead of disappearing, and existing pages that use them keep working.
  • All Amplify UP commands now come from the Amplify UP CLI; sites not on Next.js build their component list with the CLI instead of the SDK.
  • The home page leads with this week's headline numbers compared with last week, plus daily traffic and who your visitors were (people, AI and bots).
  • Top pages and top countries sit right on the home page, each a click away from the full report in Insights.
  • Layouts, providers and components are gathered in one "Your site" card with their counts, each linking to where you manage them.
  • Publishing a page takes all of its Ready content live together; if any of it can't be published, nothing goes live and you can try again.
  • Editing content no longer changes the status of the pages that use it; editing a Ready or Scheduled page now asks first, then moves it back to Draft and cancels any schedule.
  • The top bar tells you when content on the page is still in Draft and takes you to the Workflow panel; Layers only flags content that isn't Live yet.
  • Live content is protected from accidental edits: click New version on the component (or in the Content panel) and you're straight into editing a new draft, with a heads-up when other pages share that content.
  • The selected component's toolbar shows its content status at a glance, with one quick action — New version or Mark Ready — and a click on the status opens the Workflow panel.
  • The Workflow panel shows the page's status, what its next publish will do and a checklist of all its content; select a component and it shows just that component's content, one card per piece with its status in plain words and the next step.
  • A page that has been live can always be published, even while you work on a new draft: Publish takes the Live version and any Ready content live again, and your draft stays a draft.
  • The Content Ops timeline shows each page version once, on the day it went live, labelled with its version (for example Homepage v1, Homepage v2); publishing the same version again doesn't add another entry. A busy day stays tidy: one page's versions share a chip (Homepage v1–v3), pages built from the same design share one (Insights article · 10 pages), and a click lists what went live.
  • Writing on the page is simpler: the text editor has an Undo button, clicking away keeps what you typed without asking, and Save (or Ctrl+S) saves it, with a warning if you try to leave before saving.
  • A component's Draft, Ready and Live status, versions and assignees now open from their own Workflow panel, so the Content panel stays focused on editing.
  • "Data modeling" is now called Entities in the menu, breadcrumb and page title, and the page uses that name throughout.
  • Dialogs stay open until you close or cancel them, so a stray click outside or the Escape key no longer throws away what you've entered.

Fixes

  • Journey numbers, persona insights and trait previews now include all of your site's recent visitors, even on busy accounts, so new visitors are no longer left out.
  • Live editing in the Composer preview now only accepts changes sent by Amplify UP, so another website can no longer change what a page shows.
  • Creating, editing, previewing and publishing content now always checks that the site belongs to your workspace, so you can never change another workspace's content.
  • Form field tracking now records which field a visitor interacted with and whether it was filled, never what they typed, so personal details like emails and phone numbers are no longer stored.
  • Visitor activity is no longer lost when a site sends its own event ids, so profiles and reports count every event.
  • When a page fails to load on your site, visitors now see a plain error instead of technical details about what went wrong.
  • The publish dialog now names content that is still in Draft and won't go live, instead of showing it as a quiet row in the table.
  • Marking a page Ready now also marks the article it is built from Ready, so a pattern page and its article go live together.
  • Workflow notifications can now only be sent to secure public web addresses (starting with https://), so they can't be pointed at private or internal places.
  • Workflow notifications are now sent as part of saving the change, so they are no longer lost.
  • When a notification can't be delivered, the log records the address's host and the reason, but never what the other side replied.
  • Articles that began as a draft in your content source now publish from Amplify UP instead of failing with "Nothing went live".
  • A publish that fails at the last step puts your site back on the previous Live version, so "Nothing went live" is true.
  • If the site can't be put back, the message now says it may already show the new version and to publish again.
  • If adding a form webhook fails, nothing is saved, so you can add it again and still get its signing secret.
  • A form can no longer end up with more than 10 webhooks when two people add one at the same moment.
  • Uploading to or browsing the media library of a site outside your organization is now refused.
  • The text formatting toolbar in Composer now stays open after you save, so you can keep editing without selecting the text again.
  • Composer now refuses to load styles, fonts and images from internal network addresses, so the dashboard can't be used to reach private systems.
  • The Composer page preview no longer follows a site's redirects to internal network addresses, and shows a clear message instead.
  • Invited teammates can now accept an invitation and join a workspace even if they do not belong to one yet.
  • An invitation can now only be accepted by the person it was sent to, so a forwarded invitation link no longer lets someone else in.
  • Your unpublished draft pages can now only be previewed by people signed in to your organization, so a site's tracking ID alone no longer shows them.
  • If a Composer preview link runs out, you now see a short "This preview needs a refresh" message with a Reload preview button.
  • Publishing a zone now only works for sites in your organization, so nobody can publish another organization's zone.
  • A published zone now shows the person who published it, instead of a name supplied with the request.
  • If you belong to more than one organization, you can now open and edit the sites in every one of them, not just the first.
  • New sites are now created in the organization selected in the dashboard.
  • Zone lists now only ever show zones from a site in your organization, so no other organization's zones can appear.
  • Composer preview only ever shows pages from your own site.
  • Refresh preview keeps the component you had selected.
  • When you create a page in Composer, the name and URL you type are kept even if you start typing before the form has finished loading.
  • The page preview in Composer no longer stops with an error while your site loads or when you refresh it.
  • If you're removed from your only organization, or it's deleted, signing in now takes you to create a new one instead of loading forever.
  • Publishing a page now includes content connected to components placed inside other components, and to the page's layout, so nothing is left out.
  • Content you publish shows on your site straight away, instead of up to five minutes later.
  • Edge Status in Composer no longer shows a separate version number that didn't match the page's own version.
  • Component toolbars and the on-page text editor in Composer now work on the first load, instead of sometimes needing a refresh.
  • Save in Composer now saves text still open in the on-page text editor, and tells you if it couldn't, instead of saying the page saved without it.
  • Images picked from a connected content source stay set after you save, instead of the field clearing.
  • New content you create in Composer now shows on your live site after you publish the page, instead of the component appearing empty.
  • A page with no components yet now shows its outlined content area in Composer, so you can add the first component.
  • The "rules for every page / this page only" picker now sits below the panel title, so it no longer hides behind the button that collapses the side panel.
  • Events and Analytics panels no longer show a second close button on top of the collapse button. Use the back arrow to return.