You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/spec/common.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -392,4 +392,4 @@ The `receivedAt` timestamp is most important as the sort key in our Warehouses p
392
392
393
393
The `timestamp` timestamp specifies when the datapoint occurred, corrected for client-device clock skew. This is the timestamp that is passed to downstream destinations and used for historical replays. It is important to use this timestamp for importing historical data to the API.
394
394
395
-
The `timestamp` field is settable from our server-side libs or if passing info directly to the HTTP endpoints. From the client-side, a `timestamp`will be generated but cannot be manually set in order to import historical data to the Seegment API.
395
+
The `timestamp` field is settable from our server-side libs or if passing info directly to the HTTP endpoints. From the client-side, the Segment library generates `timestamp`so you cannot manually one set to import historical data to the Segment API.
0 commit comments