yes, unless you use journey starts with event uses experience event type schema or profile schema that has all the metadata. Take a look at this post
https://experienceleague.adobe.com/en/docs/journey-optimizer/using/configuration/configure-journeys/events-journeys/unitary-events/experience-event-sc...
The method of data ingestion plays a crucial role in this scenario. When all subscriptions are inputted into a single Individual Profile dataset, it is necessary to map all subscriptions each time to avoid overwriting the map value. However, if the subscriptions are stored in two distinct datasets, ...
@akwankl Below is the difference between push open and click,
Push Click - When a push notification has been delivered to the device and the user has clicked on the device. The user either wanted to view the notification (which will in turn move to Push Open tracking) or dismiss the notification.
...
@akwankl This should allow us to wait until 15th everyday when it runs. I haven't tested this. Another approach would be to directly use this function in the wait activity to allow profiles to wait until the 15th of April.
toDateTimeOnly('2024-04-15T00:00:00')
Remember to consider global journey tim...
@akwankl, If I understand correctly profiles qualify today Apr 9th, 10th, 11th, 12th, 13th, 14th will get the next touchpoint on Apr 15th.
In this case, you can use setdays function in the wait activity.
setDays(toDateTimeOnly(now()),15)
@lulugw, You can ingest the subscription data from CRM either using HTTP API or batch ingestion method that will map to the field group Generic Marketing Preference Field with Subscriptions
@akwankl Take a look at this post
You can have a wait activity with custom formula and send it on the 2nd day and 15th day.
toDateTimeOnly(setHours(nowWithDelta(2, "days"), 6))
toDateTimeOnly(setHours(nowWithDelta(15, "days"), 6))