52 posts tagged with "News"

This week improves review visibility and makes smaller screens more comfortable when checking email work on the go.

Improvements​

• Reviewer permissions are now shown more clearly, so teams can confirm what reviewers can do in an email workspace.
• The mobile workspace layout has been cleaned up, making navigation and workspace controls easier to use on smaller screens.
• Review sync overrides are now limited to admins, reducing the risk of accidental review configuration changes.

Fixes​

• Preview profile links from segmented emails now open the expected profile and preview context.

This week adds clearer reviewer access and audit history for teams that separate editing, reviewing, and approval.

Improvements​

• Better Email now includes a dedicated reviewer role for email workspaces, making it easier to invite teammates who should review without needing full editing access.
• Review and approval events now appear in the audit log, so admins can see when important workflow changes happened.

Fixes​

• Dragging modules now respects the template's content zones, preventing drops into unsupported areas.

This week continues the review workflow polish and improves how previews, segmentation, and Salesforce Marketing Cloud output behave during day-to-day work.

Improvements​

• Better Email now includes an in-app docs and feedback menu, so help and product feedback are closer to the workflow.
• Review checks now appear sooner and include hover descriptions, making blockers easier to understand before approval.
• Template base comments are now visible in the editor, so reviewers can see relevant template-level feedback while working.
• Approval behavior is more flexible: users can approve after resolving their own comments, while avoiding unnecessary self-approval notifications.
• Notification emails have been polished so review and workflow updates are easier to scan.
• The editor now warns more clearly when it disconnects, helping teams avoid editing while the workspace needs attention.

Fixes​

• Salesforce Marketing Cloud link wrapping now preserves encoded characters, reducing the chance that personalized links change during export.
• Segment permissions are now clearer: owners can finish or archive their own segments, admins retain definition editing, and read-only users can inspect disabled segment fields.
• Salesforce Marketing Cloud exports now use the right saved subject when an email relies on the current draft value.
• Hidden segmentation fallback variants now stay out of exports when they are only needed inside Better Email.
• Duplicating a block now preserves segmentation, variant values, base values, and repeatable values.
• Review previews now keep loading, feedback, and segmented states in sync, reducing flicker and blank preview moments.
• The emoji picker no longer gets clipped inside editor panes.
• Workspace activity and segment counts now show more accurate numbers.

This week improves the path from editing to review, with better approval controls, richer email metadata, and more useful Betty context.

Improvements​

• Subject lines and preheaders can now be edited directly in Better Email, so campaign metadata can stay with the email while it moves through review and export.
• Review comments, approvals, and handoffs now have clearer controls, making the path from draft to approval easier to follow.
• Betty can now work with document attachments and rendered screenshots, making it easier to explain what you need without rewriting context by hand.
• Rich text template inputs can now include a custom tag toolbar, so teams can insert approved dynamic fields from the editor.
• API users can now work with recipient fields used for personalization and segmentation. The docs now include setup, authentication, error handling, and endpoint references for recipient fields.
• Users can now manage their Better Email profile settings from inside the app.

Fixes​

• Selected roles are now applied when inviting a user, so new teammates get the intended access as soon as they join.
• Salesforce Marketing Cloud segment fallback support is detected more accurately during setup and preview.
• Segment names are now checked in the right scope, reducing false conflicts when similar names are valid in different contexts.
• New emails now follow the latest published template revision instead of staying pinned to an older version.

This week focuses on giving template teams more control over complex templates, while making it clearer when saved template changes are ready for marketers to use.

Improvements​

• Template authors can now define multiple content zones, so modules can be dropped into the right part of a template instead of one shared area.
• Repeatable settings can now enforce minimum and maximum item counts, keeping flexible sections within the intended layout.
• Shared reference copy can be overridden where needed, so reused copy blocks can still be adapted to a specific template or campaign.
• Button settings can now include emoji choices, so teams can configure emoji calls to action without custom code.
• Betty can inspect screenshots, which makes it easier to ask for help with the exact state of an email or template you are looking at.
• Template authors now get clearer guidance when a saved revision needs to be published before those changes appear in Email Builder.

Fixes​

• Email Editor now opens directly from Better Email links and navigation instead of getting stuck before the editor loads.

Better Email can now export emails directly to Microsoft Dynamics 365 Customer Insights - Journeys. Finished emails are created as draft assets in Dynamics, ready for your team to review and use in Journeys.

Connect Customer Insights - Journeys​

Admins can now add a Microsoft Dynamics 365 Customer Insights - Journeys integration in Better Email. The setup uses a Microsoft Entra app registration and a Dynamics application user, so exports can run without a separate approval popup each time.

Once connected, the integration appears in the normal export flow alongside your other ESP integrations.

Export drafts to Dynamics​

When you export an email, Better Email creates a draft email asset in Dataverse. The exported email includes the rendered HTML, preview HTML, subject line, and preview text.

If you export the same email again, Better Email updates the existing Dynamics draft instead of creating a duplicate.

Manage subject lines and preview text​

Subject line and preview text export to Dynamics with the email asset. In the current Email Workspace, teams manage them from the inbox preview row on the email itself, so reviewers can check the final inbox copy before sync.

Integration defaults still exist as fallback behavior for older templates or workflows that have not moved those fields into Workspace metadata yet.

Other fixes and improvements​

• Dynamics compliance tokens like company address and preference center can now be preserved correctly during export.
• Exported Dynamics emails now include metadata that helps Better Email update the same draft on future exports.
• Betty can now explain when template changes need to be published before they appear in Email Builder.
• Template authors now get clearer guidance from save to publish, so new modules become available in Email Builder.
• Email Editor now opens more reliably from list, grid, and show pages.

Salesforce Marketing Cloud templates now handle personalized links more safely in Better Email. You can use merge tags and AMPscript in links, and Better Email prepares the final output for SFMC automatically.

Use personalized links with confidence​

Marketers can now add personalized destinations to Link inputs and rich text links. For example, a button can include a merge tag or AMPscript value inside the URL without being rejected by the editor.

When the email is rendered for Salesforce Marketing Cloud, Better Email prepares those links in the format SFMC expects for personalized URLs and click tracking.

Preview with the right integration​

Template preview now includes an integration selector. This lets template authors check how a template renders for different integrations before marketers use it in real emails.

That means merge tags, global values, and integration-specific output can be checked earlier in the template-building process.

Keep merge tags scoped to the right ESP​

Merge tags are now scoped to the integrations where they can actually be used. This makes it easier to pick the right tag and reduces the chance of using a field that will not resolve for the selected ESP.

The same improvement applies across preview and rendered output, so what you test in Better Email better matches what you export.

Other fixes and improvements​

• SFMC integrations now support Business Unit MID, which helps teams export and sync fields in the right business unit.
• SFMC personalized links are automatically prepared for click tracking when they are rendered in anchor tags.
• Email preview code view now falls back to raw HTML when ESP-specific code cannot be formatted.
• The email overview has been cleaned up with clearer labels for language, folder, template, and integration.
• Template preview now keeps integration-specific global values in sync when the selected integration changes.

Global settings and Shared inputs are now available in the Template Editor. Together, they make it easier to build one template that works across brands, markets, languages, and business units.

Set shared values once with Global Inputs and Global Script​

The new Global setting gives every template a place for values that belong to the full email. Use it for things like brand, market, language, theme, colors, logos, or footer details.

Global values can be used across the template base and every module, so you do not have to copy the same setup into each component.

Calculate values with Global Script​

Global Script lets you calculate shared values once and use them everywhere. For example, a template can choose the right logo, color palette, or footer text based on the selected integration.

This is especially useful when several business units share one Email Design System, but each one needs its own brand output.

Reuse input definitions with Shared inputs​

The new Shared setting lets you define an input once and reuse it in multiple modules. A shared color palette, CTA style selector, or alignment control can now stay consistent across the whole template.

Combined with Global Script, shared inputs can be scoped to the selected integration. For example, a background color palette can be defined once and populated with only the brand colors available for the chosen audience — so a module that supports multiple brands automatically limits its options to the right palette when the integration is set.

When the shared definition changes, every module that references it follows the update automatically.

Other fixes and improvements​

• FX mode lets colors, placeholders, and select options follow values from template or global settings.
• Color fields can now show friendly names like Primary Blue instead of only showing hex values.
• Image inputs can now include built-in alt text, so marketers can manage the image and alt text together.
• Image inputs can now enforce size rules, helping prevent images that are too small or too large for a slot.
• Liquid errors now appear directly in the Template Editor and preview, so template authors can find issues faster.
• Betty now understands Global settings, Shared inputs, and FX mode when helping with template work.

Template inputs now give template authors more control over what marketers can enter in the Email Editor. You can guide users toward valid content before review and export, without adding manual checks at the end.

Add validation rules to inputs​

You can now add validation rules to many input types in the Template Editor. Required fields, character limits, "must change from default" rules, and format checks help catch missing or invalid content early.

When something needs attention, the Email Editor shows a clear warning on the field. Review and export stay blocked until the issue is fixed.

Use dedicated number and link inputs​

Templates can now use Number inputs for values like spacing, layout limits, and item counts. Number inputs can include minimum and maximum values, and can be shown as sliders when the value should stay within a clear range.

Link inputs are now built for standalone URLs like button destinations and image links. They support URL validation, HTTPS rules, merge tags, and custom link attributes for tracking or accessibility.

Show fields only when they matter​

Template settings and inputs can now be shown conditionally. That keeps the editor cleaner by hiding fields that only matter after another option has been selected.

Hidden fields do not block review or export while they are hidden, so users are only asked to fix fields that are relevant to the email they are building.

Other fixes and improvements​

• Rich text links and Link inputs can now require custom link attributes, so tracking and accessibility details are less likely to be missed.
• Integration access can now be limited to specific users or groups, so teams only see the exports, segments, and recipient fields they can use.

Segmentation is now live. Target individual modules in any email to specific audience groups — fully integrated with your ESP, no custom setup required.

Step 1: Set up your recipient fields​

Before you can build segments, Better Email needs to know which fields are available in your subscriber data. You can add fields manually or sync them directly from your ESP — for example, pulling attribute sets from Salesforce Marketing Cloud.

Once synced, your recipient fields are available across the platform and ready to use as segment conditions.

Step 2: Create a segment​

Head to Segments in the top navigation and create a new segment. Each segment is tied to a specific integration and can be reused across emails.

Simple mode lets you build conditions using a visual rule builder — pick a field, choose an operator, and set a value. Better Email automatically generates the correct ESP-specific code for you.

Custom code mode gives you full control. Write the conditional logic directly in your ESP's templating language and use {{ content }} as a placeholder for where the module HTML should be inserted.

Step 3: Apply segments in the editor​

With segments created, you can apply them to any module directly in the email editor. Select a module, open the Segmentation panel in the right sidebar, and assign one or more segments to it.

Each segmented module supports multiple variants — one per segment — and an automatic Everybody else fallback for recipients who don't match any of the conditions.

Segments are reusable — define them once and apply them to modules across any email in your account.