@Zoe_G Message feedback dataset is based on the execution field (default personalEmail.address) that is set on the journey to send the messages. Any status on the message feedback will get recorded back to the identityNamespace (email) along with the value (email address). If the EpsilonContactId is...

@Ikmo7 Use the nowWithDelta function in the wait activity. Take a look at some of the previous threads. https://experienceleaguecommunities.adobe.com/t5/journey-optimizer-questions/dynamic-date-condition-in-ajo/m-p/623727#M829 https://experienceleaguecommunities.adobe.com/t5/journey-optimizer-questi...

@Zoe_G Unless otherwise EpsilonContactId is the primary identity it won't be part of the identityMap and OOTB message feedback event dataset.

@workflowuser Did you follow this documentation on how to use contextual data in offer decisioning? https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/experience-decisioning/selection/context-data

@user77095 Since you have a query written take that and write to a dataset. Follow the below documentation to export the datasets and guardrails around this. There are different methods available to export the dataset choose the one that works for you. https://experienceleague.adobe.com/en/docs/anal...

@AK5 It's not clear that the current timezone setting you have account for the daylight saving switch. Probably reachout to adobe support and confirm that it will work for Australia DST changes.

@AK5 Journey setup looks good considering the requirements to send messages from 7:30 to 7:45. Hence setting the timezone done at the journey property level will use that timezone in the condition activity. If this is an evergreen journey consider how you want to handle this when daylight saving end...

Take a look at the video from this link, https://experienceleague.adobe.com/en/docs/journey-optimizer/using/channels/sms/get-started-sms

@Jorge_RogelioZe It's complaining about the contextual data being used in the URL advanced function. The function was looking for a domain name and couldn't recognize that from the contextual data.    

No. Use the audience builder "build rule" option if that works for your needs.