--- schema_version: "1" id: 2bbb02d68d63c7d9c4ff863b184cc7065784cb562ccf72e4be6d6bcd8ffb0ff9 title: Flow Marketing Cloud Updates collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/262-0-0/rn_automate_flow_marketing_cloud.md canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud.htm&release=262.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 6c8e5c6993803d7c5548479f9ff2f204324fd76bbc1c4643d169fd8145190777 description: Personalize email messages using content variables from Email Content Builder. View a flow's history and restore from earlier saves. Use flow features and elements across all marketing flow types. Send individuals to a new flow while maintaining their progress in the original flow. Automaitcally remove contacts with the Exit from a Flow element. products: - Cross Cloud release: "262" --- # Flow Marketing Cloud Updates Personalize email messages using content variables from Email Content Builder. View a flow's history and restore from earlier saves. Use flow features and elements across all marketing flow types. Send individuals to a new flow while maintaining their progress in the original flow. Automaitcally remove contacts with the Exit from a Flow element. - **[Personalize Messaging with Integrated Data by Using Clicks, Not Code](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_personalize_messaging.htm&release=262.0.0&type=5)** Expand your email messaging personalization options by mapping content variables from Email Content Builder to merge fields in Flow Builder without writing Apex code. When you create email content with custom-defined resources like manual variables or record data providers, Flow Builder renders dynamic inputs for those fields in the message action. This low-code approach gives your marketing team greater control over how you use data to personalize communication with your customers. - **[View and Restore Flow Version Edit History](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_flow_version_edit_history.htm&release=262.0.0&type=5)** View a history of saved changes to a flow version and restore earlier saves. Each time you save a flow version, the system adds a new save instance to your history. See past saves with the date, user, and a summary of elements added, edited, or deleted. - **[Use Flow Elements and Features Across All Marketing Flow Types](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_flow_type_consistency.htm&release=262.0.0&type=5)** Flow features and element availability are now consistent across all marketing flow types. This means that features and elements like Wait and Decision are available across all of the different marketing flow types. Consistency across marketing flow types makes it easier to seamlessly switch between the different marketing flows without worrying about element compatibility or feature availability. - **[Coordinate Complex Journeys Across Flows](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_send_to_a_flow.htm&release=262.0.0&type=5)** Direct individuals to a new flow while maintaining their progress in the original flow. Use the new Send to a Flow element to build more sophisticated, interrelated customer engagement strategies. The element passes the customer’s identifiers to the destination flow. The original flow and destination flow run asynchronously, so the original flow continues to run while the destination flow works simultaneously. Previously, orchestrating users through multiple flows required complex custom logic or API integrations. - **[Remove Contacts Automatically from an Active Engagement Flow](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_exit_from_a_flow.htm&release=262.0.0&type=5)** Add the new Exit from a Flow element to stop sending contacts irrelevant communications when they meet a specific goal or condition. Previously, removing contacts required manual intervention or complex custom logic. Now, you can choose to remove contacts from all versions of the selected flow or only the most recent version. - **[Personalize Flows with Deeper Access to Source Data](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_source_data_access.htm&release=262.0.0&type=5)** Sort and filter data from a source to create a selected record resource. The selected record resource provides access to nested data from data graphs and other data sources, expanding your ability to personalize flows. - **[Reach Audiences from One Streamlined Flow Category](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_audience_flow_type.htm&release=262.0.0&type=5)** Create flows based on audience data from a single, streamlined flow category: audience flow. Select a data source—List, Segment, Record, or Campaign—based on your use case. The segment audience replaces the segment-triggered flow, bringing consistency across audience-based flows. The list, record, and campaign options are based on new flow types. - **[Build More Precise Logic in Decision Elements and Exit Rules](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_decision_element_logic.htm&release=262.0.0&type=5)** Apply more powerful Decision element logic with nested condition groups. Combine conditions, add aggregation functions—Average, Sum, Max, Min—for numerical data types, and use expanded date operators such as Is Anniversary of Today, Is Today, and Last Number of Days. In exit rules, add aggregation functions for numerical data types. - **[Add Exit Rules That Use Events](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_exit_rules_events.htm&release=262.0.0&type=5)** For flows that support exit rules, like segment-triggered, event-triggered, and on-demand flows, you can now use events to exit an individual from a flow. For example, if a customer is in an event-triggered flow for cart abandonment, use a purchase event as an exit rule so that the customer doesn’t get irrelevant messages. - **[Set Conditions and Reentry Criteria for Event-Triggered Flows](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_additional_conditions_re_entry.htm&release=262.0.0&type=5)** For event-triggered flows, you can now specify additional trigger conditions with fields from the specified primary data model object. You can also now set reentry criteria, so you can specify whether an individual can rejoin the flow. - **[Add More Contact Points and Related DMOs to Event-Triggered Flows with Enhanced Engagement Signals](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_enhanced_engagement_signals.htm&release=262.0.0&type=5)** Now you can specify SMS and WhatsApp contact points in your flows. When creating engagement signals, you can also specify a profile data model object (DMO) instead of only engagement DMOs. Profile DMOs give you direct access to an individual’s data in a flow. Optionally add a related object and reference its fields to define the engagement signal or use filters. For example, create a flow that triggers after a customer makes an order, and then include related order item information with a filter that fires only if the spend exceeds a certain amount - **[Filter Element Analytics by Date Range](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_element_analytics_date_range.htm&release=262.0.0&type=5)** Filter analytics on flow elements by a date range. Metrics on elements reflect the selected period, so you can analyze recent performance, compare periods, and align analytics with your campaign windows. - **[View Path Outcome Metrics for Path Experiment](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_path_experiment_outcome_metrics.htm&release=262.0.0&type=5)** See path outcome metrics for path experiment elements in the analytics dashboard. View how each path in an experiment performs. Compare paths and choose a winner with better context. - **[Keep Send Log Data in Marketing Flows](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_send_log_data.htm&release=262.0.0&type=5)** Marketing send elements now support send logging. Use the new retain send log data option to keep send log data and have it passed to Marketing Cloud Engagement for reporting and troubleshooting. - **[Users Can Now View Flow Dependencies](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_marketing_cloud_citizen_users_view_flow_usage.htm&release=262.0.0&type=5)** Non-admin users can now view flow dependencies for their marketing flows in the Automation app. Previously, only users with the Manage Flow permission had access to this information. #### See Also - [Use Batch DMO Activations, More Flow Elements, and Debug with Enhanced Activation-Triggered Flows](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_activation_triggered_flow_updates.htm&release=262.0.0&type=5 "Use batch data model object (DMO) activations to trigger a flow, so that you can utilize full DMO datasets in your automations. Take advantage of activation data in SMS messages with the Send SMS action, now enabled in activation-triggered flows. You can now also use the Wait Until Event element. Debugging is now available to troubleshoot and test your flow.") - [Use Wait Elements and Test Flows with Broadcast Flow Enhancements](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_broadcast_flow_updates.htm&release=262.0.0&type=5 "Asynchronous broadcast flows now support wait elements. You can also now test broadcast flows in debug.") - [Use Unlimited MuleSoft Connectors in Segment-Triggered, Activation-Triggered, and Broadcast Flows](https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_unlimited_connectors.htm&release=262.0.0&type=5 "For segmentation and activation use cases, MuleSoft for Flow: Integration connectors no longer consume automation credits for segment-triggered, activation-triggered, and broadcast flows. You can use MuleSoft connectors in these flow types without a MuleSoft for Flow: Integration add-on license. Other flow types still require the MuleSoft for Flow: Integration add-on license.")