Skip to content

Commit 50df150

Browse files
authored
Merge pull request #6408 from segmentio/joeynmq-patch-4
Clarify Segment timestamps are in UTC
2 parents 74a3d0a + aba47ec commit 50df150

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/connections/spec/common.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -248,7 +248,7 @@ Sending data to the rest of Segment's destinations is opt-out so if you don't sp
248248

249249
Every API call has four timestamps, `originalTimestamp`, `timestamp`, `sentAt`, and `receivedAt.` They're used for very different purposes.
250250

251-
**All timestamps are [ISO-8601](http://en.wikipedia.org/wiki/ISO_8601){:target="_blank"} date strings.**
251+
**All timestamps are [ISO-8601](http://en.wikipedia.org/wiki/ISO_8601){:target="_blank"} date strings, and are in the UTC timezone.** To see the user's timezone information, check the `timezone` field that's automatically collected by [client-side libraries](/docs/connections/spec/common/#context-fields-automatically-collected).
252252

253253
> info ""
254254
> You must use ISO-8601 date strings that include timezones when you use timestamps with [Engage](/docs/engage/). If you send custom traits without a timezone, Segment doesn't save the timestamp value.

0 commit comments

Comments
 (0)