I think it also depends on some scenarios, for instance,
- A delivery can be scheduled to start sending (contacting customers) at a specified date/time in the delivery template, this is your "Contact Date", however, by default this is not set, therefore, the "Contact Date" becomes the time the delivery started being processed.
- In the case of setting the scheduler to start sending messages at a specified time, you can still execute the campaign workflow which will prepare the messages etc, however, the delivery will be waiting until the "Contact Date" is met to then start the delivery.
Image may be NSFW.
Clik here to view.
3. EventDate is tied to broadlog entries, and by default is in the order that that particular entry/record was processed, also in the case of retris (soft bounces), the eventDate will be updated to the last retry datetime.
4. A broadlog entry for a campaign which was executed today (i.e 19th 12 2019) and then failed to get delivered by a temporary failure error type (soft bounce) it will trigger retries, by default x5 a day after the first error and then each one every day, until the validity period of the delivery is met. In this case, if the entry runs into the next day and is still retrying, the eventDate will no longer be the 19th, but rather the 20th.
Clik here to view.
