Using Salesforce Data as an entry source we could select required fields to be used as attributes within the journey. These attributes would become journey data and you could use them within decision splits but we want to use more or less realtime data from Salesforce in decision splits. We could tolerate 1-2 minute delay and therefore could not use synchronized data as delay would be around 15 mins which is too much in our case. Do you see any solutions for this case?

  • A custom activity could be one of the solutions. – manjit5190 Jun 15 at 15:21
  • Can you be more specific? What happens in the journey before this decision split and what data would you need for that decision? – zuzannamj Jun 15 at 16:19
  • @z uzannamj We are on the stage of journey analysis therefore it's not that specific. Generally, during the previous steps within journey we plan to update an Object in SF, then put wait activity (as short as possible). After update, Service Cloud should do an API call to update an external system and decision split should be based on the data returned by the external system to Service Cloud (it could successful or failed update). – Artur Krotkov Jun 16 at 6:46
  • @manjit5190 Yes you're right, we've considered that but still try to investigate whether easier approach is available. – Artur Krotkov Jun 16 at 6:47
  • 1
    What about creating a boolean custom field on your object that let's MC know that the API call has been returned and a status has been assigned. Then you could use that field being set to true as an additional qualifier on your journey entry criteria. It's not ideal, but I'd have to think it will be a lower lift than building/testing a custom activity to accomplish something like this. – Jason Hanshaw Jun 16 at 21:33

Your Answer

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

Browse other questions tagged or ask your own question.