The connector is not able to identify two events separately if they are triggered at the same.
- Iterable Connector
- Any destination
Iterable is working on this as a feature request on their end and as soon as they have solution, we will be able to support this use-case as well.
We use the event_name, campaign_id, created_at, and email columns of the events to generate the hash identifier. However, these four fields cannot uniquely identify a record because Iterable doesn't support timestamps with milliseconds precision.