Merge pull request #4100 from segmentio/vanand17-patch-6

Impact of exposing the source write key - AJS

Author: stayseesong

src/connections/sources/catalog/libraries/website/javascript/troubleshooting.md

@@ -128,9 +128,17 @@ analytics.track("Receipt Viewed", {}, {
     }
 })
 ```
-
 This works for any [context field](/docs/connections/spec/common/#context) that Segment automatically collects.
 
+
+### What is the impact of exposing the source's write keys?
+
+For the Segment script to work in the browser, you need to expose the write key in order for client-side tracking to work. Segment's library architecture requires the write key to be exposed, similar to that of other major tools like Google Analytics, Mixpanel, Kissmetrics, Hubspot, and Marketo.
+ 
+If you see any unusual behavior associated with your write key, you can generate a new key. Navigate to **Connections > Sources** and select your source. On the **Settings** tab, go to the **API Keys** section, and click **Generate New Key**.
+
+If you want to hide the write key, you can use Segment's [HTTP Tracking API source](/docs/connections/sources/catalog/libraries/server/http-api/) or one of the other [server-side libraries](/docs/connections/sources/catalog/#server).
+
 ### Can I add context fields that do not already exist?
 
 Yes. Similar to overwriting context, you can add context fields by passing them into the options object as the third argument of the event call. For example, the analytics.js library does not automatically collect location information. To add this into the context object, pass it into the third argument as in the example below:
@@ -149,7 +157,6 @@ analytics.track("Order Completed", {}, {
 
 Some destinations accept properties only. As a result, custom context fields you add may not forward to these destinations.
 
-
 ## Known issues:
 
 [Review and contribute to these on GitHub](https://github.com/segmentio/analytics.js/issues)