Figma Integration, Now Available
Designers can now work from Stensul-governed templates inside Figma and push finished designs back into Stensul, with guardrails checked on export. The design-to-email rebuild goes away.
How it works
Install the Stensul plugin in Figma and connect it to your Stensul instance. From there:
Pull approved templates and modules from your Stensul library into Figma. Only pre-approved content is available to the designer.
Design in Figma with full editing of text, images, colors, buttons, dividers, and spacing.
Push the design back to Stensul in one click. No export files, no handoff.
Guardrails validate the design against your module rules on export and flag anything outside brand rules before it lands in Stensul.
The design arrives in Stensul ready for your normal review and approval process. Designers can pull templates back in and keep iterating without breaking the connection.
For a full breakdown, see the Figma Integration help article.
Stensul Email Previews, Now Available
Render testing now runs inside Stensul. Test emails across more than 110 email client and device combinations, with accessibility, link, image, and spam checks in the same governed environment where the email was built.
How it works
Preview real renders across web and mobile clients, including dark mode and light mode variants, each timestamped
Run accessibility, link, image, and spam checks before send
QA and get sign-off without leaving Stensul or moving the email into a separate testing tool
Teams that use an external render testing tool today can retire that step. The check happens where the email lives.
AI Campaign Creation: Kickoff (Beta)
You can now start AI Campaign Creation by uploading the brief you already have. Stensul parses it and generates a first draft inside an approved template, within your brand rules. No retyping the brief into a prompt.
How it works
Upload a .docx, PDF, or .xls file up to 10 MB. The legacy .doc format isn't supported.
The parsed brief becomes the primary prompt. An optional instructions field adds tone, audience, or CTA notes on top without re-uploading.
Stensul maps the brief into your selected template and generates a draft inside your guardrails.
You can start from a typed description or an uploaded brief, one or the other. Your library needs at least one template for this to work.
How to get access
AI Campaign Creation: Kickoff is in beta. Contact your CSM to enroll.
For a full breakdown, see the AI Email Creation: Brief Upload (previous name) help article.
Governance Agents: Accessibility QA Check v1.1
The Accessibility QA Check now goes deeper than what's visible on screen. Six new checks cover the structure of the email, not just its surface: link and button accessibility, language tags, table markup, list semantics, custom code and custom elements, and support for MCP-connected creation.
How it works
The check runs against rendered HTML, mapped to WCAG 2.1 AA, and flags issues before send. It now runs wherever the email gets created:
Email Builder
AI-assisted creation
Any agent connected through Stensul MCP
An issue that used to surface after send, like broken table markup a screen reader can't parse, now gets caught while the email is still in the builder. The v1 checks (alt text, color contrast, heading structure) still run as before.
WRITER Connector (Beta)
Approved copy from WRITER can now move directly into production-ready emails through Stensul MCP. No copy-paste, no manual handoff, and the governance record stays intact.
How it works
Copy is drafted and approved in WRITER using your brand-voice models
Through Stensul MCP, that approved copy is called into a governed Stensul template, mapped into modules with structure and formatting intact
The assembled email routes through your existing Stensul approval workflow: same reviewers, same path, nothing new to configure
Content that didn't change doesn't get re-reviewed
How to get access
The WRITER Connector is in beta. Contact your CSM to talk through whether it's a fit for your account.
Dynamic Content: Segment Management, Now Available
Administrators get a control center for dynamic content segments across libraries. Segments are no longer global by default.
How it works
Five changes:
Library-scoped by default. A segment created in one library stays there unless an admin promotes it globally.
Centralized admin panel. One view of every segment, which libraries it lives in, and what actions are available, instead of opening emails library by library.
Soft delete. Admins can retire deprecated segments. Any email still referencing a deleted segment shows a warning before it can be completed.
Split permissions. Renaming a segment and editing its conditional logic are now separate permissions.
Auto-clone on duplication. When an email moves libraries, its segments travel with it as independent copies.
For a full breakdown, see the Managing Segments for Script Based Dynamic Content help article.
Landing Pages: Interactive Elements, Now Available
Carousels and accordions are now native elements in the Landing Page Builder. Rotating multi-slide sections and collapsible sections can be added by dragging them in, no code or developer needed, inside your brand guardrails.
Landing Pages: Form Preview Accuracy
Forms from Pardot, Marketo, and Eloqua now preview exactly as they'll appear on the published page.
Previously, security protocols stripped scripts and styling from MAP forms in the builder, so previews could show missing submit buttons or wrong dimensions. The connector now preserves the original form code inside a secure, sandboxed iframe. The form looks the same in the builder, the preview, and the live page. Desktop, tablet, and mobile previews are all available before publish.
Coming: Salesforce Marketing Cloud Next Support
Stensul has announced planned support for Salesforce Marketing Cloud Next and for customer migrations to that platform, building on our SFMC integrations today. The goal: governed, approved, personalization-ready content moves with your team into MCN. If your organization is planning an MCN migration, contact your CSM to talk through timing.
Status colors are now consistent across the platform
What's changing: We're unifying how status tags are colored everywhere in the platform. Anything that's actively moving through a workflow, like a draft email, a proof in progress, or a translation being worked on, now appears in blue no matter which screen you're on.
Blue means work in progress. Everything is fine; it's just not done yet.
Green means complete or approved.
Amber means it needs your attention (something is outdated or unpublished).
Red means something actually failed.
Users can read status at a glance anywhere in Stensul without interpreting screen-specific color meanings.