Fix broken external links (#2668)

Author: markzegarelli

ignore-links.txt

@@ -61,8 +61,9 @@ https://support.autopilothq.com/hc/en-us/categories/200396835-Segment
 https://support.autopilothq.com/hc/en-us/requests/new
 https://support.cloudflare.com/hc/en-us/articles/360020348832-How-do-I-do-CNAME-setup-
 https://support.twilio.com/hc/en-us/articles/223136127-Twilio-Support-business-hours
+https://talkable.helpjuice.com/questions/45313-Where-do-I-find-my-site-ID
 https://www.braze.com/documentation/Web/#step-5-configure-safari-push
 https://www.getdrip.com/settings/site
 https://www.linkedin.com/company/segment-io/
 https://www.navilytics.com/member/code_settings
-https://www.navilytics.com/member/code_settings
+https://www.navilytics.com/member/code_settings

src/connections/destinations/catalog/doubleclick-floodlight/index.md

@@ -99,7 +99,7 @@ Click **Save**.
 
 ## COPPA Compliance
 
-DoubleClick Floodlight lets you set a parameter called `tag_for_child_directed_treatment` as either `0`, or `1` to mark a specific tag as coming from a user under the age of 13, under the [COPPA compliance privacy law](https://www.ftc.gov/news-events/media-resources/protecting-consumer-privacy/kids-privacy-coppa).
+DoubleClick Floodlight lets you set a parameter called `tag_for_child_directed_treatment` as either `0`, or `1` to mark a specific tag as coming from a user under the age of 13.
 
 If you want to set this flag, you can send an integration option namespaced as `coppaCompliant` with `true` or `false` (default):
 

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

@@ -54,7 +54,7 @@ analytics.identify("userId123", {
 
 ## Track
 
-If you're not familiar with the Segment Specs, take a look to understand what the [track method](/docs/connections/spec/track/) does. Track calls sent to Segment will be automatically passed directly to FullStory using [FullStory's](https://help.fullstory.com/develop-js/363565-fs-event-api-sending-custom-event-data-into-fullstory) `FS.event` method, including all the properties passed in the event.
+If you're not familiar with the Segment Specs, take a look to understand what the [track method](/docs/connections/spec/track/) does. Track calls sent to Segment will be automatically passed directly to FullStory using [FullStory's](https://help.fullstory.com/hc/en-us/articles/360020623274){:target="_blank} `FS.event` method, including all the properties passed in the event.
 
 An example call would look like:
 

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

@@ -34,4 +34,4 @@ These events are enriched with other data, aggregated, and pushed to appropriate
 
 ## Questions?
 
-More details available on [MadKudu's website](http://www.madkudu.com/segment) or email  [hello@madkudu.com](mailto:hello@madkudu.com).
+More details available on [MadKudu's website](http://www.madkudu.com/) or email  [hello@madkudu.com](mailto:hello@madkudu.com).

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

@@ -243,7 +243,7 @@ Copy the Server Key from the FCM console and add it to the MoEngage Dashboard. T
 
 To display push notifications, some metadata regarding the notification is required. For example, the small icon and large icon drawables are mandatory.
 
-Refer to the [MoEngage - NotificationConfig](https://moengage.github.io/android-api-reference/core/core/com.moengage.core.config/-notification-config/index.html) API reference for all the possible options.
+Refer to the [MoEngage - NotificationConfig](https://moengage.github.io/android-api-reference-v11/core/com.moengage.core.config/-notification-config/index.html){:target="_blank"} API reference for all the possible options.
 
 Use the `configureNotificationMetaData()` to pass on the configuration to the SDK.
 
@@ -319,7 +319,7 @@ When the MoEngage SDK handles push registration, it optionally provides a callba
 
 An application can get this callback by implementing `FirebaseEventListener` and registering for a callback in the Application class `onCreate()` using `MoEFireBaseHelper.getInstance().addEventListener()`
 
-Refer to the [MoEngage - API reference](https://moengage.github.io/android-api-reference/moe-push-firebase/moe-push-firebase/com.moengage.firebase.listener/-firebase-event-listener/index.html) for more details on the listener.
+Refer to the [MoEngage - API reference](https://moengage.github.io/android-api-reference-v11/moe-push-firebase/com.moengage.firebase.listener/-firebase-event-listener/index.html?query=open%20class%20FirebaseEventListener){:target="_blank"} for more details on the listener.
 
 
 

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

@@ -23,7 +23,7 @@ Vero is supported on the client-side, server-side and mobile.
 
 When you call [`identify`](/docs/connections/spec/identify/) on analytics.js, we augment `traits` to have `traits.id` set to the `userId`, and then call Vero's `user` with the augmented traits object. You should provide both a `traits.email` and a `userId` for Vero to work best.
 
-If no `email` is attached, the user is created in Vero but cannot be emailed. If you send omit the `userId`, Vero will use the email as the ID, which is is not recommended. Check out the [Vero docs](http://www.getvero.com/help/adding-data-to-vero/creating-and-matching-vero-user-ids/) for more information.
+If no `email` is attached, the user is created in Vero but cannot be emailed. If you send omit the `userId`, Vero will use the email as the ID, which is is not recommended. Check out the [Vero docs](https://help.getvero.com/workflows/articles/creating-and-matching-vero-customer-ids/){:target="_blank"} for more information.
 
 A `userId` is a required value for all types of calls. Be sure you call `identify` with a `userId` for subsequent `track` calls to populate into Vero correctly. For server side calls, you will have to manually pass in the `userId` at the top level.
 

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

@@ -17,7 +17,7 @@ This destination is maintained by Vespucci. For any issues with the destination,
 2. Search for "Vespucci" in the Destinations Catalog, and select the Vespucci destination.
 3. Choose which Source should send data to the Vespucci destination.
 4. Go to your "Your Active Projects" section on your [Vespucci Dashboard](https://dashboard.vespuccianalytics.com). Click on the **+** button. Enter a name and select "Segment Destination" as the DataPipe.
-5. [Depending on your project configuration](https://vespuccianalytics.com/docs/#segment), select one of the two tracking methods and click "Create" to create your project.
+5. [Depending on your project configuration](https://www.vespuccianalytics.com/documentation-article/getting-started){:target="_blank"}, select one of the two tracking methods and click "Create" to create your project.
 6. Take note of the API key associated with this project. Back in the Segment App, enter your API key in the Vespucci destination settings.
 
 ## Page