Understanding the Challenge

The issue with using synced data extensions in decision splits is that it can lead to lag times of up to 75 minutes in the worst-case scenario. This can be problematic when dealing with large volumes of data or when updates happen frequently.

The root cause of this issue is the way synced data extensions are handled in Journey Builder. When using synced data extensions in decision splits, the system may not always have the most up-to-date data, leading to potential errors or inconsistencies.

Possible Solutions

One possible solution is to use time-based messages in the journey to check for updates to the record. This approach can help fill in the gaps when no updates are happening to the data. However, it requires careful configuration to ensure that messages are only sent to customers who haven’t had any updates.

Another approach is to use Salesforce Data Entry to leverage the most up-to-date data. This can be particularly useful when dealing with large volumes of data or when updates happen frequently.

Configuring Decision Splits

When configuring decision splits, it’s essential to ensure that the criteria are correctly set up to avoid errors. This includes matching on Journey.contactId = contact.contactId AND your logic, as well as ensuring that there are no multiple rows per contact in the synced source.

Decision Split Configuration

IF (Journey.contactId = contact.contactId AND ) THEN
  // send message or perform action
ELSE
  // alternative action

Best Practices

Checklist for Using Synced Data Extensions in Decision Splits

• Use time-based messages to check for updates to the record
• Leverage Salesforce Data Entry for the most up-to-date data
• Ensure correct configuration of decision splits to avoid errors
• Match on Journey.contactId = contact.contactId AND your logic
• Avoid multiple rows per contact in the synced source
• Test and validate your configuration to ensure accuracy
• Monitor sync lag times to optimize performance

What is the recommended approach for using synced data extensions in decision splits?

The recommended approach is to filter synced data extensions, but this can increase sync lag time.

How can I leverage Salesforce Data Entry to use the most up-to-date data?

You can use Salesforce Data Entry to leverage the most up-to-date data, particularly when dealing with large volumes of data or frequent updates.

What are the potential errors when using synced data extensions in decision splits?

Potential errors include inconsistencies due to lag times, incorrect configuration, or multiple rows per contact in the synced source.

How can I ensure accurate configuration of decision splits?

Ensure correct matching on Journey.contactId = contact.contactId AND your logic, and avoid multiple rows per contact in the synced source.

What are the best practices for using synced data extensions in decision splits?

Best practices include using time-based messages, leveraging Salesforce Data Entry, ensuring correct configuration, and monitoring sync lag times.