The entry event comparisons are being made on the server side, which is running on US Central Standard Time (without daylight savings) which would be about 19 hours behind your timezone.
This is a known limitation. The date/time displays will follow your account timezone settings but any date-based entry event will be based on the server time.
Currently, there is no option to configure the timezone to be used for a date-based entry event and the recommended solution would be to adjust the filter settings to match US Central Standard Time.
ie instead of DateCreated after today minus 2
use DateCreated equal Today
Support has suggested an inefficient solution. My solution will be to either:
- SQL queries converting the data file date/time to CST, then use that field for the Entry Criteria
- Use a Data Filter Activity to output the subscribers eligible for mailing into another Data Extension, then use that Data Extension as the source Data Extension for the Journey
Update on 27/10/2016
My final solution was to create a Query which outputs a CST version of the Date field using below:
DATEADD(HH,-19,CONVERT(datetime, LEFT(CONVERT(nvarchar(20),DateCreated, 20),10) + ' 12:00:00', 120)) as DateCreatedCST
- It's important to hardcode the time (12:00:00) to account for fluctuations of DST between NZ Timezone and server Timezone.
- To adjust for another timezone, simply change the -19 value to whatever the offset between CST and your timezone is.
In Journey Builder, I used this filter criteria
DateCreatedCST Equal today minus 1 day
In order to target 5 days ago I would use
DateCreatedCST Equal today minus 5 days
There is no need to set a more complex filter.