Skip to content

Remove mention of timestamp modification in mobile libs #1409

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 3 commits into from
Feb 10, 2021
Merged

Remove mention of timestamp modification in mobile libs #1409

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
da129ef
Remove mention of timestamp modification in mobile libs
Feb 10, 2021
68320a4
Merge branch 'master' into bsneed/mobile-timestamps
sanscontext Feb 10, 2021
2c81ae8
Merge branch 'master' into bsneed/mobile-timestamps
sanscontext Feb 10, 2021
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
2 changes: 1 addition & 1 deletion src/connections/spec/common.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -392,4 +392,4 @@ The `receivedAt` timestamp is most important as the sort key in our Warehouses p

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.

If you are using the Segment server Source libraries, or passing calls directly to the HTTP API endpoint, you can manually set the `timestamp` field. If you are using a Segment Source in device mode, the library generates `timestamp` and you cannot manually set one directly in the call payload. However, for mobile sources, you can use Middleware ([Middleware for iOS](/docs/connections/sources/libraries/mobile/ios/middleware/), [Middleware for Android](/docs/connections/sources/libraries/mobile/ios/middleware/)) to modify the payload, including the timestamp. (You might manually set or override a timestamp to import historical data to the Segment API).
If you are using the Segment server Source libraries, or passing calls directly to the HTTP API endpoint, you can manually set the `timestamp` field. If you are using a Segment Source in device mode, the library generates `timestamp` and you cannot manually set one directly in the call payload.