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

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.

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. 

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). 

Hi @Ben Wright, 

Passing “time” as an event property will not work. “Time” is a key that should not be included under user property or event property, the general structure should look like this:

"api_key": "xxxxxxxxxx”,
      "raw_data": �
        {
          "app_version": "",
          "device_model": "",
          "os_version": "",
          "device_type": "",
          "language": "",
          "device_carrier": "",
          "device_manufacturer": "",
          "event_type": "xxx",
          "insert_id": "xxx",
          "user_id": "486448",
          "device_brand": "",
          "os_name": "",
          "time": 1684524688000,
          "event_properties": {XXXXXX}