1

When selecting Event > Date Based as entry source, we can only see Einstein-related Attribute Groups, and can't see the Salesforce instance.

We need to trigger a journey one year before a Loan (date on SF Contact) is due.

Ideas as to why it doesn't show and/or how to achieve the goal?

Thanks

PS

MC Connect is well configured and appears in other sections in Journey Builder.

See screenshot below: Journey Builder - Event - Can't see SF as a source

1

This is a good question. Since you need to filter based in a "static" attribute, you cannot use Salesforce Data as Entry Source (because you are not creating ou updating something). Instead, what you can do is:

  1. Create a Standard Data Extension with the same fields that your Data Extension Synchronized has; (e.g. Standard_Contact_Salesforce)
  2. Create a SQL Query to populate this Data Extension based on the Sync. DE;
  3. Schedule an automation with this SQL Query Activity to run daily (or weekly);
  4. If your journey depends of fields that are not present in the respective D.E do the same for those others D.E and create the relationship in Contact Builder;
  5. You will select the respective Data Extension that you create in Step 1 as Entry Source

enter image description here

  1. Create a filter criteria (as in the image below)

(e.g. Loan (Due Date) is equal Today minus 1 year)

enter image description here

Maybe this is not the smartest way, but eventually will solve your problem.

The other solution that cames in my mind is: create a field in Salesforce and a process builder to update this field when meet criteria, then you can use Salesforce Data as entry Source.

If you find a more beautiful solution please let me know.

4
  • Thanks for you reply. I lost you at #4. Do I have to create the relation in Contact Builder for the new DE, created via SQL, to be present in the list as date-based events? Also, why would I need a filter criteria (#5) if I use the Date-based event? It's this type of event that filters the date for me, or what am I missing?
    – LimeWeb
    Aug 6 '20 at 15:35
  • 1
    I edited my awnser, hopefully it helps you! :) Aug 6 '20 at 17:32
  • thanks, so this is what I found as to "why" I can't see SF - trailblazer.salesforce.com/… What you are suggesting is a workaround to not use Event Date-Based as an Entry Source. But I believe that if I follow steps 1,2,3 + connect the DE to the Contact model under a new Attribute Group - I will simply be able to select the new DE in the list as it'll be sendable. Need to test, but my MC is currently stuck. Will report back.
    – LimeWeb
    Aug 6 '20 at 21:30
  • yup, validated. Problem solved! I added the full answer below for future reference.
    – LimeWeb
    Aug 6 '20 at 22:22
1

The reason we can't directly select Salesforce Contacts - from the Contact Model - is that these are not Sendable.

To bypass this we need to:

  • create a Copy in a Sendable DE + Automation to update the new DE reglarly.

Notice that the only way to do this is with a SQL Query activity in Automation builder.

Best Practice: Avoid Select * for that SQL Query

If you try to use Filter Activity on Synced DEs, it will create another Synced DE, which is again not sendable so it doesn't solve the problem.

  • Once we create the new DE, we have to connect it to the Contact model in Contact Builder, and voilà.

The new DE is now an option under a Date-Based Event.

Hopefully this helps someone in the future. (Upvote it to let me know!)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.