Explain why AJS Write Key is public (#1035)

bryanmikaelian · sanscontext · web-flow · commit ed262bd3c0fa · 2020-08-04T13:19:23.000-07:00
* Explain why Write Key is public

* Update src/connections/sources/catalog/libraries/website/javascript/quickstart.md

Co-authored-by: LRubin &lt;sanscontext@users.noreply.github.com&gt;

Co-authored-by: LRubin &lt;sanscontext@users.noreply.github.com&gt;
diff --git a/src/connections/sources/catalog/libraries/website/javascript/quickstart.md b/src/connections/sources/catalog/libraries/website/javascript/quickstart.md
@@ -20,6 +20,9 @@ Installing Segment is easy, just paste this snippet into the `<head>` tag of you
 
 Next, replace `YOUR_WRITE_KEY` in the snippet you pasted with your Segment project's **Write Key**, which you can find in your project set up guide or settings.
 
+> note ""
+> **Note:** When you use Analytics.js in device-mode the source's Write Key is public, because it runs in a user's browser and can be accessed using the browser's developer tools. If this is not acceptable to your organization, you can explore [other Segment Sources](/docs/connections/sources/catalog/) which collect data from a server-based installation, and which are not accessible to the user.
+
 That snippet loads Analytics.js onto the page _asynchronously_, so it won't affect your page load speed. Once the snippet is running on your site, you can turn on destinations from the destinations page in your workspace and they start loading on your site automatically!
 
 Note that you should remove other native third-party destination code that you might have on your site. For example, if you're using Segment to send data to Google Analytics, make sure you remove the Google Analytics snippet from your site source code to prevent sending the data twice.
