segmentio · sanscontext · Nov 22, 2019 · Nov 22, 2019
@@ -20,7 +20,7 @@ sections:
   section:
   - path: "https://segment.com/docs/"
     title: Documentation
-  - path: "https://segment.com/docs/sources/"
+  - path: "https://segment.com/docs/connections/sources/"
     title: Segment API
   - path: "https://segment.com/partners/developer-center/"
     title: Build on Segment
@@ -32,7 +32,7 @@ sections:
   section:
   - path: "https://segment.com/docs/"
     title: Customer Stories
-  - path: "https://segment.com/docs/sources/"
+  - path: "https://segment.com/docs/connections/sources/"
     title: Enterprise
   - path: "https://segment.com/partners/developer-center/"
     title: Startups
@@ -48,7 +48,7 @@ sections:
   section:
   - path: "https://segment.com/docs/"
     title: Careers
-  - path: "https://segment.com/docs/sources/"
+  - path: "https://segment.com/docs/connections/sources/"
     title: Blog
   - path: "https://segment.com/partners/developer-center/"
     title: Press
@@ -60,7 +60,7 @@ sections:
   section:
   - path: "https://segment.com/docs/"
     title: Help Center
-  - path: "https://segment.com/docs/sources/"
+  - path: "https://segment.com/help/contact/"
     title: Contact us
   - path: "https://segment.com/partners/developer-center/"
     title: Resources

@@ -8,7 +8,7 @@ platforms -> what data do we recognize-->
 
 
 
-The first step is to make sure {{ currentIntegration.display_name }} supports the source type and connection mode you've chosen to implement. You can learn more about what dictates [the connection modes we support here](https://segment.com/docs/destinations/#connection-modes).
+The first step is to make sure {{ currentIntegration.display_name }} supports the source type and connection mode you've chosen to implement. You can learn more about what dictates [the connection modes we support here](https://segment.com/docs/connections/destinations/#connection-modes).
 
 <table>
   <tr>

@@ -10,7 +10,7 @@
 
 You can send computed traits and audiences generated through [Segment Personas](/docs/personas) to this destination as a **user property**. To learn more about Personas, reach out for a [demo](https://segment.com/contact/demo).
 
-For user-property destinations, an [identify](/docs/spec/identify) call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property `order_completed_last_30days: true`, and when this user no longer satisfies we will set that value to `false`.
+For user-property destinations, an [identify](/docs/connections/spec/identify) call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property `order_completed_last_30days: true`, and when this user no longer satisfies we will set that value to `false`.
 
 When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.
 
@@ -23,7 +23,7 @@ When the audience is first created an identify call is sent for every user in th
 {% if currentIntegration.components.size > 0 %}
 {% include content/connection-modes.md %}
 
-To learn more about about Connection Modes and what dictates which we support, [see here](https://segment.com/docs/destinations/#connection-modes).
+To learn more about about Connection Modes and what dictates which we support, [see here](https://segment.com/docs/connections/destinations/#connection-modes).
 
 {% endif %}
 

@@ -1,3 +1,3 @@
 ### More About Identify
 
-To learn more about how `identify` works, check out our [Identify docs](/docs/spec/identify). For example, `email` and `name` are two of our [special traits](/docs/spec/identify#special-traits) that we recognize semantically.
+To learn more about how `identify` works, check out our [Identify docs](/docs/connections/spec/identify). For example, `email` and `name` are two of our [special traits](/docs/connections/spec/identify#special-traits) that we recognize semantically.
@@ -1,3 +1,3 @@
 ### More About Track
 
-To learn more about how `track` works check out our [Track docs](/docs/spec/track). For example, `revenue` is a [special property](/docs/spec/track#special-properties) that lets you semantically describe how much money you're making.
+To learn more about how `track` works check out our [Track docs](/docs/connections/spec/track). For example, `revenue` is a [special property](/docs/connections/spec/track#special-properties) that lets you semantically describe how much money you're making.
@@ -2,6 +2,6 @@
 
 You can send computed traits and audiences generated through [Segment Personas](/docs/personas) to this destination as a **user property**. To learn more about Personas, reach out for a [demo](https://segment.com/contact/demo). 
 
-For user-property destinations, an [identify](/docs/spec/identify) call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property `order_completed_last_30days: true`, and when this user no longer satisfies we will set that value to `false`. 
+For user-property destinations, an [identify](/docs/connections/spec/identify) call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property `order_completed_last_30days: true`, and when this user no longer satisfies we will set that value to `false`. 
 
 When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.
@@ -3,6 +3,6 @@
   <td>*optional if userID is set instead*</td>
   <td>String</td>
   <td>A pseudo-unique substitute for a User ID, for cases when you don't have an absolutely unique identifier. A userId or an anonymousId is required.
-    <p>See the [Identities docs](/docs/spec/identify#identities) for more detail</p>
+    <p>See the [Identities docs](/docs/connections/spec/identify#identities) for more detail</p>
   </td>
 </tr>
@@ -3,6 +3,6 @@
   <td>*optional*</td>
   <td>Object</td>
   <td>Dictionary of extra information that provides useful context about a message, but is not directly related to the API call like `ip` address or `locale`
-  <p>See the [Context field docs](/docs/spec/common#context) for more detail</p>
+  <p>See the [Context field docs](/docs/connections/spec/common#context) for more detail</p>
 </td>
 </tr>
@@ -3,6 +3,6 @@
   <td>*optional*</td>
   <td>Object</td>
   <td>Free-form dictionary of properties of the event, like `revenue`
-    <p>See the [Properties docs](/docs/spec/track#properties) for a list of reserved property names</p>
+    <p>See the [Properties docs](/docs/connections/spec/track#properties) for a list of reserved property names</p>
   </td>
 </tr>
@@ -3,6 +3,6 @@
   <td>*required*</td>
   <td>String</td>
   <td>Name of the action that a user has performed.
-    <p>See the [Event field docs](/docs/spec/track#event) for more detail</p>
+    <p>See the [Event field docs](/docs/connections/spec/track#event) for more detail</p>
   </td>
 </tr>
@@ -3,6 +3,6 @@
   <td>*required*</td>
   <td>String</td>
   <td>A unique identifier for the group in your database.
-    <p>See the [Group ID field docs](/docs/spec/group#group-id) for more detail</p>
+    <p>See the [Group ID field docs](/docs/connections/spec/group#group-id) for more detail</p>
   </td>
 </tr>
@@ -3,6 +3,6 @@
   <td>*optional*</td>
   <td>Object</td>
   <td>Free-form dictionary of traits of the group, like `email` or `name`
-    <p>See the [Traits field docs](/docs/spec/group#traits) for a list of reserved trait names</p>
+    <p>See the [Traits field docs](/docs/connections/spec/group#traits) for a list of reserved trait names</p>
   </td>
 </tr>
@@ -3,6 +3,6 @@
   <td>*optional*</td>
   <td>Object</td>
   <td>Free-form dictionary of traits of the user, like `email` or `name`.
-    <p>See the [Traits field docs](/docs/spec/identify#traits) for a list of reserved trait names</p>
+    <p>See the [Traits field docs](/docs/connections/spec/identify#traits) for a list of reserved trait names</p>
   </td>
 </tr>
@@ -3,6 +3,6 @@
   <td>*optional*</td>
   <td>Object</td>
   <td>Dictionary of destinations to either enable or disable
-    <p>See the [Destinations field docs](/docs/spec/common#integrations) for more detail</p>
+    <p>See the [Destinations field docs](/docs/connections/spec/common#integrations) for more detail</p>
   </td>
 </tr>
@@ -3,5 +3,5 @@
   <td>*optional*</td>
   <td>Object</td>
   <td>Free-form dictionary of properties of the page, like `url` and `referrer`
-    <p>See the [Properties field docs](/docs/spec/page#properties) for a list of reserved property names</p></td>
+    <p>See the [Properties field docs](/docs/connections/spec/page#properties) for a list of reserved property names</p></td>
 </tr>
@@ -3,6 +3,6 @@
   <td>*required*</td>
   <td>String</td>
   <td>Previous unique identifier for the user
-    <p>See the [Previous ID field docs](/docs/spec/alias#previous-id) for more detail</p>
+    <p>See the [Previous ID field docs](/docs/connections/spec/alias#previous-id) for more detail</p>
   </td>
 </tr>
@@ -3,6 +3,6 @@
   <td>*implicit*</td>
   <td>Date</td>
   <td>Automatically set by Segment, the timestamp of when a message is received by Segment
-    <p>It is an [ISO-8601](http://en.wikipedia.org/wiki/ISO_8601) date string.  See the [Timestamps fields docs](/docs/spec/common#timestamps) for more detail</p>
+    <p>It is an [ISO-8601](http://en.wikipedia.org/wiki/ISO_8601) date string.  See the [Timestamps fields docs](/docs/connections/spec/common#timestamps) for more detail</p>
   </td>
 </tr>
@@ -3,6 +3,6 @@ _<tr>
   <td>*optional*</td>
   <td>String</td>
   <td>Name of the screen
-    <p>See the [Name field docs](/docs/spec/screen#name) for more detail</p>
+    <p>See the [Name field docs](/docs/connections/spec/screen#name) for more detail</p>
   </td>
 </tr>
@@ -3,6 +3,6 @@
   <td>*optional*</td>
   <td>Object</td>
   <td>Free-form dictionary of properties of the screen, like `name`
-    <p>See the [Properties field docs](/docs/spec/screen#properties) for a list of reserved property names</p>
+    <p>See the [Properties field docs](/docs/connections/spec/screen#properties) for a list of reserved property names</p>
   </td>
 </tr>
@@ -3,5 +3,5 @@
   <td>*optional*</td>
   <td>Date</td>
   <td>Timestamp of when a message is sent to Segment, used for clock skew correction
-    <p>It is set automatically by the Segment tracking libraries. It is an [ISO-8601](http://en.wikipedia.org/wiki/ISO_8601) date string. See the [Timestamps fields docs](/docs/spec/common#timestamps) for more detail.</p> </td>
+    <p>It is set automatically by the Segment tracking libraries. It is an [ISO-8601](http://en.wikipedia.org/wiki/ISO_8601) date string. See the [Timestamps fields docs](/docs/connections/spec/common#timestamps) for more detail.</p> </td>
 </tr>
@@ -4,5 +4,5 @@
   <td>Date</td>
   <td>Timestamp when the message itself took place, defaulted to the current time by the Segment Tracking API
     <p>It is an [ISO-8601](http://en.wikipedia.org/wiki/ISO_8601) date string</p>
-    <p>If the event just happened, leave it out and we'll use the server's time. If you're importing data from the past, make sure you to provide a `timestamp`.See the [Timestamps fields docs](/docs/spec/common#timestamps) for more detail.</p></td>
+    <p>If the event just happened, leave it out and we'll use the server's time. If you're importing data from the past, make sure you to provide a `timestamp`.See the [Timestamps fields docs](/docs/connections/spec/common#timestamps) for more detail.</p></td>
 </tr>
@@ -4,6 +4,6 @@
   <td>String</td>
   <td>Unique identifier for the user in your database
     <p>A userId or an anonymousId is required </p>
-    <p>See the [Identities docs](/docs/spec/identify#identities) for more detail</p>
+    <p>See the [Identities docs](/docs/connections/spec/identify#identities) for more detail</p>
   </td>
 </tr>
@@ -1,5 +1,5 @@
-The User ID is a unique identifier for the user performing the actions. Check out the [User ID docs](/docs/spec/identify#user-id) for more detail.
+The User ID is a unique identifier for the user performing the actions. Check out the [User ID docs](/docs/connections/spec/identify#user-id) for more detail.
 
-The Anonymous ID can be any pseudo-unique identifier, for cases where you don't know who the user is, but you still want to tie them to an event. Check out the [Anonymous ID docs](/docs/spec/identify#anonymous-id) for more detail.
+The Anonymous ID can be any pseudo-unique identifier, for cases where you don't know who the user is, but you still want to tie them to an event. Check out the [Anonymous ID docs](/docs/connections/spec/identify#anonymous-id) for more detail.
 
-**Note: In our browser and mobile libraries a User ID is automatically added** from the state stored by a previous [`identify`](/docs/spec/identify/) call, so you do not need to add it yourself. They will also automatically handle Anonymous ID's under the covers.
+**Note: In our browser and mobile libraries a User ID is automatically added** from the state stored by a previous [`identify`](/docs/connections/spec/identify/) call, so you do not need to add it yourself. They will also automatically handle Anonymous ID's under the covers.
@@ -3,7 +3,7 @@ In Segment, you create a source (or more than one!) for each website or app you
 Sources belong to a workspace, and the URL for a source look something like this:
 `https://segment.com/<my-workspace>/sources/<my-source-name>/`
 
-You can create new sources using the button in the workspace view. Each source you create has a write key, which is used to send data to that source. For example, to load [`analytics.js`, the Segment JavaScript library](https://segment.com/docs/sources/website/analytics.js/) on your page, the snippet on the [Quickstart Guide](https://segment.com/docs/sources/website/analytics.js/quickstart/) includes:
+You can create new sources using the button in the workspace view. Each source you create has a write key, which is used to send data to that source. For example, to load [`analytics.js`, the Segment JavaScript library](https://segment.com/docs/connections/sources/catalog/libraries/website/analytics.js/) on your page, the snippet on the [Quickstart Guide](https://segment.com/docs/connections/sources/catalog/libraries/website/analytics.js/quickstart/) includes:
 
 ```js
 analytics.load("YOUR_WRITE_KEY");

@@ -119,7 +119,7 @@ $ curl \
 
 > Analytics.js
 >
-> The Javascript source requires that you add analytics.js to your website to collect data. See the [Quickstart: Analytics.js](https://segment.com/docs/sources/website/analytics.js/quickstart/) guide for full details.
+> The Javascript source requires that you add analytics.js to your website to collect data. See the [Quickstart: Analytics.js](https://segment.com/docs/connections/sources/catalog/libraries/website/analytics.js/quickstart/) guide for full details.
 
 ## Create a Google Analytics Destination
 
@@ -173,7 +173,7 @@ $ curl \
 
 ## Update Google Analytics Settings
 
-Over time we may want to modify the Google Analytics destination settings. First, the destination was created as disabled by default, so we can use the API to enable it. We can also toggle other settings like "[server side identify](https://segment.com/docs/destinations/google-analytics/#server-side-identify)". Note the required `update_mask` field that explicitly specifies the fields you want to update.
+Over time we may want to modify the Google Analytics destination settings. First, the destination was created as disabled by default, so we can use the API to enable it. We can also toggle other settings like "[server side identify](https://segment.com/docs/connections/destinations/catalog/google-analytics/#server-side-identify)". Note the required `update_mask` field that explicitly specifies the fields you want to update.
 
 ```shell
 $ curl -i \
@@ -227,13 +227,13 @@ $ curl -i \
 }
 ```
 
-See the [Google Analytics Destination](https://segment.com/docs/destinations/google-analytics/) reference for all the settings.
+See the [Google Analytics Destination](https://segment.com/docs/connections/destinations/catalog/google-analytics/) reference for all the settings.
 
 ## Send Sample Events
 
 We can also test our source and destination by interacting with the Tracking API from the command line.
 
-Let's send an events to our new source. Note that `userID` is required and the `name` and `url` properties are expected by Google Analytics and other website tools. See the [Page API spec](https://segment.com/docs/sources/server/http/#page) for more details.
+Let's send an events to our new source. Note that `userID` is required and the `name` and `url` properties are expected by Google Analytics and other website tools. See the [Page API spec](https://segment.com/docs/connections/sources/catalog/libraries/server/http/#page) for more details.
 
 ```shell
 $ WRITE_KEY=LxKXARX9IuqR9v0gn7y2Fw1iHi0ephbF
-Original file line number
+Diff line change
@@ Expand Up / @@ -8,7 +8,7 @@ platforms -> what data do we recognize--> @@
-    The first step is to make sure {{ currentIntegration.display_name }} supports the source type and connection mode you've chosen to implement. You can learn more about what dictates [the connection modes we support here](https://segment.com/docs/destinations/#connection-modes).
+    The first step is to make sure {{ currentIntegration.display_name }} supports the source type and connection mode you've chosen to implement. You can learn more about what dictates [the connection modes we support here](https://segment.com/docs/connections/destinations/#connection-modes).
     <table>
       <tr>
@@ Expand Down @@