Flow Marketing Cloud Updates

Send Marketing Cloud Engagement emails in segment-triggered, event-triggered, activation-triggered, and broadcast flows. Trigger automation event-triggered flows when records related to an individual are changed. Get more control over schedule-triggered flows with more granular scheduling options. Use contact point selection rules to make sure your messages get to the right person. Send email messages using activation data.

  • Automate Marketing Cloud Engagement Emails from Flow Builder
    Send Marketing Cloud Engagement emails via segment-triggered, event-triggered, activation-triggered, or broadcast flows. The Send Marketing Cloud Engagement Email action efficiently targets Data 360 audience segments using your existing Marketing Cloud Engagement content and settings without requiring segment activation or data replication.
  • Ensure Recipients Don’t Get Duplicate Messages
    Use contact point selection rules to send messages to the right individual record and a single messaging contact point. This update improves message precision. The update also enables flows to retrieve contact points from source systems, so that a contact point can be selected even if identity resolution or the data graph has not been refreshed.
  • Send Email Messages Using Activation Data
    In activation-triggered flows, to include data from the activation in the Send Email Message action, use the $ActivationData variable in the email.
  • Run Segment-Triggered Flows at The Right Time with More Scheduling Options
    Run segment-triggered flows on customizable schedules for more control and precision. For example, run a flow every hour to ensure you're working with the latest data, or schedule flows to run only on weekdays to avoid weekend sends. New scheduling options include Hourly, Daily on Weekdays, Weekly on specific days, Monthly on specific days, and Yearly.
  • Get More Targeted Segments in Segment-Triggered Flows
    Create segment-triggered flows with segments built on Individual data model object (DMO) and engagement records, not just a Unified Individual DMO. For example, create a segment of all contacts converted yesterday. This update enables more precise targeting and provides access to engagement-specific data like order details or registration information.
  • Test Multiple Records in Segment-Triggered Flows in Debug
    Test up to 10 records simultaneously. Use the debug panel to instantly verify how different customers move through your flow. This update helps you quickly identify issues across diverse customer profiles before activation.
  • Trigger Automation Event-Triggered Flows When CRM Records Change
    Now you can trigger an automation event-triggered flow when a prospect, lead, or contact record changes, or when a record related to a prospect, lead, or contact record changes. For example, send a personalized email to a contact when a case is closed, or trigger a follow-up flow that notifies a lead owner when an opportunity moves to a new stage. This update helps you engage customers immediately when key business events occur, with prospect, lead, or contact data available for personalization in your messages.
  • Stay Informed About Path Experiment Outcomes
    Users who activate flows now receive automatic in-app notifications when path experiments are completed. Notifications cover winner selection, fallback handling, and inconclusive outcomes. This change keeps flow creators informed without requiring additional setup. If the activating user is deactivated, no notification is sent.
  • View Path Comparison Analytics in Path Experiment Element
    Monitor path experiment results without leaving the Flow Builder canvas. The new Analytics tab in the Path Experiment element panel shows total participants, metrics, and confidence levels for path comparison. Monitor experiment results at a glance with this embedded summary, which is consistent with analytics available in other flow elements. To see in-depth analytics, click View Analytics.
  • Control Path Selection When Debugging Path Experiments
    Configure the Path Experiment element to randomize path assignment or manually select a winning path while debugging. Randomization is the default, but you can validate specific paths without relying on chance by using manual selection. With the manual selection configuration, you can test the exact path you want to validate.
  • View Path Experiment History
    Understand what happened during your path experiments with the new History tab. View all changes since activation, including timestamps, who made changes, and whether actions were automated or manual. Track events like experiment start, winner selection, delayed group releases, and fallback handling.
  • Trace Individual Paths Through Flows with View Flow Run for Individual
    Troubleshoot specific customer issues by viewing the exact execution path that an individual took through a flow run. This capability shows you which branching paths were followed, what elements were completed, and where the individual potentially encountered errors or delays. This detailed view helps administrators investigate specific customer complaints, verify personalization logic, and identify bottlenecks for specific contacts in your marketing automation flows.
  • Personalize and Debug On-Demand Flows with Apex
    Personalize on-demand flows with Apex code and control processing priority when triggering flows via API. Select specific individuals and contact points to target messages. Debug flows with built-in debugging tools to test logic and identify issues before activation. Access help documentation from the start node to understand configuration options and best practices. These updates provide more flexibility for customizing flow behavior and faster troubleshooting during development.
  • Remove Individuals from Flows Externally via API
    Remove individuals from flows when external systems trigger exits via API. For example, exit customers from flows when they complete an order or when they reach a specified status. This update provides more flexibility to coordinate flow exits with external systems.