Setting event timestamp during import



We have a stack using hightouch, rudderstack, and amplitude to import order data to amplitude.


When an event is created in amplitude, it seems to use the timestamp when it is imported, not a designated timestamp.  Am I missing something or can this value not be set?

5 replies

Userlevel 4
Badge +5

@Ben Wright welcome! I’ve asked our technical team to dig into this for you.

Userlevel 7
Badge +10

Hey @Ben Wright 

I looked up some docs and here’s what I found.

Are you selecting the event timestamp column before syncing or is it empty?


@Saish Redkar we set a timestamp to the created_at field in rudderstack at the time of sync. We also tried a few other variable names like time and event_time with no change.

Userlevel 5
Badge +5

Hi @Ben Wright

I believe that rudderstack send in data through our HTTP v2 API. With this API, Amplitude uses the key “time” in the JSON event object to determine event time. 

time Optional. The timestamp of the event in milliseconds since epoch. If time isn't sent with the event, then it's set to the request upload time.


I checked the raw data for one of your projects, and saw the “time” field was passed with valid values. An example value is: 1685034104000. 

Could you please check with rudderstack what values they are passing to Amplitude for the “time” key? Thanks. 


@Yuanyuan Zhang I’ve passed the time property in the order completed event here.  But you can see that the timeline and event time use the sync timestamp (created_at).