salesforce.stackexchange.com/questions/333219/journey-handling-deleted-or-non-existent-subscribers

Prerna i would recommend posting the question on stackexchange or on trailblazer community questions with more details on the scenario you are trying out. Thanks

Journey builder is meant to be a 1X1 engagement tool - that is every contact that enters a journey goes through a path depending on how they engage within the journey. You are not using the email within a journey to send to multiple folks in a DE - rather you are configuring the email to be sent to every contact that enters the journey and reaches the email activity. Where you control the DE / Recipients is in the Entry source - all contacts who qualify for journey entry will flow through and be sent Emails if any are configured in their path. If you need to send a mass email to recipients in a DE, you can use User Initiated Send manually in Email Studio, or Email Send in Automation Studio or even a single Step journey by selecting the DE as entry source.

That is not how you distinguish between Journey and Contact data - in fact both point to the same set of fields associated with the Entry DE - just that Journey data is static and does not change during the lifecycle of a contact in the journey. However when u refer to contact data of the contact in the journey, it will show the live data from the DE. Even though rare, if you change the Lastname of the contact in the DE after he / she has entered the journey, then the contact data will show the updated value but journey data the initial value. Contact data can also get data from linked DEs to the main Entry source DE so that you can use it in Decision splits. For e.g. if you want to check if a Purchased flag has been set to true in the DE based on some transaction the contact has done in an ecommerce portal which updates the DE, then you would use the contact data as it will show you the latest flag value. Whereas the flag value in Journey data will always show the initial one and not reflect any updates.

Try checking the Journey History tab - help.salesforce.com/s/articleView?id=sf.mc_jb_view_contact_history_in_dashboard.htm&type=5

Havent tested it but if the custom object is created on the underlying SF core platform, I dont see why it shouldnt be available in MC thru the connector - unless there is a restriction as part of the healthcloud managed pkg permissions.

That happens outside the scope of MC - you can have process set up in eCommerce system to send data over through FTP or API daily / weekly as needed depending on volume.

@@sfmctrailblazers thank you so much. Another question from my end is: What are the possibilities of sending of a product review email to customers each time they made a purchase in e commerce ?

@@pritamrkms if u need near real time, u can use API to send a triggered send email. If its a transactional email then u can even use Transactional Send journey - for both u can invoke thru API and pass the relevant info

tidbitsforu.com/contact-me/