Incorrect timestamp formats #75
Description
Looking at the raw events delivered to Segment, I've noticed a discrepancy in the timestamps:
...
-d originalTimestamp=2021-10-16T16:00:27.029:Z \
-d receivedAt=2021-10-16T16:00:28.078Z \
-d sentAt=2021-10-16T16:00:27.957:Z \
...
You can see that the originalTimestamp and sentAt dates use a different format than the receivedAt date – there's an additional colon prior to the timezone signifier.
When using it with the Amplitude Actions plugin and trying to map the originalTimestamp to Amplitude's timestamp property this causes the event to be rejected.
By default, the Amplitude Actions destination maps the receivedAt property to its timestamp property which of course means events are appearing out of order. It would be much better if we could use the originalTimestamp property as currently the events are arriving as shuffled.