Make regional config URLs a snippet (#3689)

Author: markzegarelli

src/_includes/content/regional-config.md

@@ -0,0 +1,3 @@
+For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
+1. Oregon (Default) — `api.segment.io/`
+2. Dublin — `events.eu1.segmentapis.com/`

src/connections/sources/catalog/libraries/server/clojure/index.md

@@ -49,15 +49,13 @@ using the `Analytics` singleton anywhere in your code.
 The default initialization settings are production-ready.
 
 ### Regional configuration
-For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
-1. Oregon (Default) — `api.segment.io/v1`
-2. Dublin — `events.eu1.segmentapis.com/`
+{% include content/regional-config.md %}
 
 ## Identify
 
 `identify` lets you tie a user to their actions and record traits about them. It includes a unique User ID and any optional traits you know about them.
 
-We recommend calling `identify` a single time when the user's account is first created, and only identifying again later when their traits are change.
+Segment recommends calling `identify` a single time when the user's account is first created, and only identifying again later when their traits are change.
 
 Example `identify` call:
 

src/connections/sources/catalog/libraries/server/go/index.md

@@ -40,10 +40,7 @@ That will create a `client` that you can use to send data to Segment for your so
 The default initialization settings are production-ready and queue 20 messages before sending a batch request, and a 5 second interval.
 
 ### Regional configuration
-For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
-1. Oregon (Default) — `api.segment.io/v1`
-2. Dublin — `events.eu1.segmentapis.com/`
-
+{% include content/regional-config.md %}
 ## Identify
 
 > note ""

src/connections/sources/catalog/libraries/server/http-api/index.md

@@ -35,9 +35,7 @@ The HTTP API has no hard rate limit. However, Segment recommends not exceeding 5
 There is a maximum of `32KB` per normal API request.  The `batch` API endpoint accepts a maximum of `500KB` per request, with a limit of `32KB` per event in the batch.  If you are sending data from a server source, Segment's API responds with `400 Bad Request` if these limits are exceeded.
 
 ## Regional configuration
-For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
-1. Oregon (Default) — `api.segment.io/v1`
-2. Dublin — `events.eu1.segmentapis.com/`
+{% include content/regional-config.md %}
 
 ## Identify
 

src/connections/sources/catalog/libraries/server/java/index.md

@@ -59,9 +59,7 @@ Although not enforced at compile time, make sure you provide either of `userId`
 The following examples use [Guava's](https://github.com/google/guava) immutable maps, but feel free to use plain old Java maps instead.
 
 ### Regional configuration
-For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
-1. Oregon (Default) — `api.segment.io/v1`
-2. Dublin — `events.eu1.segmentapis.com/`
+{% include content/regional-config.md %}
 ## Identify
 
 > note ""

src/connections/sources/catalog/libraries/server/kotlin/index.md

@@ -65,9 +65,7 @@ To get started with the Analytics-Kotlin server library:
     `useLifecycleObserver` | Default set to `false`. <br> Set to `true` to use `LifecycleObserver` to track Application lifecycle events. |
 
 ### Regional configuration
-For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
-1. Oregon (Default) — `api.segment.io/v1`
-2. Dublin — `events.eu1.segmentapis.com/`
+{% include content/regional-config.md %}
 ## Tracking Methods
 
 Once you've installed the mobile or server Analytics-Kotlin library, you can start collecting data through Segment's tracking methods:

src/connections/sources/catalog/libraries/server/net/index.md

@@ -79,9 +79,7 @@ You only need to initialize once at the start of your program. You can then keep
 The default initialization settings are production-ready and queue messages on another thread before sending any requests. In development you might want to use [development settings](/docs/connections/sources/catalog/libraries/server/net/#development-settings).
 
 ### Regional configuration
-For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
-1. Oregon (Default) — `api.segment.io/v1`
-2. Dublin — `events.eu1.segmentapis.com/`
+{% include content/regional-config.md %}
 
 ## Identify
 

src/connections/sources/catalog/libraries/server/php/index.md

@@ -44,9 +44,7 @@ Of course, you'll want to replace `YOUR_WRITE_KEY` with your actual **Write Key*
 The default PHP consumer is the [lib-curl consumer](#lib-curl-consumer). If this is not working well for you, or if you have a high-volume project, you may want to try one of our other consumers like the [fork-curl consumer](#fork-curl-consumer).
 
 ### Regional configuration
-For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
-1. Oregon (Default) — `api.segment.io/v1`
-2. Dublin — `events.eu1.segmentapis.com/`
+{% include content/regional-config.md %}
 
 ## Identify
 

src/connections/sources/catalog/libraries/server/python/index.md

@@ -56,9 +56,7 @@ analytics.send = False
 **Using Django?** Check out the [Django docs](/docs/connections/sources/catalog/libraries/server/python/#django).
 
 ### Regional configuration
-For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
-1. Oregon (Default) — `https://api.segment.io/v1`
-2. Dublin — `https://events.eu1.segmentapis.com/`
+{% include content/regional-config.md %}
 
 ## Identify
 

src/connections/sources/catalog/libraries/server/ruby/index.md

@@ -45,16 +45,14 @@ If you're using Rails, you can stick that initialization logic in `config/initia
 > The analytics-ruby gem makes requests asynchronously, which can sometimes be suboptimal and difficult to debug if you're pairing it with a queuing system like Sidekiq/delayed job/sucker punch/resqueue. If you'd prefer to use a gem that makes requests synchronously, you can check out [`simple_segment`](https://github.com/whatthewhat/simple_segment){:target="_blank"} , an API-compatible drop-in replacement for the standard gem that does its work synchronously inline. Big thanks to [Mikhail Topolskiy](https://github.com/whatthewhat){:target="_blank"}  for his stewardship of this alternative gem!
 
 ### Regional configuration
-For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
-1. Oregon (Default) — `api.segment.io/v1`
-2. Dublin — `events.eu1.segmentapis.com/`
+{% include content/regional-config.md %}
 
 ## Identify
 
 > note ""
 > **Good to know**: For any of the different methods described on this page, you can replace the properties and traits in the code samples with variables that represent the data collected.
 
-The `identify` method is how you associate your users and their actions to a recognizable `userId` and `traits`. You can [find details on the identify method payload in our Spec](/docs/connections/spec/identify/).
+The `identify` method is how you associate your users and their actions to a recognizable `userId` and `traits`. You can [find details on the identify method payload in the Spec](/docs/connections/spec/identify/).
 
 The `identify` call has the following fields: