404 fixes (#959)

* 404 fixes

* more 404s

Author: sanscontext

src/_data/glossary.yml

@@ -81,7 +81,7 @@ Lookback: |
   A “lookback window” limits the period of time in which data is considered when calculating a trait or audience. For example, you might set a lookback window of 7 days on an audience or trait like `new_users_7_days`, but you would not add a lookback window to a trait that isn’t time-bounded, such as `lifetime_value`.
 
 Method: |
-  A method is programming speak for "an action an object can take". It's a specific type of function that is attached to an object. All of our analytics tracking libraries create `analytics` objects, and then `track`, `identify`, `page`, [etc](/docs/conncetions/spec/) are methods you can invoke on those objects.
+  A method is programming speak for "an action an object can take". It's a specific type of function that is attached to an object. All of our analytics tracking libraries create `analytics` objects, and then `track`, `identify`, `page`, [etc](/docs/connections/spec/) are methods you can invoke on those objects.
 
 MTU: |
   Monthly Tracked Users. You can find more about how they are calculated [here](https://segment.com/docs/guides/usage-and-billing/how-are-mtus-calculated-by-segment/) but in short, they are calculated by adding the number unique userIds and number of unique anonymousIds that a customer tracks with Segment.

src/_data/sidenav/_auto/main.yml

@@ -27,7 +27,7 @@ sections:
     section:
     - path: /connections/sources
       title: Sources Overview
-    - path: /connections/sources/cloud-source-data
+    - path: /connections/sources/about-cloud-sources
       title: What can you do with cloud source data?
     - path: /connections/sources/custom-domains
       title: Set up a custom domain proxy in Segment
@@ -37,7 +37,7 @@ sections:
       title: Sources
     - path: /connections/sources/visual-tagger
       title: Visual Tagger
-    - path: /connections/sources/what-are-cloud-sources
+    - path: /connections/sources/about-cloud-sources
       title: What are Cloud-App Sources?
   - section_title: Spec
     slug: connections/spec

src/_data/sidenav/_auto/partners.yml

@@ -3,9 +3,9 @@ sections:
   section:
   - path: /partners
     title: Developer Center Overview
-  - path: /partners/build-functions
+  - path: /partners/subscriptions/build-functions
     title: Building a Subscription Function
-  - path: /partners/build-webhook
+  - path: /partners/subscriptions/build-webhook
     title: Building a Subscription Webhook
   - path: /partners/checklist
     title: Public Beta Checklist

src/connections/destinations/catalog/adwords-remarketing-lists/index.md

@@ -28,7 +28,7 @@ The Google Adwords Remarketing Lists Destination is one of our most popular Pers
 
 This Destination can send *audiences* (lists of users) created in [Personas](/docs/personas/) to Google Adwords Audience Lists as a [**Customer List**](https://support.google.com/google-ads/answer/7558048) type. Once you set this up, Segment sends an [initial list](https://developers.google.com/analytics/devguides/config/mgmt/v3/remarketing#insert) of users to Google Adwords Audience lists as a “Customer list”. As users move in and out of the audience, Segment automatically [updates the list](https://developers.google.com/analytics/devguides/config/mgmt/v3/remarketing#insert) in Google on an hourly basis. This allows you to run advertising campaigns without having manually update the list of users to target in Adwords campaigns.
 
-Currently, you can only send either an email address or mobile id (IDFA) from Segment Personas to Google as custom matchers. You can set an email address on the user profile by including `email` as a trait on an [`identify` call](/docs/connections/spec/identify/), as a property on a [`track` call](/docs/connections/spec/track/) or as an [external id](/docs/personas/identity-resolution-externalids/) for the user.
+Currently, you can only send either an email address or mobile id (IDFA) from Segment Personas to Google as custom matchers. You can set an email address on the user profile by including `email` as a trait on an [`identify` call](/docs/connections/spec/identify/), as a property on a [`track` call](/docs/connections/spec/track/) or as an [external id](/docs/personas/identity-resolution/externalids/) for the user.
 If you use Segment’s mobile SDK to collect events from a mobile app, the user’s IDFA is automatically captured. If you do not use Segment’s mobile SDK, you can set the user’s IDFA by setting it within `context.device.advertisingId`.
 
 When you send an audience to Google Adwords Remarketing Lists, you can choose which custom matcher (email or mobile id/IDFA) to match with. If a user has multiple emails or IDFAs on their account as `external_ids`, Personas only sends Adwords the ID that was most recently added to the user profile.

src/connections/destinations/catalog/attribution/index.md

@@ -4,9 +4,9 @@ rewrite: true
 ---
 [Attribution](http://attributionapp.com/) is an easy to use one stop dashboard for multi-touch attribution across all marketing channels. Attribution prides itself on high-fidelity and allows marketers to trace every visit, conversion or revenue dollar to the source. Marketers can easily integrate Attribution and Segment to begin measuring the effectiveness of their campaigns today.
 
-This destination is maintained by Attribution. For any issues with the destination, [contact their team](Support@attribtutionapp.com).
+This destination is maintained by Attribution. For any issues with the destination, [contact their team](mailto:support@attribtutionapp.com).
 
-This document was last updated on March 9, 2020. If you notice any gaps, out-dated information, or simply want to leave some feedback to help us improve our documentation, [let us know](Support@attribtutionapp.com)!
+This document was last updated on March 9, 2020. If you notice any gaps, out-dated information, or simply want to leave some feedback to help us improve our documentation, [let us know](mailto:support@attribtutionapp.com)!
 
 ## Getting Started
 

src/connections/destinations/catalog/canny/index.md

@@ -5,7 +5,7 @@ rewrite: true
 
 [Canny](https://canny.io) is a single place for all customer feedback. It saves you time managing all the feedback while keeping your customers in the loop. Let your customers post and vote on feedback from within your website or mobile app. You'll get an organized list of feedback that you can use to inform your roadmap.
 
-This destination is maintained by Canny. For any issues with the destination, [contact their team]([email protected]).
+This destination is maintained by Canny. For any issues with the destination, [contact their team](mailto:[email protected]).
 
 ## Getting Started
 

src/connections/destinations/catalog/experiments-by-growthhackers/index.md

@@ -1,6 +1,7 @@
 ---
 rewrite: true
 title: Experiments by Growthhackers Destination
+redirect_from: '/connections/destinations/catalog/northstar-by-growthhackers/'
 ---
 [Experiments by Growthhackers](http://growthhackers.com/software) provides a project management tool for growth teams, allowing companies to create and prioritize ideas, run experiments and gather data to learn upon!
 

src/connections/destinations/catalog/firebase/index.md

@@ -125,7 +125,7 @@ Firebase automatically collects [these user properties](https://support.google.c
 
 When you call `track` Segment will log the event with Firebase. Firebase automatically tracks [the events listed here](https://support.google.com/firebase/answer/6317485) and it will still do so when bundling with Segment.
 
-Firebase has a limit of 500 distinctly named events so it pays off to be [intentional in what you track](/docs/faqs/sources/what-to-track/).
+Firebase has a limit of 500 distinctly named events so it pays off to be [intentional in what you track](/docs/protocols/tracking-plan/best-practices/).
 
 When you call `track`, Segment maps from the [Segment spec](/docs/connections/spec/) to those that match Firebase's spec. For anything that does not match, Segment will pass the event to Firebase as a custom event. Custom parameters cannot be seen directly in the Firebase Analytics dashboard but they can be used as filters in **Audiences**.
 

src/connections/destinations/catalog/google-analytics/index.md

@@ -725,7 +725,7 @@ analytics.on('track', function(event, properties, options){
 
 **Important**: Keep in mind you will need to do all the data translation/properties mapping inside this `.on()` function before you send the event to Google Analytics like you see in our [destination code](https://github.com/segment-integrations/analytics.js-integration-google-analytics/blob/master/lib/index.js#L161-L207).
 
-To do this server side, you can create a separate [source](https://help.segment.com/hc/en-us/articles/204892239-What-are-sources-) in Segment, and within this source enter your GA credentials for the second tracker.
+To do this server side, you can create a separate [source](/docs/connections/sources/) in Segment, and within this source enter your GA credentials for the second tracker.
 
 This source can be your server-side source. From there, its easy to send data to multiple projects server-side, as you can see in this [Node example](/docs/connections/sources/catalog/libraries/server/node/#multiple-clients) you can initialize multiple instances of our library.
 
@@ -810,11 +810,11 @@ You may, however, want to deploy [page hiding](https://support.google.com/360sui
 
 ### User Deletion
 
-You can use Segment's in-app Privacy Tool to send deletion requests using `userId`s. This deletes a user from your connected raw Data Destinations and forwards a deletion request to Google Analytics. [See the Privacy Tools documentation](/docs/privacy/user-deletion-and-suppression/) to learn more. 
+You can use Segment's in-app Privacy Tool to send deletion requests using `userId`s. This deletes a user from your connected raw Data Destinations and forwards a deletion request to Google Analytics. [See the Privacy Tools documentation](/docs/privacy/user-deletion-and-suppression/) to learn more.
 
 To enable user deletion for Google Analytics:
 1. Navigate to the the **User Deletion** setting in your Segment Google Analytics destination settings
-2. Authenticate your Google Analytics account using OAuth. 
+2. Authenticate your Google Analytics account using OAuth.
 
 > **Note**: User deletion for Google Analytics is currently only supported for Universal Analytics and not Classic Analytics. You also can only send user deletion requests using a `userId` through the Privacy Tool. This means you must  have the User-Id feature enable in your Google Analytics Property within the your Google Analytics dashboard and have Segment sending your Property `userIds` by enabling the setting **Send User-ID to GA**.
 

src/connections/destinations/catalog/moengage/index.md

@@ -373,7 +373,7 @@ If you selected `HTTPS` mode, you must take some additional steps:
 * serviceworker.js
 
 > note ""
-> **Note**: Make sure the name of the serviceworker file is exactly `serviceworker.js`. [Contact MoEngage support]([email protected]) if you need to rename the serviceworker file.
+> **Note**: Make sure the name of the serviceworker file is exactly `serviceworker.js`. [Contact MoEngage support](mailto:[email protected]) if you need to rename the serviceworker file.
 
 2. Use your serviceworker file (HTTPS only)
 

src/connections/destinations/catalog/proof-experiences/index.md

@@ -2,7 +2,7 @@
 title: 'Proof Experiences Destination'
 beta: true
 rewrite: true
-redirect_from: '/connections/destinations/proof/'
+redirect_from: '/connections/destinations/catalog/proof/'
 ---
 
 [Proof Experiences](https://useproof.com/experiences?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) helps B2B SaaS businesses increase new trials and demos by creating delightfully personalized experiences for their visitors and customers.

src/connections/destinations/catalog/wootric/index.md

@@ -3,11 +3,11 @@ rewrite: true
 title: Wootric Destination
 ---
 
-[Wootric](https://www.wootric.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is the modern customer feedback management platform that brands around the globe use to make experience their competitive advantage. 
+[Wootric](https://www.wootric.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is the modern customer feedback management platform that brands around the globe use to make experience their competitive advantage.
 
 The Wootric Destination is open-source. You can browse the code [on GitHub](https://github.com/segment-integrations/analytics.js-integration-wootric).
 
-This document was last updated on January 23, 2020. If you notice any gaps, out-dated information or simply want to leave some feedback to help us improve our documentation, let us [know]([email protected])!
+This document was last updated on January 23, 2020. If you notice any gaps, out-dated information or simply want to leave some feedback to help us improve our documentation, [contact Wootric Support](mailto:[email protected])!
 
 
 ## Getting Started

src/connections/destinations/index.md

@@ -83,7 +83,7 @@ In order to override the default, check the destination settings pane in the Seg
 
 ## Data Deliverability
 
-Segment increases deliverability to destinations in two ways: [retries](#retries) and [replays](docs/guides/what-is-replay/). Retries happen automatically for all customers, while replays are available on request for [Business](https://segment.com/pricing/) customers.
+Segment increases deliverability to destinations in two ways: [retries](#retries) and [replays](/docs/guides/what-is-replay/). Retries happen automatically for all customers, while replays are available on request for [Business](https://segment.com/pricing/) customers.
 
 ### Retries
 

src/connections/sources/about-cloud-sources.md

@@ -1,8 +1,8 @@
 ---
 title: All about Cloud Sources
 redirect_from:
-  - 'connections/sources/what-are-cloud-sources'
-  - 'connections/sources/cloud-source-data'
+  - '/connections/sources/what-are-cloud-sources/'
+  - '/connections/sources/cloud-source-data/'
 ---
 
 Cloud-App Sources (often shortened to Cloud Sources) allow you to pull in data from third-party tools so you can use it in Segment. There are two types of Cloud Apps: **Object** and **Event** sources.

src/connections/sources/catalog/libraries/mobile/android/v1/quickstart.md

@@ -183,4 +183,4 @@ Once you've added a few `track` calls, **you're done!** You successfully instrum
 
 ## What's Next?
 
-We just walked through the quickest way to get started with Segment using Analytics for Android. You might also want to check out our full [Analytics for Android reference](/docs/connections/sources/catalog/libraries/mobile/android/) to see what else is possible, or read about the [Tracking API methods](docs/connections/sources/catalog/libraries/server/http-api/) to get a sense for the bigger picture.
+We just walked through the quickest way to get started with Segment using Analytics for Android. You might also want to check out our full [Analytics for Android reference](/docs/connections/sources/catalog/libraries/mobile/android/) to see what else is possible, or read about the [Tracking API methods](/docs/connections/sources/catalog/libraries/server/http-api/) to get a sense for the bigger picture.

src/connections/sources/catalog/libraries/mobile/xamarin/index.md

@@ -17,9 +17,10 @@ Our [Xamarin](http://xamarin.com/) Portable Class Library ([PCL](http://develope
 
 The library issues requests that hit our servers, and then we route your data to any analytics service you enable on our destinations page. This library is open-source, so you can [check it out on Github](https://github.com/segmentio/Analytics.Xamarin).
 
-**Note:** Since Xamarin requires our library to be portable to different builds, we can only enable server-side destinations, as opposed to bundling select native SDKs like we do for iOS and Android. Look for the "Server" icon when selecting destinations. For tools for which we offer both bundled and server-side destinations, like Mixpanel, Amplitude, and Google Analytics, our Xamarin library will only be able to leverage their server-side functionality. [Read this help article for more information](https://help.segment.com/hc/en-us/articles/204892879).
+**Note:** Since Xamarin requires our library to be portable to different builds, we can only enable server-side destinations, as opposed to bundling select native SDKs like we do for iOS and Android. Look for the "Server" icon when selecting destinations. For tools for which we offer both bundled and server-side destinations, like Mixpanel, Amplitude, and Google Analytics, our Xamarin library will only be able to leverage their server-side functionality.
 
 ## Getting Started
+
 Clone `Analytics.Xamarin` from [Github](https://github.com/segmentio/Analytics.Xamarin)...
 
 ```bash

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

@@ -1,6 +1,9 @@
 ---
 title: Analytics.js (Javascript) Source
-redirect_from: '/connections/sources/catalog/libraries/website/analytics.js/'
+redirect_from:
+  - '/connections/sources/catalog/libraries/website/analytics.js/'
+  - '/sources/website/javascript/'
+  - '/sources/website/analytics.js/'
 ---
 
 Analytics.js, Segment's Javascript source, makes it simple to send your data to any tool without having to learn, test or implement a new API every time.

src/connections/sources/catalog/libraries/website/plugins/youtube/index.md

@@ -16,7 +16,7 @@ To begin, you'll need to generate an API Key for the Segment Youtube plugin, whi
 
 Enable a new plugin by navigating to the settings for your Source, and clicking  **Plugins**. You can enable the YouTube plugin from this menu.
 
-![the plugins setting screen](docs/connections/sources/plugins-enable.png)
+![the plugins setting screen](/docs/connections/sources/plugins-enable.png)
 
 **Note: At this time, only Javascript sources support plugins.**
 

src/connections/spec/ecommerce-tracking-plan.md

@@ -1,6 +1,9 @@
 ---
 title: Ecommerce Tracking Plans
-redirect_from: '/protcols/data-quality/ecommerce-tracking-plans/'
+redirect_from:
+  - '/protcols/data-quality/ecommerce-tracking-plans/'
+  - '/protcols/ecommerce-tracking-plan/'
+  - '/guides/sources/how-to-implement-an-ecommerce-tracking-plan/'
 ---
 
 When tracking your data, it's important to set yourself up for success. E-commerce and retail companies want to use their data to understand why some customers fall out of their funnels or why customers become repeat buyers. They want to understand the important lifecycle events that lead up to the sale of a physical item, so they can, for example, test whether personalized shopping experiences yield higher conversions, or build a multi-channel cart abandonment campaign. But first, they need to make sure those lifecycle events are being captured in their datasets.

src/getting-started/04-full-install.md

@@ -67,7 +67,7 @@ Consider using Identify and traits when:
 
 ## How to Call Identify
 
-You can call Identify from any of Segment’s device-based or server-based libraries, including [Javascript](/docs/connections/sources/catalog/libraries/website/javascript/), [iOS](/docs/connections/sources/catalog/mobile/ios), [Android](/docs/connections/sources/catalog/mobile/android), [Ruby](/docs/connections/sources/catalog/libraries/server/ruby/), and [Python](/docs/connections/sources/catalog/libraries/server/python/).
+You can call Identify from any of Segment’s device-based or server-based libraries, including [Javascript](/docs/connections/sources/catalog/libraries/website/javascript/), [iOS](/docs/connections/sources/catalog/libraries/mobile/ios), [Android](/docs/connections/sources/catalog/libraries/mobile/android), [Ruby](/docs/connections/sources/catalog/libraries/server/ruby/), and [Python](/docs/connections/sources/catalog/libraries/server/python/).
 
 Here are two examples of calling identify from two different libraries:
 

src/guides/how-to-guides/cross-channel-tracking.md

@@ -171,7 +171,7 @@ If your store allows user registration and users are logged in when they shop on
 
 This works by using a `userId` instead of an `anonymousId` to track key events and where they occur. This `userId` serves as the primary key in your downstream tools and data warehouse, allowing you to join all of her anonymous activities with her logged in ones. You also can get a complete picture of where she is and what device she is on, while she is using your apps or website.
 
-[Learn more about pulling the entire user journey for a single user given a userId.](https://segment.com/docs/guides/sources/join-user-profiles/)
+[Learn more about pulling the entire user journey for a single user given a userId.](https://segment.com/docs/guides/how-to-guides/join-user-profiles/)
 
 Unfortunately, tracking the same user across devices only works if she logs into each device. Anonymous browsing in each distinct "experience" (e.g. mobile safari, native iPhone, browser on laptop) generates its own unique `anonymousId` . Each `anonymousId` is limited to the scope of that browser or app, only measuring activities in those sessions. It's not until the user logs in when the `userId` is generated (if she is registering for a new account) or the `userId` is retrieved from your database, and then mapped to the `anonymousId` of that session. Segment will keep a table of `anonymousId` s mapped to a single `userId`so you can analyze a user's activity across multiple devices.