Skip to content

Commit b37739a

Browse files
committed
README improvements
1 parent 13fec3a commit b37739a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ Note that all SDK communication with Optable DCNs is done over TLS. The only exc
106106
MainActivity.OPTABLE = OptableSDK(this, "dcn.customer.com", "my-app", true)
107107
```
108108

109-
However, since production DCNs only listen to TLS traffic, the above is meant for Optable developers running the DCN locally for testing.
109+
Note that production DCNs only listen to TLS traffic. The `insecure: true` option is meant to be used by Optable developers running the DCN locally for testing.
110110

111111
By default, the SDK detects the application user agent by sniffing `settings.userAgentString` from a `WebView`. The resulting user agent string is sent to your DCN for analytics purposes. To disable this behavior, you can provide an optional fifth string parameter `useragent`, which allows you to set whatever user agent string you would like to send instead. For example, in Kotlin:
112112

@@ -460,7 +460,7 @@ Working examples are available in the Kotlin and Java SDK demo applications.
460460

461461
## Identifying visitors arriving from Email newsletters
462462

463-
If you send Email newsletters that contain links to your application (e.g., deep links), then you may want to automatically _identify_ visitors that have clicked on any such links via their Email address. Incoming application traffic which is originating from a subscriber click on a link in a newsletter is considered to be implicitly authenticated by the recipient of the Email, therefore serving as an excellent source of linking of online user identities.
463+
If you send Email newsletters that contain links to your application (e.g., deep links), then you may want to automatically _identify_ visitors that have clicked on any such links via their Email address.
464464

465465
### Insert oeid into your Email newsletter template
466466

0 commit comments

Comments
 (0)