Skip to content

Commit 30b94f0

Browse files
authored
Clarify writekey usage
The writekey data is to help segment identify issues internally, rather than the customer
1 parent ac34f84 commit 30b94f0

File tree

1 file changed

+1
-1
lines changed
  • src/connections/sources/catalog/libraries/mobile/apple

1 file changed

+1
-1
lines changed

src/connections/sources/catalog/libraries/mobile/apple/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -170,7 +170,7 @@ The Analytics-Swift SDK collects telemetry data on configuration and usage by de
170170
171171
You can disable telemetry at any time by setting `Telemetry.shared.enable = false`.
172172
173-
When internal errors or errors from plugins occur, the write key may be included with error data to help you identify the issue(s). You can disable this by setting `Telemetry.shared.sendWriteKeyOnError = false`.
173+
When internal errors or errors from plugins occur, the write key may be included with error data to help Segment identify the issue(s). You can disable this by setting `Telemetry.shared.sendWriteKeyOnError = false`.
174174
175175
## Timestamps in Swift
176176
Due to efficiency updates made to Segment's Swift library, Segment now adds the `sentAt` timestamp to an event when the batch is complete and initially tried to the Segment API. This can impact the value of the `timestamp` field calculated by Segment if users are operating in an offline mode. More details on this change can be seen in Segment's [timestamp documentation](/docs/connections/spec/common/#sentat).

0 commit comments

Comments
 (0)