Merge pull request #1195 from segmentio/ios-android-timestamp

Jessica-Kuo · web-flow · commit f7628126f24e · 2020-11-05T15:10:43.000-05:00
updated 'timestamp' field functionality in group calls
diff --git a/src/connections/sources/catalog/libraries/mobile/ios/index.md b/src/connections/sources/catalog/libraries/mobile/ios/index.md
@@ -438,7 +438,7 @@ The Group call has the following fields:
   </tr>
   <tr>
     <td>`options` _Options, optional_</td>
-    <td>An `Options` object lets you set a [timestamp](/docs/connections/spec/common/#timestamps), [enable or disable destinations](#selecting-destinations), or [send additional context](/docs/connections/spec/common/#context).</td>
+    <td>An `Options` object lets you [enable or disable destinations](#selecting-destinations), or [send additional context](/docs/connections/spec/common/#context).</td>
   </tr>
 </table>
 
diff --git a/src/connections/spec/common.md b/src/connections/spec/common.md
@@ -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.
 
-The `timestamp` field is settable from our server-side libs or if passing info directly to the HTTP endpoints.
+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 (including the mobile sources), the library generates `timestamp` and you cannot manually set one.  (You might manually set or override a timestamp to import historical data to the Segment API).

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.
	`395`	+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 (including the mobile sources), the library generates `timestamp` and you cannot manually set one. (You might manually set or override a timestamp to import historical data to the Segment API).