diff --git a/src/connections/sources/catalog/libraries/website/javascript/faq.md b/src/connections/sources/catalog/libraries/website/javascript/faq.md
index ec998a3757..ad7993651b 100644
--- a/src/connections/sources/catalog/libraries/website/javascript/faq.md
+++ b/src/connections/sources/catalog/libraries/website/javascript/faq.md
@@ -11,6 +11,14 @@ Yes, the limit is 32KB per event message. Events with a payload larger than 32KB
 
 In the event that Analytics.js does not load, callbacks passed into your API calls do not fire. This is as designed, because the purpose of callbacks are to provide an estimate that the event was delivered and if the library never loads, the events won't be delivered.
 
+## Is there an updated version of the Segment snippet?
+Segment released an updated version of the Analytics.js snippet, which introduces several enhancements and fixes that might improve your setup. For a full list of version updates, see the Analytics.js snippet's [Releases](https://github.com/segmentio/snippet/releases){:target="_blank”}.
+
+You can find the latest version of the Segment snippet in your JavaScript source's Overview tab or in the [Quickstart: Analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/#step-2a-add-the-segment-snippet) documentation.
+ 
+While there is no deadline to upgrade your snippet to the latest version, upgrading lets you use the latest improvements in the Segment library.
+
+
 ## Why do I see a network request to `/m`?
 
 In May 2018, Segment began collecting client-side performance metrics in Analytics.js. This includes metrics like: