Skip to main content

Safer Recipient Fields and Email Checks

Nicki Pabst
Co-founder & Email wizard

This week makes it easier to build accurate audience segments, catch email issues before export, and keep shared libraries permission-safe.

More precise recipient fields

Salesforce Marketing Cloud date fields now work more naturally in segments. Teams can build date-based rules with conditions such as on, not on, before, after, empty, and not empty instead of treating calendar values like plain text.

Admins can also guide marketers toward approved text values for recipient fields, then choose whether exceptions are allowed. Strict fields prevent new out-of-list values while older saved values continue to work.

More accurate email checks

Email checks can now cover more of the review process, including copy, brand, links, images, accessibility, placeholders, file size, and rules your team has configured. Reviewers can inspect findings in preview, dismiss false positives, turn them into comments, or ask Betty to help fix them.

Segmented emails are now checked separately for each audience version. VIP, fallback, or other audience-specific blocks no longer create misleading warnings as if every version appears to the same recipient.

Improvements

  • Template developers can give Betty uploaded .html files or pasted notes as context, making it easier to adapt existing creative or campaign guidance.
  • Marketers can ask Betty to insert recipient fields from a searchable catalog instead of remembering exact field names while personalizing copy.
  • Email library filters now include a created-by option, making it easier to find work from a specific teammate.

Fixes

  • Folder permissions now carry through nested folders and into the email workspace, so restricted users no longer see or open emails outside their access.
  • Folder counts now stay trustworthy for restricted users, making the email sidebar easier to scan for folders they can read.
  • Expired invitations can be resent from the invite dialog instead of being blocked by the previous invitation.
  • Exports now respect the minify setting, and subject or preview-text checks no longer block integrations that do not support those fields.