updates

Author: markzegarelli

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

@@ -22,7 +22,7 @@ This destination is maintained by [Algolia](https://www.algolia.com/). For any i
 
 1. From the Segment web app, click **Catalog**.
 2. Search for "Algolia" in the Catalog, select it, and choose which of your sources to connect the destination to.
-3. Enter the "App ID" & "API Key" into your Segment Settings UI which you can find from your [Algolia Dashboard](https://www.algolia.com/apps/), under API Keys menu.
+3. Enter the "App ID" & "API Key" into your Segment Settings UI which you can find from your Algolia Dashboard, under API Keys menu.
 
 _**NOTE:** The Algolia Insights Destination is not a plug-and-play integration. It requires you to modify your frontend code to send additional Algolia-related data like index name, queryID, etc._
 

src/connections/destinations/catalog/facebook-app-events/index.md

@@ -12,13 +12,13 @@ This document was last updated on October 04, 2018. If you notice any gaps, outd
 ## Other Facebook Destinations Supported by Segment
 This page is about the **Facebook App Events**. For documentation on other Facebook destinations, see the pages linked below.
 
-| **Facebook Destination**   | Supported by Personas |
-| ---------------------- | --------------------- |
-| **[Facebook App Events](/docs/connections/destinations/catalog/facebook-app-events/)**                  | Yes                   |
-| **[Facebook Offline Conversions](/docs/connections/destinations/catalog/facebook-offline-conversions/)** | Yes                   |
-| **[Facebook Pixel](/docs/connections/destinations/catalog/facebook-pixel/)**                             | No                    |
-| **[Facebook Custom Audiences](/docs/connections/destinations/catalog/personas-facebook-custom-audiences/)**      | Yes                   |
-| **Facebook Custom Audiences Website**    | Yes                   |
+| **Facebook Destination**                                                                                    | Supported by Personas |
+| ----------------------------------------------------------------------------------------------------------- | --------------------- |
+| **[Facebook App Events](/docs/connections/destinations/catalog/facebook-app-events/)**                      | Yes                   |
+| **[Facebook Offline Conversions](/docs/connections/destinations/catalog/facebook-offline-conversions/)**    | Yes                   |
+| **[Facebook Pixel](/docs/connections/destinations/catalog/facebook-pixel/)**                                | No                    |
+| **[Facebook Custom Audiences](/docs/connections/destinations/catalog/personas-facebook-custom-audiences/)** | Yes                   |
+| **Facebook Custom Audiences Website**                                                                       | Yes                   |
 
 
 
@@ -239,7 +239,7 @@ In addition to the integration available for both iOS and Android, there is a cl
 
 ### Pre-defined Events and Parameters
 
-The integration currently only supports the `FBSDKAppEventNameActivatedApp` pre-defined event (via the `activateApp` handler). All other events are forwarded as [custom events](https://developers.facebook.com/docs/app-events/ios#custom). If other [pre-defined events](https://developers.facebook.com/docs/app-events/ios#manual) are important to you, [contact us](https://segment.com/help/contact/).
+The integration currently only supports the `FBSDKAppEventNameActivatedApp` pre-defined event (via the `activateApp` handler). All other events are forwarded as [custom events](https://developers.facebook.com/docs/app-events/getting-started-app-events-ios). If other pre-defined events are important to you, [contact us](https://segment.com/help/contact/).
 
 ## Troubleshooting
 

src/connections/destinations/catalog/ibm-ubx/index.md

@@ -60,9 +60,6 @@ endpoint from Segment's support team._
    authentication key again and paste it into your UBX settings in the Segment
    UI.
 
-You can read more about defining and activating applications in UBX [here in
-their
-documentation](https://www.ibm.com/support/knowledgecenter/en/SS9JVY/UBX/Endpoints_ubx/Registering_endpoints_as_applications.html).
 
 ## General Tracking Advice
 
@@ -466,12 +463,6 @@ options:
   channels are `email` and `sms`, and the only two acceptable subscription
   options are `opt-in` and `opt-out`.
 
-For more information, refer to IBM UBX's documentation on `subchannel`
-[here](https://www.ibm.com/support/knowledgecenter/SS9JVY/UBX/Event_taxonomy_ubx/Best_practice_event_attributes.html)
-(*Best practice event attributes* article) and on `channel`
-[here](https://www.ibm.com/support/knowledgecenter/SS9JVY/UBX/Events_ubx/Event_publication.html).
-Note that recommended values for these fields is often determined by the
-downstream tools connected to UBX (e.g. Watson Customer Engagement tools).
 
 ## Troubleshooting
 
@@ -497,4 +488,3 @@ Segment's integration with UBX supports the following UBX abandonment events:
 - ibmcartAbandonment
 - ibmcartAbandonmentItem
 
-You can find more information about these events in [UBX's Event Taxonomy](https://ubx-pilot.ibmmarketingcloud.com/#/taxonomy).

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

@@ -44,7 +44,7 @@ If you use Kameleoon Full Stack, please refer to the [Kameleoon SDK documentatio
 
 Kameleoon supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
 
-If the Segment event name matches exactly the name of an existing [goal](https://help.kameleoon.com/create-new-goal/){:target="_blank"} in your Kameleoon account, a conversion for this goal will be associated to the visitor. If the goal does not exist, Kameleoon will create a [custom goal](https://help.kameleoon.com/create-new-goal/#Custom_goal){:target="_blank"} by using the Segment event name and associate the conversion to the visitor. The goal will appear in the Kameleoon [goals page](https://help.kameleoon.com/manage-goals/){:target="_blank"} with the name convention 'SegmentIO eventType - eventName'. Once the goal has been created, you can use them in any of your [campaign](https://https://help.kameleoon.com/set-up-goal-campaign/){:target="_blank"}.
+If the Segment event name matches exactly the name of an existing [goal](https://help.kameleoon.com/create-new-goal/){:target="_blank"} in your Kameleoon account, a conversion for this goal will be associated to the visitor. If the goal does not exist, Kameleoon will create a [custom goal](https://help.kameleoon.com/create-new-goal/#Custom_goal){:target="_blank"} by using the Segment event name and associate the conversion to the visitor. The goal will appear in the Kameleoon [goals page](https://help.kameleoon.com/manage-goals/){:target="_blank"} with the name convention 'SegmentIO eventType - eventName'. Once the goal has been created, you can use them in any of your [campaign](https://help.kameleoon.com/set-up-goal-campaign/){:target="_blank"}.
 
 ### Page
 

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

@@ -19,8 +19,8 @@ This destination is maintained by Proof. For any issues with the destination, [c
 
 1. From the Segment web app, click **Catalog**.
 2. Search for "Proof Experiences" in the Catalog, select it, and choose which of your sources to connect the destination to.
-3. Enter the "API Key" into your Segment Settings UI which you can find from your [Proof Experiences dashboard](https://app.proof-x.com/account/apikeys).
-4. You should see data flowing into your Proof dashboard in the [event debugger](https://app.proof-x.com/settings/events) within 1 minute of creating your API key and activating your Proof Experiences integration.
+3. Enter the "API Key" into your Segment Settings UI which you can find from your Proof Experiences dashboard.
+4. You should see data flowing into your Proof dashboard in the event debugger within 1 minute of creating your API key and activating your Proof Experiences integration.
 
 
 ## Page

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

@@ -59,6 +59,6 @@ analytics.track("Watched", {
 });
 ```
 
-Track calls will be sent to Tamber as [`event-track`](https://works.tamber.com/docs/api/#event-track) calls and increment both Event and Item counts within the Tamber UI. You can also [retrieve](https://tamber.com/docs/api/#event-retrieve) events, and [retrieve](https://tamber.com/docs/api/#item-retrieve) or [list](https://tamber.com/docs/api/#item-list) items from Tamber.
+Track calls will be sent to Tamber as [`event-track`](https://tamber.com/docs/api/#event-track) calls and increment both Event and Item counts within the Tamber UI. You can also [retrieve](https://tamber.com/docs/api/#event-retrieve) events, and [retrieve](https://tamber.com/docs/api/#item-retrieve) or [list](https://tamber.com/docs/api/#item-list) items from Tamber.
 
-**NOTE:** [`item`](https://works.tamber.com/docs/api/#item) is a required property but can be renamed within the Tamber UI under Custom Field Definition for Item. Make sure that the name passed into your Track call matches what you have set in the Tamber UI. If you are using Segment's [E-Commerce](https://segment.com/docs/connections/spec/ecommerce/v2) or [Video](https://segment.com/docs/connections/spec/video) APIs, you can configure Tamber to automatically handle item loading – either during set up or at any time in the Tamber Dashboard <strong>Sources</strong> > <strong>Segment</strong> section – and ignore this information.
+**NOTE:** [`item`](https://tamber.com/docs/api/#item) is a required property but can be renamed within the Tamber UI under Custom Field Definition for Item. Make sure that the name passed into your Track call matches what you have set in the Tamber UI. If you are using Segment's [E-Commerce](https://segment.com/docs/connections/spec/ecommerce/v2) or [Video](https://segment.com/docs/connections/spec/video) APIs, you can configure Tamber to automatically handle item loading – either during set up or at any time in the Tamber Dashboard <strong>Sources</strong> > <strong>Segment</strong> section – and ignore this information.

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

@@ -30,7 +30,7 @@ When you call `identify` on analytics.js, we call Woopra's `woopraTracker.addVis
 
 ### Server Side
 
-When you call `identify` from the server-side languages, we call Woopra's [HTTP REST API](http://www.woopra.com/docs-old/tracking/http-tracking-api/) with the traits that you pass in.
+When you call `identify` from the server-side languages, we call Woopra's [HTTP REST API](https://docs.woopra.com/reference/intro-http-tracking) with the traits that you pass in.
 
 
 ## Group

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

@@ -3,7 +3,7 @@ rewrite: true
 title: Zendesk Chat (Zopim) Destination
 ---
 
-[Zendesk Chat](https://developer.zendesk.com/rest_api/docs/chat/introduction), (previously called Zopim) is a live chat solution that helps businesses increase sales conversion by engaging important leads on their websites. The `analytics.js` Zendesk Chat Destination is open-source. You can browse the code [on GitHub](https://github.com/segment-integrations/analytics.js-integration-zopim).
+[Zendesk Chat](https://developer.zendesk.com/rest_api/docs/chat/introduction), (previously called Zopim) is a live chat solution that helps businesses increase sales conversion by engaging important leads on their websites. The `analytics.js` Zendesk Chat Destination is open-source. You can browse the code [on GitHub](https://github.com/segmentio/analytics.js-integrations/tree/master/integrations/zopim).
 
 **NOTE:** Zendesk Chat currently offers [two types of widgets](https://support.zendesk.com/hc/en-us/articles/115007912068-Using-the-Chat-JavaScript-API): a standalone `Chat Widget`, which is mainly designed to provide chat related features, and a `Web Widget`, which incorporates both Zendesk Chat and Zendesk Support functionalities. At the moment, Segment only supports the `Chat Widget`. For more details refer to the "Getting Started" section below.
 

src/connections/sources/catalog/cloud-apps/delighted/index.md

@@ -17,8 +17,6 @@ This source is maintained by Delighted. For any issues with the source, you may
 6. Enable the "Sync feedback to Segment" option.
 7. Copy the Write Key from your Delighted source within Segment and paste it into the provided box within Delighted
 
-![segment-delighted-setup](https://scrn.es/6fEhinjMQGiuESd2aQqLcv.gif)
-
 **NOTE**: We only send feedback back to Segment on surveys triggered from Segment initially. This ensures all feedback we send to Segment is identified and enriched with Segment information.
 
 ## Components