Understanding the Difference

At the platform level, Triggered Sends and Salesforce Data Entry options serve distinct purposes. Triggered Sends are designed to handle more complex logic and offer greater control over the email send process, whereas Salesforce Data Entry options are better suited for straightforward record creation-based triggers.

The root cause of the confusion lies in the fact that both Triggered Sends and Salesforce Data Entry options can be used to initiate email sends based on record creation in Sales Cloud objects. However, as we delve deeper, it becomes clear that Triggered Sends offer more flexibility and control, particularly when dealing with duplicate records or sales agent-triggered re-sends.

For instance, if the Salesforce Entry Event is set to Create, you would not have the duplicate problem, but you would also not be able to trigger the Journey with an update, thereby limiting the sales agent’s ability to trigger a re-send.

Step-by-Step Solution

To determine whether to use a Triggered Send or Salesforce Data Entry option, follow these steps:

journey_builder.js

// Evaluate the complexity of your email send logic
if (logicIsComplex || duplicatesArePossible) {
  // Use a Triggered Send for more granular control
  useTriggeredSend = true;
} else {
  // Use Salesforce Data Entry option for straightforward record creation-based triggers
  useSalesforceDataEntry = true;
}

By following these steps and considering the specific requirements of your use case, you can make an informed decision about whether to use a Triggered Send or Salesforce Data Entry option in Journey Builder.

Heads up: when using Triggered Sends, ensure that you have the necessary permissions and access to the Sales Cloud object to initiate the email send.

Checklist

• Evaluate the complexity of your email send logic
• Consider the possibility of duplicate records
• Determine if sales agent-triggered re-sends are required
• Assess the need for granular control over the email send process
• Choose the appropriate option based on your specific use case
• Ensure necessary permissions and access to the Sales Cloud object
• Test and validate your chosen approach

Frequently Asked Questions

What is the main difference between Triggered Sends and Salesforce Data Entry options?

Triggered Sends offer more granular control over the email send process, whereas Salesforce Data Entry options are better suited for straightforward record creation-based triggers.

Can I use a Triggered Send to handle duplicate records?

Yes, Triggered Sends can be used to handle duplicate records and offer more control over the email send process.

How do I determine which option to use?

Evaluate the complexity of your email send logic, consider the possibility of duplicate records, and determine if sales agent-triggered re-sends are required to make an informed decision.

What are the implications of using a Triggered Send?

Using a Triggered Send requires careful consideration of the email send logic and may require additional setup and testing to ensure correct functionality.

Can I use a Salesforce Data Entry option to trigger a re-send?

No, Salesforce Data Entry options are limited to record creation-based triggers and do not support sales agent-triggered re-sends.