round 3

lychee.toml

@@ -50,7 +50,7 @@ headers = []
 ### Exclusions
 ###
 # Exclude URLs from checking (supports regex)
-exclude = ['https://segment.zendesk.com','(example-service)','(redacted)','(foo)','http://dl.bintray.com/swrve-inc/android','https://ajs.cd.segment.com/analytics.js/v1/','http://0.0.0.0:4000','https://api.segment.io/v1/', 'https://segment.com/docs/assets/docs.bundle.js','https://www.linkedin.com', 'https://segment.com/jobs/', 'https://segment.com/press/', 'https://github.com/segmentio', 'https://unpkg.com/@segment/[email protected]/standalone/consent-manager.js', '(segment.com)', '(segmentapis.com)', '(example.com)', '(schema.org)','(maxcdn)', '(your-org-name)', '(mywebsite)']
+exclude = ['(acme.com)','(webhooks.company.com)','(your-webhook-url)','https://segment.zendesk.com','(example-service)','(redacted)','(foo)','http://dl.bintray.com/swrve-inc/android','https://ajs.cd.segment.com/analytics.js/v1/','http://0.0.0.0:4000','https://api.segment.io/v1/', 'https://segment.com/docs/assets/docs.bundle.js','https://www.linkedin.com', 'https://segment.com/jobs/', 'https://segment.com/press/', 'https://github.com/segmentio', 'https://unpkg.com/@segment/[email protected]/standalone/consent-manager.js', '(segment.com)', '(segmentapis.com)', '(example.com)', '(schema.org)','(maxcdn)', '(your-org-name)', '(mywebsite)']
 
 # Exclude URLs contained in a file from checking
 exclude_file = []

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

@@ -19,7 +19,7 @@ This destination is maintained by ActiveCampaign. For any issues with the destin
 
 ## Page
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
 
 ```js
 analytics.page();
@@ -32,7 +32,7 @@ When you call `page`, we will send that event to ActiveCampaign as a `site track
 
 ## Identify
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
 
 ```js
 analytics.identify('ze8rt1u89', {
@@ -119,7 +119,7 @@ analytics.identify('ze8rt1u89', {
 ```
 ## Track
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
 
 ```js
 analytics.track('Clicked a button', {

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

@@ -21,7 +21,7 @@ This destination is maintained by AdQuick. For any issues with the destination,
 
 ## Page
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
 
 ```
 analytics.page()
@@ -32,7 +32,7 @@ Page calls will be sent to AdQuick as a `pageview`.
 
 ## Screen
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. An example call would look like:
 
 ```
 [[SEGAnalytics sharedAnalytics] screen:@"Home"];
@@ -43,7 +43,7 @@ Screen calls will be sent to AdQuick as a `screenview`.
 
 ## Identify
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
 
 ```
 analytics.identify('userId123', {
@@ -56,7 +56,7 @@ Identify calls will be sent to AdQuick as an `identify` event.
 
 ## Track
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
 
 ```
 analytics.track('Clicked Login Button')

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

@@ -19,26 +19,26 @@ title: AdRoll Destination
 
 ## Page
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
 ```javascript
 analytics.page()
 ```
 _**NOTE:** The `page` call **must** be made on a page for any `identify` or `track` events to be sent to AdRoll. Our Analytics.js snippet includes a `page` call by default so you should be fine, unless you've manually removed the page call from your Analytics.js snippet._
 
 ## Identify
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
 ```javascript
 analytics.identify('123', {
   email: '[email protected]'
 });
 ```
-Set a `userId` using the `identify` call which will then be passed it to AdRoll each time a [`track`](https://segment.com/docs/connections/destinations/catalog/adroll/#track) call is made. If you pass an `email` trait, we'll send that to AdRoll by setting `window.adroll_email` to that value.
+Set a `userId` using the `identify` call which will then be passed it to AdRoll each time a [`track`](/docs/connections/destinations/catalog/adroll/#track) call is made. If you pass an `email` trait, we'll send that to AdRoll by setting `window.adroll_email` to that value.
 
 
 ## Track
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
 ```javascript
 analytics.track('Sign-up Form Completed');
 ```
@@ -88,7 +88,7 @@ analytics.track('Vewed Product', {
 
 ### **Legacy:** Named Segments
 
-Prior to rolling out Segment ID's, AdRoll allowed "named segments". If your account was created prior to 2015, then the track events you send from the browser using our [`analytics.track`](https://segment.com/docs/connections/destinations/catalog/adroll/#track) method will be passed on to AdRoll as `adroll_segments` with the segment being the snake-cased event name.
+Prior to rolling out Segment ID's, AdRoll allowed "named segments". If your account was created prior to 2015, then the track events you send from the browser using our [`analytics.track`](/docs/connections/destinations/catalog/adroll/#track) method will be passed on to AdRoll as `adroll_segments` with the segment being the snake-cased event name.
 
 ## Troubleshooting
 

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

@@ -17,12 +17,12 @@ This destination is maintained by Adtriba. For any issues with the destination,
 
 1. From the Segment web app, click **Catalog**.
 2. Search for "Adtriba" in the Catalog, select it, and choose which of your sources to connect the destination to.
-3. Enter the "Project Tracker ID / API Key" into your Segment Settings UI which you can find from your [Adtriba dashboard](https://console.adtriba.com).
+3. Enter the "Project Tracker ID / API Key" into your Segment Settings UI which you can find from the Adtriba dashboard.
 4. Validate the forwarded events by checking the Tracking Report under the "Tracking" tab.
 
 ## Page
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
 
 ```
 analytics.page()
@@ -33,7 +33,7 @@ Page calls will be sent to Adtriba as a `pageview`.
 
 ## Identify
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
 
 ```
 analytics.identify('userId123', {
@@ -46,7 +46,7 @@ Identify calls will be sent to Adtriba as an `identify` event.
 
 ## Track
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
 
 ```
 analytics.track('Conversion', {
@@ -58,4 +58,4 @@ analytics.track('Conversion', {
 
 Track calls will be sent to Adtriba as a `track` event.
 
-Trigger additional events by using [Semantic Events](https://segment.com/docs/connections/spec/semantic/) in order to enrich the Adtriba machine learning process.
+Trigger additional events by using [Semantic Events](/docs/connections/spec/semantic/) in order to enrich the Adtriba machine learning process.

src/connections/destinations/catalog/algolia-insights/index.md

@@ -32,9 +32,9 @@ You can read more about how to send Algolia-related data to Segment from [the do
 
 ## Track
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does.
+If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does.
 
-Algolia supports the following six events from Segment's [Ecommerce Spec](https://segment.com/docs/connections/spec/ecommerce/v2/).
+Algolia supports the following six events from Segment's [Ecommerce Spec](/docs/connections/spec/ecommerce/v2/).
 
 <table>
   <tr>

src/connections/destinations/catalog/amazon-eventbridge/index.md

@@ -20,13 +20,13 @@ The Event Source will be denoted by your Segment Source ID, which you can find i
 We'll forward all the messages in the source (pending any Destination Filters you've enabled) to the Segment Partner Event Source we create for you in EventBridge.
 
 ## Page
-If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
 ```javascript
   analytics.page();
 ```
 
 ## Identify
-If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example identify call is shown below:
+If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example identify call is shown below:
 ```javascript
 analytics.identify('97980cfea0085', {
   email: '[email protected]',
@@ -35,7 +35,7 @@ analytics.identify('97980cfea0085', {
 ```
 
 ## Track
-If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example identify call is shown below:
+If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example identify call is shown below:
 
 ```javascript
 analytics.track("User Registered", {

src/connections/destinations/catalog/amazon-kinesis-firehose/index.md

@@ -49,13 +49,13 @@ To get started:
     2. Search and select the **Amazon Kinesis Firehose** destination and enter details for [these settings options](#settings).
 
 ## Page
-Take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like:
+Take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
 ```javascript
   analytics.page();
 ```
 
 ## Identify
-Take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example identify call is shown below:
+Take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example identify call is shown below:
 ```javascript
 analytics.identify('97980cfea0085', {
   email: '[email protected]',
@@ -64,7 +64,7 @@ analytics.identify('97980cfea0085', {
 ```
 
 ## Track
-Take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example identify call is shown below:
+Take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example identify call is shown below:
 
 ```js
 analytics.track("User Registered", {
@@ -116,7 +116,7 @@ firehose.putRecord({
 Segment appends a newline character to each record to allow for easy downstream parsing.
 
 ## Group
-Take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example group call is shown below:
+Take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example group call is shown below:
 
 ```js
 analytics.group("0e8c78ea9d9dsasahjg", {

src/connections/destinations/catalog/amazon-kinesis/index.md

@@ -51,14 +51,14 @@ To get started:
    * **NOTE:** For security purposes, Segment sets your Workspace ID as your Secret ID. If you’re using a Secret ID different from your Workspace ID, reach out to our support team so they can change it to make your account more secure.
 
 ## Page
-If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like:
 
 ```js
   analytics.page();
 ```
 
 ## Identify
-If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does.  An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does.  An example call would look like:
 
 ```js
 analytics.identify('97980cfea0085', {
@@ -68,7 +68,7 @@ analytics.identify('97980cfea0085', {
 ```
 
 ## Track
-If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like:
+If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like:
 
 ```js
 analytics.track("User Registered", {
@@ -105,7 +105,7 @@ Segment uses the the `userId || anonymousId` as the `PartitionKey`. The partitio
 > **NOTE:** The JSON payload is base64 stringified.
 
 ## Group
-If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does.
+If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does.
 
 An example group call is shown below:
 ```js

src/connections/destinations/catalog/amazon-lambda/index.md

@@ -193,7 +193,7 @@ This setting controls the [Log Type](https://docs.aws.amazon.com/lambda/latest/d
 Due to how our event delivery system, [Centrifuge](https://segment.com/blog/introducing-centrifuge/), works, your Lambda can't take more than 5 seconds to run per message. If you're consistently running into timeout issues, you should consult the [AWS Lambda docs](https://docs.aws.amazon.com/lambda/index.html#lang/en_us), as well as docs for your language of choice, for tips on optimizing performance.
 
 **Handling Common Errors**
-You can find delivery logs in Destination > [Event Delivery](https://segment.com/docs/guides/destinations/how-do-i-check-if-data-is-successfully-being-delivered-to-my-destination/).
+You can find delivery logs in Destination > [Event Delivery](/docs/guides/destinations/how-do-i-check-if-data-is-successfully-being-delivered-to-my-destination/).
 
 Here are some common errors you may come across and how to resolve:
 

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

@@ -22,7 +22,7 @@ Since Ambassador only records specific events and user data, events and users ma
 
 ## Identify
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does.
+If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does.
 
 For Ambassador it takes the unique `userId` of a user and a specific set of traits. All supported `traits` are listed in the example below:
 
@@ -47,7 +47,7 @@ _**NOTE:** You can optionally use the URL campaign map to enroll the user as an
 
 ## Track
 
-If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does.
+If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does.
 
 For Ambassador `track` events will be recorded as a conversion if the Segment event name is mapped to a campaign in your Ambassador destination settings in the Segment UI. All supported `properties` are listed in the example below: