round 2

Author: markzegarelli

lychee.toml

@@ -50,7 +50,7 @@ headers = []
 ### Exclusions
 ###
 # Exclude URLs from checking (supports regex)
-exclude = ['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 = ['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/adroll/index.md

@@ -3,9 +3,7 @@ rewrite: true
 title: AdRoll Destination
 ---
 
-[AdRoll](https://developers.adroll.com/) is a retargeting network that allows you to show ads to visitors who've landed on your site while browsing the web. The AdRoll Destination is open-source. You can browse the code on [GitHub](https://github.com/segment-integrations/analytics.js-integration-adroll).
-
-This document was last updated on January 26, 2018. If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, [let us know](https://segment.com/help/contact)!
+[AdRoll](https://adroll.com/) is a retargeting network that allows you to show ads to visitors who've landed on your site while browsing the web. The AdRoll Destination is open-source. You can browse the code on [GitHub](https://github.com/segment-integrations/analytics.js-integration-adroll).
 
 ## Getting Started
 

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

@@ -152,7 +152,7 @@ Segment will automatically trigger an `Install Attributed` event if you have **t
 ### Server
 If you are tracking events server-side, AppsFlyer can still send attribution postbacks but you will need to configure this functionality in your AppsFlyer account. To enable this, navigate to your AppsFlyer app and on the sidebar of the main screen click on **Integrated Partners** and search for Segment. You will be prompted with a couple of configuration options and asked to input your Segment Write Key. Once enabled, successfully attributed app installs will begin showing up as `Install Attributed` events similar to the client side behavior documented above.
 
-If you are sending in the attribution data yourself, for iOS be sure the following properties are sent in within the campaign object on the `Install Attributed` or `Application Opened` event so Appsflyer can correctly attribute it as an Apple Search Ad event. These values should be returned by the [Apple Search Ads API](https://searchads.apple.com/advanced/help/measure-results/#attribution-api):
+If you are sending in the attribution data yourself, for iOS be sure the following properties are sent in within the campaign object on the `Install Attributed` or `Application Opened` event so Appsflyer can correctly attribute it as an Apple Search Ad event. These values should be returned by the [Apple Search Ads API](https://searchads.apple.com/help/reporting/0028-apple-ads-attribution-api):
 
 ```
 "campaign": {

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

@@ -23,11 +23,11 @@ When you enable Boomtrain in the Segment web app, your changes appear in the Seg
 
 ## Identify
 
-When you call [`identify`](/docs/connections/spec/identify/) on analytics.js, we call `person.set` on the Boomtrain Javascript Library with the `traits` object. A `userId` must be specified.  For additional details about the Boomtrain `person.set` methods see [this article](https://boomtrain.readme.io/docs/personset-attributes-callback) on the Boomtrain Developer Documentation.
+When you call [`identify`](/docs/connections/spec/identify/) on analytics.js, we call `person.set` on the Boomtrain Javascript Library with the `traits` object. A `userId` must be specified.  For additional details about the Boomtrain `person.set` methods see [this article](https://boomtrain.readme.io/docs/set) on the Boomtrain Developer Documentation.
 
 ## Track
 
-When you call [`track`](/docs/connections/spec/track/), we will send the `event` you specify to the `track` method on the Boomtrain Javascript library, along with the properties you provide.  For additional details about the Boomtrain `track` method see [this article](https://boomtrain.readme.io/docs/track-an-activity-1) on the Boomtrain Developer Documentation.
+When you call [`track`](/docs/connections/spec/track/), we will send the `event` you specify to the `track` method on the Boomtrain Javascript library, along with the properties you provide. 
 
 ## Settings
 

src/connections/destinations/catalog/new-relic/index.md

@@ -2,7 +2,7 @@
 rewrite: true
 title: New Relic Destination
 ---
-[New Relic](https://newrelic.com/insights) enables you to better understand, using their real-time analytics, the end-to-end business impact of your software performance.
+[New Relic](https://newrelic.com/) enables you to better understand, using their real-time analytics, the end-to-end business impact of your software performance.
 
 This document was last updated on August 29, 2018. If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, [let us know](https://segment.com/help/contact)!
 

src/connections/destinations/catalog/perfect-audience/index.md

@@ -24,7 +24,7 @@ Perfect Audience is only supported on the client-side.
 
 ## 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("My Custom Event", {
@@ -37,12 +37,9 @@ When you call `track` on analytics.js, we call Perfect Audience's `track` with t
 
 Perfect Audience requires that you define your goals ahead of time in their interface. If that hasn't happened, then they don't track the events.
 
-[Here's their video of how to set that up](http://support.perfectaudience.com/knowledgebase/articles/234037-how-to-create-and-track-conversion-goals-with-perf) - you'll need to match event names between Perfect Audience and your Segment track calls.
-
-
 ### Order Completed
 
-If you're using our [ecommerce spec](/docs/connections/spec/ecommerce/v2/) and passing the `Order Completed` event the `orderId` and `total` will be passsed along to Perfect Audience.
+If you're using our [ecommerce spec](/docs/connections/spec/ecommerce/v2/) and passing the `Order Completed` event the `orderId` and `total` will be passed along to Perfect Audience.
 
 ## Troubleshooting
 

src/connections/destinations/catalog/quora-conversion-pixel/index.md

@@ -3,7 +3,7 @@ rewrite: true
 title: Quora Conversion Pixel Destination
 ---
 
-[Quora Conversion Pixel](https://www.quora.com/business) enables you to attribute downstream user actions on your website to your ad campaigns running on Quora.com. Our client-side Destination code is open source. You can browse the code in GitHub [here](https://github.com/segment-integrations/analytics.js-integration-quora-conversion-pixel).
+[Quora Conversion Pixel](https://www.quora.com/business) enables you to attribute downstream user actions on your website to your ad campaigns running on Quora.com. Our client-side Destination code is open source. You can browse the code in GitHub [here](https://github.com/segmentio/analytics.js-integrations/tree/master/integrations/quora-conversion-pixel).
 
 This document was last updated on June 15th, 2018. If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, [let us know](https://segment.com/help/contact).
 

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

@@ -43,7 +43,7 @@ _NOTE_: You can find your account's endpoint by simply going to your Oracle Resp
 
 4. Enter the name of your default **Profile List** where you would like to store your `.identify()` calls. Again, this can be overriden using destination specific options on a per-call basis as seen [here](#overriding-default-folder-and-list-names).
 
-5. Choose whether you'd like to set your **Default Permission Status** to be `OPTIN` or `OPTOUT`. Unless configured otherwise, the default will be `OPTOUT`. If you are unsure the implications of this settings, you can read more about it [here](https://policy3.responsys.net/permission.htm).
+5. Choose whether you'd like to set your **Default Permission Status** to be `OPTIN` or `OPTOUT`. Unless configured otherwise, the default will be `OPTOUT`.
 
 Once you have entered these required settings, you are ready to integrate your Oracle Responsys account through the Segment platform!
 

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

@@ -19,11 +19,11 @@ This destination is maintained by Richpanel. For any issues with the destination
 4. In your Richpanel account, go to Data Sources > Integrations and install the Segment Connector.
 5. Enter the "API Key" into your Segment Settings UI which you can find from your [Richpanel data sources](https://app.richpanel.com/connectors/my/list).
 
-**NOTE**: Richpanel accepts anonymous users, or [Visitors](http://event.richpanel.com/#/customers/understanding-customers), but they will not appear in the Richpanel Customer Section UI unless the customer is first identified using an `identify` call or customer actvity through Richpanel Channels, thereby becoming a [Customer](http://event.richpanel.com/#/customers/understanding-customers).
+**NOTE**: Richpanel accepts anonymous users, or Visitors, but they will not appear in the Richpanel Customer Section UI unless the customer is first identified using an `identify` call or customer activity through Richpanel Channels, thereby becoming a Customer.
 
 ## 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('userId123', {
@@ -44,11 +44,10 @@ The basic properties to identify and create a user are:
 
 `uid` is a *required* field; `email`, `firstName`, and `lastName` are optional, but highly recommended.
 
-See [Richpanel's User Properties](http://event.richpanel.com/#/properties) and [Richpanel's Events](http://event.richpanel.com/#/events?id=attribute-glossary) for more details.
 
 ## 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('Pricing', {
@@ -64,7 +63,7 @@ If no `richpanel_session_id` is supplied, Richpanel will automatically generate
 
 ## 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 Login Button', {
@@ -74,4 +73,4 @@ analytics.track('Clicked Login Button', {
 
 Track calls are sent to Richpanel as a `track` event. `track` calls can only update `email` traits, but do not create them.
 
-**NOTE**: Richpanel accepts all events listed in [Segment's Specs](https://segment.com/docs/connections/spec/ecommerce/v2/). For events like Order Updated, Order Cancelled, and Order Refunded, we recommend that you pass an `order_status` property.
+**NOTE**: Richpanel accepts all events listed in [Segment's Specs](/docs/connections/spec/ecommerce/v2/). For events like Order Updated, Order Cancelled, and Order Refunded, we recommend that you pass an `order_status` property.

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

@@ -16,12 +16,12 @@ This destination is maintained by ScopeAI. For any issues with the destination,
 2. Search for "ScopeAI" in the Catalog, select it, and choose which of your sources to connect the destination to.
 3. In the Segment Settings UI under "API Key" place the Segment token that can be seen after clicking "Show Token" in the panel of the Segment integration you've  created in the [ScopeAI integrations page](https://www.getscopeai.com/integrations). If you haven't yet created a Segment integration on the ScopeAI app, follow these [instructions](http://help.getscopeai.com/integrations/integrating-with-segment) to create one.
 
-Data will only display when there are conversations imported into ScopeAI (these must be imported through separate integrations) that have a `userId` or `email` that match with the `userId` or `email` of Segment API calls. More information on this can be found [here](http://help.getscopeai.com/integrations/integrating-with-segment).
+Data will only display when there are conversations imported into ScopeAI (these must be imported through separate integrations) that have a `userId` or `email` that match with the `userId` or `email` of Segment API calls.
 
 
 ## 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()
@@ -31,12 +31,12 @@ Page calls will be sent to ScopeAI as a `pageview`.
 
 You can filter by this data in ScopeAI by finding "Page View" under "User Attributes".
 
-This data can be used to customize analysis on ScopeAI, information on how can be found [here](http://help.getscopeai.com/getting-started/customizing-analysis).
+This data can be used to customize analysis on ScopeAI.
 
 
 ## 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', {
@@ -48,17 +48,17 @@ Identify calls will be sent to ScopeAI as an `identify` event. The `userId` will
 
 ScopeAI saves all traits of an `identify` event under "User Attributes" which can be used to filter queries.
 
-This data can be used to customize analysis on ScopeAI, information on how can be found [here](http://help.getscopeai.com/getting-started/customizing-analysis).
+This data can be used to customize analysis on ScopeAI.
 
 
 ## 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')
 ```
 
 Track calls will be sent to ScopeAI as a `track` event.
 
-This data can be used to customize analysis on ScopeAI, information on how can be found [here](http://help.getscopeai.com/getting-started/customizing-analysis).
+This data can be used to customize analysis on ScopeAI.

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

@@ -48,7 +48,7 @@ It looks like this:
 analytics.page('Blog', '15,000 Ways to Increase Conversion');
 ```
 
-You can label as many categories / modules as you need, but as a best practice you'll probably want to have around 5 for a small – medium sized app to 20 for a very large web-application. Not sure which modules to use? Check out Totango's [Best Practices guide](http://help.totango.com/best-practices/preparing-an-integration-worksheet/).
+You can label as many categories / modules as you need, but as a best practice you'll probably want to have around 5 for a small – medium sized app to 20 for a very large web-application.
 
 
 ## Identify

src/connections/destinations/catalog/tv-squared/index.md

@@ -3,7 +3,7 @@ rewrite: true
 title: tvsquared Destination
 ---
 
-[TV Squared](https://tvsquared.com/) enables you to pull same-day TV performance analytics so you can manage TV spend, and create data-driven TV media plans based on network, days, programs, and genres. Our TV Squared Destination is open-source. You can browse the code [in GitHub](https://github.com/segment-integrations/analytics.js-integration-tvsquared).
+[TV Squared](https://tvsquared.com/) enables you to pull same-day TV performance analytics so you can manage TV spend, and create data-driven TV media plans based on network, days, programs, and genres. Our TV Squared Destination is open-source. You can browse the code [in GitHub](https://github.com/segmentio/analytics.js-integrations/tree/master/integrations/tvsquared).
 
 This document was last updated on April 20th, 2018. If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, [let us know](https://segment.com/help/contact/)!
 
@@ -23,7 +23,7 @@ This document was last updated on April 20th, 2018. If you notice any gaps, outd
 
 ## 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();
@@ -33,7 +33,7 @@ When you call `page` in Analytics.js, we call TV Squared's `Basic Hit Tracker`.
 
 ## 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('Completed Purchase', {

src/guides/how-to-guides/join-user-profiles.md

@@ -31,7 +31,7 @@ Though we wish you could use a database ID for everything, some tools force you
 
 ## For Segment Destination Users
 
-Integrating as many tools as possible through Segment will make your joins down the road a little easier. When you use Segment to [`identify`](https://segment.com/docs/connections/spec/identify) users, we'll send the same ID and traits out to all the destinations you turn on in our interface. (More about [Segment destinations](https://segment.com/docs/connections/destinations/catalog).
+Integrating as many tools as possible through Segment will make your joins down the road a little easier. When you use Segment to [`identify`](/docs/connections/spec/identify) users, we'll send the same ID and traits out to all the destinations you turn on in our interface. (More about [Segment destinations](/docs/connections/destinations/catalog).
 
 A few of our destination partners accept an external ID, where they will insert the same Segment user ID. Then you can join tables in one swoop. For example, Zendesk saves the Segment User ID as `external_id`, making a Segment-Zendesk join look like this:
 
@@ -150,7 +150,7 @@ ORDERBY2desc
 
 An alternative to the lookup user table in SQL would be writing a script to grab user IDs across your third-party tools and dump them into your database.
 
-You'd have to ping the APIs of each tool with something like an email, and ask them toreturn the key or id for the corresponding user in their tool.
+You'd have to ping the APIs of each tool with something like an email, and ask them to return the key or id for the corresponding user in their tool.
 
 A sample script, to run on a nightly cron job, would look something like this: