You are here:
The Salesforce Data Event
A Salesforce Data Event is an action in Sales Cloud or Service Cloud, such as creating or updating an object record, that injects a contact into a journey. If the primary object meets rule criteria and reference object filtering criteria, Flow Builder initiates a Journey Builder event.
Consider these items when you configure the event:
- Use the Sales Cloud or Service Cloud object as the source of the entry event
- Who enters the journey, such as users, leads, or contacts
- When the user, lead, or contact enters the journey, such as when a record is created or updated
- Select attributes from object data to filter who enters the journey
- Select fields from related objects and the entry object to use for journey
dataNote Limit selection to 250 fields or less. Limit journeys per object to 80 or less.
Each record includes the ID for the user, lead, or contact entering the journey, their email address, and the email opt-out flag status.
After the entry source is configured, you can’t edit the object it uses or who enters the journey. To select a different object, delete and recreate the entry source. You can edit the entry criteria, filters, and event data for a configured entry source before it’s published. You can copy journeys that contain Salesforce entry sources and entry sources are reusable.
After you save the entry source, Engagement creates a data extension that uses event data as columns and the contact ID as the Subscriber ID. Records that meet the entry source criteria are imported into this data extension when the journey is published. A row is created in the data extension every time a record meets the criteria, but existing rows aren’t updated. You can have the same record in the data extension multiple times when it enters the journey more than one time. For more details, see Journey Settings.
The integration between Engagement and Sales Cloud uses Flows, Process Builder, Apex, Platform Events, and SOAP APIs. Therefore, Salesforce Data Events are subject to all APEX Governor Limits. Adding Journey Builder events or your own processes or flows into the save order of an object can expose or exceed limits within your org. When an integrated journey is activated, the Sales Cloud Flow Metadata API launches the flow for the object with the conditions specified in the entry configuration. These tools allow your business to run behind the scenes. Here’s an example that illustrates how the objects are used and how they work from end to end.
Required Permissions
To configure or activate a journey that includes a Salesforce Data Event, your user account must have a role assigned with these permissions allowed:
- Email | Integrations | Salesforce CRM
- Journey Builder | Sales and Service Cloud
APEX Governor Limits
Salesforce Data Events are subject to all APEX limits, or governors, and process limits within the platform. Introducing Journey Builder Events or Process Builder and Flows into the save order of an object can expose or exceed limits within your org.
- 50 Future invocations: Before the 5.496 Marketing Cloud Connect package, Journey Builder
made direct callouts using the
futureannotation. This action causes an error on any transaction exceeding 50 records, meeting the Journey Builder Event criteria. To avoid this error, use Marketing Cloud Connect package 5.496 or above. - Transactions with more than 2,000 records: A save transaction is limited to less than 2,000 flow invocations. This limit allows up to 2,000 records to enter a flow within a transaction. If multiple flows are triggered or your org has custom logic generating transactions with more than 2,000 records, the flow invocation fails. To interact with a smaller number of objects, modify transactions.
- Maximum CPU Time: The event adds steps to the target objects save order transaction, which uses a small portion of the allocated CPU for a transaction. To avoid exceeding this limit, monitor the addition of processes.
- 50 System.enqueueJob limit: Each Journey Builder callout is queued as an invocable method. Each transaction can enqueue up to 50 invocable methods and can process up to 200 records. If objects meet the criteria for multiple events, this limit can be reached with 50 unique events on a single object. This limit is shared with non-Journey Builder triggers and flows.
Associated Sales or Service Org Changes
If the Sales or Service Cloud org connected to the Engagement account changes, delete all associated journeys and events. Journeys can reference objects or fields that don’t exist in the new org and cause publishing to fail. Create journeys and events to reference the new org.
- Configure the Salesforce Data Event
Using this Journey Builder event, contacts enter the journey when a Sales Cloud record is created or updated. - Create a Salesforce Campaign Event
The Salesforce Campaign event in Journey Builder adds contacts to a Marketing Cloud Engagement journey when they’re added to a Sales Cloud campaign. You can also use this event to send Salesforce object data into the data extension created upon entry. - Salesforce Experience Cloud
The Salesforce Experience Cloud entry source in Journey Builder starts activities in a journey when new members are added to your Experience Cloud site. Use the Salesforce Data Event for activities that aren’t related to adding new members. - Person Accounts and Salesforce Data Events
A person account is a type of account that stores information about individual consumers. By default, Salesforce accounts are business accounts, but administrators can choose to set up person accounts. Person accounts facilitate business-to-consumer functionality within Sales and Service Clouds. Use the Salesforce Data Event to tell Journey Builder to perform one of these actions:
