Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Timezone requirements when using Personas DOC-360 #2134

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 10, 2021
Merged

Timezone requirements when using Personas DOC-360 #2134

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion src/connections/spec/common.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -304,6 +304,9 @@ Every API call has four timestamps, `originalTimestamp`, `timestamp`, `sentAt` a

**All timestamps are [ISO-8601](http://en.wikipedia.org/wiki/ISO_8601) date strings.**

> note ""
> **NOTE:** ISO-8601 date strings with timezones included are required when using timestamps with [Personas](/docs/personas/). Sending custom traits without a timezone included in the timestamp will result in the value not being saved.

### Timestamp Overview

<table>
Expand Down Expand Up @@ -343,7 +346,7 @@ Every API call has four timestamps, `originalTimestamp`, `timestamp`, `sentAt` a
</tr>
<tr>
<td>`receivedAt`</td>
<td>time on Segment server clock when call was received</td>
<td>Time on Segment server clock when call was received</td>
<td>
Used by Segment to calculate `timestamp`, and used as sort key in Warehouses.
<br><br>
Expand Down
3 changes: 3 additions & 0 deletions src/connections/storage/warehouses/schema.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -336,6 +336,9 @@ All four timestamps pass through to your Warehouse for every ETL'd event. In mos

`received_at` does not ensure chronology of events. For queries based on event chronology, `timestamp` should be used.

> note ""
> **NOTE:** ISO-8601 date strings with timezones included are required when using timestamps with [Personas](/docs/personas/). Sending custom traits without a timezone included in the timestamp will result in the value not being saved.

To learn more about timestamps in Segment, [read our timestamps overview](/docs/connections/spec/common/#timestamps) in the Segment Spec.

## id
Expand Down