So I was building a journey with the entry source as a DE where the data in that DE would be populated by a cloudpage. There would be emails sent for confirmation on submit.
I was told that this would not work because it would only be a "snapshot" in time.
The way to go about this is to use attribute groups in journey builder where the data would be "constantly" reviewed if that is the correct term to use - so that people would be eligible for the confirmation email closer to the event date.
Can anyone point to why this is the case? Are contact builder-attribute groups the best entry sources to use when launching journeys that have "retroactive" rules like looking if someone has registered or not - then sending an email ex. you launch a journey then 5 days later they register.