fixed some broken links

Author: markzegarelli

src/_release_notes/2020-09-08-data-lakes.md

@@ -16,7 +16,7 @@ doc_links:
     url: "/docs/connections/storage/data-lakes/"
   - 
     title: Set Up Segment Data Lakes
-    url: "docs/connections/storage/catalog/data-lakes"
+    url: "/docs/connections/storage/catalog/data-lakes"
 # images:
 #   -
 #     path: images/release-notes/identity-onboarding-1.png

src/connections/destinations/catalog/facebook-pixel-server-side/index.md

@@ -78,7 +78,7 @@ This approach provides a redundancy that ensures maximum signal reliability. Eve
 For this option to work best, you must pass the same `external_id` from both the browser and the server sources.
 To do this, go to your Facebook Pixel destination settings in Segment, and enable **Use UserId or Anonymous Id as External Id**. By default the Facebook Conversions API destination uses the `userId` (or `anonymousId` if not present) to set the External Id, so when you set up Facebook Pixel to use the same settings, Facebook can then match the users.
 
-You can also increase the match rate for events from a server source by sending [user traits in the context object of the track events](/#default-mappings-to-facebook-properties). You can also collect other fields from the browser, such as `userAgent`, `ip` address, and [Facebook's parameters (fbp, fbc)](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/fbp-and-fbc) and pass them to the server, and manually add them to the events.
+You can also increase the match rate for events from a server source by sending [user traits in the context object of the track events](#default-mappings-to-facebook-properties). You can also collect other fields from the browser, such as `userAgent`, `ip` address, and [Facebook's parameters (fbp, fbc)](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/fbp-and-fbc) and pass them to the server, and manually add them to the events.
 
 #### Deduplication considerations
 
@@ -92,7 +92,7 @@ Use this approach if you want to separate tracking events completed on a user's
 
 For this option to work best, the same `external_id` needs to be passed from the browser and from the server. To easily achieve this go to your Segment destination settings for Facebook Pixel and toggle on the setting called **Use UserId or Anonymous Id as External Id**. The Facebook Conversions API destination uses the userId (or anonymousId if not present) to set the External Id by default. Therefore enabling this on Facebook Pixel will allow Facebook to match the users.
 
-You can also increase the match rate for events from a server source by sending [user traits in the context object of the track events](/#default-mappings-to-facebook-properties). You can also collect other fields from the browser, such as `userAgent`, `ip` address, and [Facebook's parameters (fbp, fbc)](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/fbp-and-fbc) and pass them to the server, and manually add them to the events.
+You can also increase the match rate for events from a server source by sending [user traits in the context object of the track events](#default-mappings-to-facebook-properties). You can also collect other fields from the browser, such as `userAgent`, `ip` address, and [Facebook's parameters (fbp, fbc)](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/fbp-and-fbc) and pass them to the server, and manually add them to the events.
 
 #### Deduplication considerations
 
@@ -106,7 +106,7 @@ Use this approach if you don't want to track users from the browser with Faceboo
 
 If you use Facebook Conversions API as a stand-alone without certain data fields collected from the browser, the match rate might not be as high as if you included them.
 
-You can also increase the match rate for events from a server source by sending [user traits in the context object of the track events](/#default-mappings-to-facebook-properties). You can also collect other fields from the browser, such as `userAgent`, `ip` address, and [Facebook's parameters (fbp, fbc)](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/fbp-and-fbc) and pass them to the server, and manually add them to the events.
+You can also increase the match rate for events from a server source by sending [user traits in the context object of the track events](#default-mappings-to-facebook-properties). You can also collect other fields from the browser, such as `userAgent`, `ip` address, and [Facebook's parameters (fbp, fbc)](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/fbp-and-fbc) and pass them to the server, and manually add them to the events.
 
 
 #### Deduplication considerations

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

@@ -22,7 +22,7 @@ Different Measurement IDs begin with different prefixes, which indicate which Go
 | UA     | Your global site tag is controlled by Google Analytics. The ID is your Google Analytics Measurement ID. To find the property associated with this ID, use the [account search feature](https://support.google.com/analytics/answer/6100731) in Google Analytics. If the property does not appear, you probably do not have access to it. | [Google Analytics](/docs/connections/destinations/catalog/google-analytics/): Configure ID > Measurement ID           |
 | G      | Your global site tag is controlled by Google Analytics 4 (GA4). The ID is your Google Analytics Measurement ID.       | [Google Analytics](/docs/connections/destinations/catalog/google-analytics/): Configure ID > App + Web Measurement ID |
 | AW     | Your global site tag is controlled by Google Ads. The numeric string following the AW prefix is your Google Ads Conversion ID.        | [Google Ads](/docs/connections/destinations/catalog/google-ads-gtag/): Configure ID > Conversion ID                  |
-| DC     | Your global site tag is controlled by a Floodlight tag. The numeric string following DC is your Advertiser ID.       | [Floodlight](docs/connections/destinations/catalog/doubleclick-floodlight/): Configure ID > App + Web Measurement ID       |
+| DC     | Your global site tag is controlled by a Floodlight tag. The numeric string following DC is your Advertiser ID.       | [Floodlight](/docs/connections/destinations/catalog/doubleclick-floodlight/): Configure ID > App + Web Measurement ID       |
 | other  | Your global site tag is controlled by a different Google product or may be implemented incorrectly. Use the [Tag Assistant extension](https://support.google.com/tagassistant/answer/2947093) for Google Chrome to verify.      | n/a      |
 
 

src/connections/functions/destination-functions.md

@@ -194,7 +194,7 @@ If your function fails, you can check the error details and logs in the **Output
 > warning ""
 > Batch handling for Functions is currently available as an early access beta release. By enabling batch handlers for your function, you acknowledge that your use of batch handlers is subject to [Segment’s Beta Terms and Conditions](https://segment.com/legal/first-access-beta-preview), or the applicable terms governing Beta Releases found in your subscription agreement with Segment.
 >
-> If you notice any bugs or have any general feedback on this new feature, contact [[email protected]]([email protected]).
+> If you notice any bugs or have any general feedback on this new feature, contact [[email protected]](mailto:[email protected]).
 
 Batch handlers are an extension of destination functions. When you define an `onBatch` handler alongside the handler functions for single events (for example: `onTrack` or `onIdentity`), you're telling Segment that the destination function can accept and handle batches of events.
 

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

@@ -612,7 +612,7 @@ There are two ways to send data to your analytics services through this library:
 
 #### Cloud-Mode in Android
 
-When a destination is enabled for your Android source from the Segment web app, but you haven't packaged its SDK with your app, requests go through the Segment REST API, and are routed to the destination service's API as [described here](/docs/connections/destinations/#connection-modes). Most, but not all destinations offer a cloud-based connection mode, so it's a good idea to [check for destinations that you might _need_ to package](/docs/util/cmodes-compare/).
+When a destination is enabled for your Android source from the Segment web app, but you haven't packaged its SDK with your app, requests go through the Segment REST API, and are routed to the destination service's API as [described here](/docs/connections/destinations/#connection-modes). Most, but not all destinations offer a cloud-based connection mode, so it's a good idea to [check for destinations that you might _need_ to package](/docs/connections/destinations/cmodes-compare).
 
 #### Packaging device-mode destination SDKs
 

src/connections/sources/catalog/libraries/mobile/android/troubleshooting.md

@@ -18,8 +18,8 @@ strat: android
 1. Check that the destination is actually enabled in the Segment app.
 2. Check that you entered your credentials for the destination correctly in the Segment app, and that you added them for the correct Source in the correct Workspace.
 3. Make sure the destination can accept the data that you're sending:
-   - Does the [destination support device-mode or cloud-mode support](/docs/utils/cmodes-compare/)? Confirm you are sending using the correct connection mode.
-   - Does the destination [accept the type of call you are sending](/docs/utils/methods-compare/)? Not all destinations accept all calls: page, track, etc.
+   - Does the [destination support device-mode or cloud-mode support](/docs/connections/destinations/cmodes-compare/)? Confirm you are sending using the correct connection mode.
+   - Does the destination [accept the type of call you are sending](/docs/connections/destinations/methods-compare/)? Not all destinations accept all calls: page, track, etc.
 
 
 If you still don't see data getting to your destination, continue debugging based on the type of connection mode, using the sections below.

src/connections/sources/catalog/libraries/website/shopify-littledata/index.md

@@ -19,7 +19,7 @@ Here's an architecture diagram that shows how the Littledata app mediates data f
 ![](images/littledata_arch.png)
 
 > warning "Note"
-> This integration is maintained by Littledata _and is not supported by Segment directly_. The Littledata app has been reviewed by the Segment team for conformance with Segment's [E-Commerce Spec](/docs/connections/spec/e-commerce/v2/), and is the recommended way of using Segment with Shopify. However, it does require a paid subscription with Littledata, who mediates the connection between Shopify and Segment. [Contact the Littledata Support team](mailto:[email protected]) with any questions.
+> This integration is maintained by Littledata _and is not supported by Segment directly_. The Littledata app has been reviewed by the Segment team for conformance with Segment's [E-Commerce Spec](/docs/connections/spec/ecommerce/v2/), and is the recommended way of using Segment with Shopify. However, it does require a paid subscription with Littledata, who mediates the connection between Shopify and Segment. [Contact the Littledata Support team](mailto:[email protected]) with any questions.
 
 ## Getting Started
 

src/connections/spec/best-practices-identify.md

@@ -56,7 +56,7 @@ The illustration below shows a timeline with a user’s interactions on a websit
 
 <!-- https://www.figma.com/file/Gc53MamYsKZBg3IUduunc5/identity-best-practices?node-id=1%3A3 -->
 
-When the user first visits a page, Analytics.js automatically assigns the user an `anonymousId` and saves it to the user's local storage. As the user interacts with the site, for example clicking around to different pages, Analytics.js includes this `anonymousId` and some [contextual information](/docs/spec/common#context) with each Page and Track call. The contextual information might be the user’s [IP address, browser, and more](/docs/connections/spec/common#context-fields-automatically-collected).
+When the user first visits a page, Analytics.js automatically assigns the user an `anonymousId` and saves it to the user's local storage. As the user interacts with the site, for example clicking around to different pages, Analytics.js includes this `anonymousId` and some [contextual information](/docs/connections/spec/common#context) with each Page and Track call. The contextual information might be the user’s [IP address, browser, and more](/docs/connections/spec/common#context-fields-automatically-collected).
 
 When a user signs up to create an account on the website, the `.identify(UID)` and `.track(“Signed Up”)` events fire, in that order. You pull the `userId` unique to the user from your systems, and send it to the Segment library so you can label that user’s later events with their ID. The later Track call (“Signed Up”) contains both the `userId` *and* the automatically-collected `anonymousId` for the user, and any other information you capture about them -  such as their first name, last name, and email address.
 

src/segment-app/iam/membership.md

@@ -96,6 +96,6 @@ Segment does not support programmatic de-provisioning at this time. However, if
 
 ## Request Access
 
-If you are a [workspace member](/segment-app/iam/roles), you might encounter a section of the Segment App that you do not have access to view. If you need expanded permissions, you can request access directly in the Segment App. Once submitted, Access requests are sent to all workspace owners by email.
+If you are a [workspace member](/docs/segment-app/iam/roles), you might encounter a section of the Segment App that you do not have access to view. If you need expanded permissions, you can request access directly in the Segment App. Once submitted, Access requests are sent to all workspace owners by email.
 
 To review an access request, workspace owners click the link in the access request email to go to their workspace's Access Management Settings. The requestor's access request message appears on the Segment Access Management page, and the workspace owner can adjust the user's permissions. The access request message disappears after the permissions are updated.

src/segment-app/iam/roles.md

@@ -12,7 +12,7 @@ All Segment workspaces have the following roles, regardless of account type.
   Owners have full read and edit access to everything in the workspace, including sources, destinations, add-on products, and settings. Owners have full edit access to all team permissions.
 
 - **Workspace Member**
-Members inherit custom permissions based on [individual roles](/docs/segment-app/iam/roles/##business-tier-roles) assigned.
+Members inherit custom permissions based on [individual roles](#business-tier-roles) assigned.
 
 - **Source admin**
   Source admins have edit access to assigned source(s), to the settings for that source, to any connected streaming destinations, schema, and live data from the source in the [debugger](/docs/connections/sources/debugger/). A user with the Source Admin role can be granted access to either all current and future Sources, or a specific list of Sources, or (if you are on a Business plan) to Sources with a specific Label.