Experience Cloud and Integrating with Journey Builder

Journey Builder in Marketing Cloud Engagement helps you create personalized journeys for your site based on triggering events or geared for specific audiences. Greet new users with rich content emails, send reminders to users who need profile pics, or schedule follow-up emails for users who log a case. To use this feature, you must have both Experience Cloud and Marketing Cloud Engagement licenses.

Note Beginning in Summer ’26, Chatter is turned off by default in all new orgs. For any features in these orgs that require access to Chatter functionality or the Chatter APIs, turn on Chatter by going to Setup | Chatter Settings and selecting Enable. For details, see Chatter Is Turned Off by Default in New Orgs Beginning in Summer ’26.

This feature passes member information, including email addresses, from the Experience Cloud to Engagement.

Trigger a personalized journey with events, or choose a specific audience.

Examples of audiences include:

• All users of the site
• Users who own a certain product (depending on configuration)
• Users with the highest number of reputation points
• Users who belong to the same Chatter group
• Users who haven’t contributed in the last number of days

The two clouds integrate through Marketing Cloud Connect (available on AppExchange). When it’s set up, you’re ready to go. The process and email creation is all handled in Journey Builder. The See Also links guide you to those steps.

Note Adding users to a community is slower when triggering journeys. If you’re adding lots of new users, like more than 1,000, at once, we suggest letting Journey Builder run overnight.

• Experience Cloud Journey Data Model
  When you create an Experience Cloud journey, you choose whether to add user or contact data. To avoid unintentionally sending emails to people who have opted out, you must stay consistent. There are also some event trigger and tracking limitations.
• Email Preferences
  The Unsubscribe link at the bottom of a Marketing Cloud Engagement email opts the person out of all further emails from that instance of Engagement. If you want users to be able to unsubscribe from site emails without unsubscribing from other brand or company emails, some setup is required.
• Triggering Journeys Based on Events
  You can trigger journeys based on an event that happens in the site, like when members join.
• Triggering Journeys Based on Audiences
  You can select a set of users—an audience—and put them into a journey. Your audience can be specific and include, say, a user who purchased a certain product and posted within the last 30 days.
• Determine If an Object Can Trigger Journeys
  Before you create an event-based journey, check that the object you want to use works. This test helps you identify available objects.
• Sync an Object to the Marketing Cloud Engagement
  To create an audience-based journey, sync object data to Marketing Cloud Engagement.
• Experience Cloud Objects for Creating Member Journeys
  Most, but not all, Experience Cloud objects can be used for creating journeys. This list includes the available objects along with a description, their eligibility status, API object, and use cases (as appropriate).