Skip to content

Commit be0ff95

Browse files
Add note about change in sentat in new mobile libraries
1 parent 2c045a1 commit be0ff95

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

src/connections/spec/common.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -276,6 +276,9 @@ The `sentAt` timestamp specifies the clock time for the client's device when the
276276

277277
**Note:** The `sentAt` timestamp is not useful for any analysis since it's tainted by user's clock skew.
278278

279+
> warning ""
280+
> When `sentAt` is added to a payload has been changed in the Swift, Kotlin, and C# mobile libraries. The `sentAt` value is now added when the batch is complete and initially tried to the Segment API. This changes the value of the Segment calculated `timestamp` to align closer with the `receivedAt` value rather than the `originalTimestamp` value. For most users who are online when events are sent, this will not impact the data in any significant way. However, if your application utilizes an offline mode where events are queued up for any period of time, the `timestamp` value will more closely reflect when the events were received by Segment, rather than the time they occurred on the users device.
281+
279282

280283
### receivedAt
281284

0 commit comments

Comments
 (0)