Merge pull request #2406 from segmentio/develop

Release 22.4.1

Author: forstisabella

ignore-links.txt

@@ -0,0 +1,34 @@
+https://www.linkedin.com/company/segment-io/
+https://support.twilio.com/hc/en-us/articles/223136127-Twilio-Support-business-hours
+https://support.cloudflare.com/hc/en-us/articles/360020348832-How-do-I-do-CNAME-setup-
+https://github.com/segment-integrations/analytics.js-integration-adlearn-open-platform
+https://github.com/segment-integrations/analytics.js-integration-adobe-analytics
+https://marketing.adobe.com/resources/help/en_US/sc/implement/context_data_variables.html
+https://marketing.adobe.com/resources/help/en_US/sc/implement/timestamps-overview.html
+https://help.adroll.com/hc/en-us/articles/213429827-Currency-Codes
+https://github.com/GetAmbassador/segment/blob/master/lib/index.js
+https://help.amplitude.com/hc/en-us/articles/235649848-Settings#general
+https://help.amplitude.com/hc/en-us/articles/115002923888-Limits#h_8d90ca72-bf91-4161-88b2-01b5448b0859
+https://help.amplitude.com/hc/en-us/articles/360017800371
+https://help.amplitude.com/hc/en-us/articles/360003032451-Instrumentation-Explorer-Debugger
+https://amplitude.com/settings
+https://support.anodot.com/hc/en-us/articles/360018508380-Segment-Integration
+https://support.anodot.com/hc/en-us/articles/360009537879-Mapping-Dimensions-to-Measures-BETA-
+https://github.com/segment-integrations/analytics.js-integration-appnexus
+https://support.appsflyer.com/hc/en-us/articles/207034486-Server-to-Server-In-App-Events-API-HTTP-API-
+https://support.appsflyer.com/hc/en-us/articles/207032246-OneLink-Setup-Guide
+https://support.appsflyer.com/hc/en-us/articles/207032066-AppsFlyer-SDK-Integration-iOS
+https://support.appsflyer.com/hc/en-us/articles/207032126-AppsFlyer-SDK-Integration-Android 
+https://support.autopilothq.com/hc/en-us/categories/200396835-Segment
+https://support.autopilothq.com/hc/en-us/requests/new
+https://support.autopilothq.com/hc/en-us/articles/203658119
+https://bugsnag.com/dashboard
+https://github.com/segment-integrations/analytics.js-integration-clevertap
+https://github.com/segment-integrations/analytics.js-integration-convertro
+https://github.com/segment-integrations/analytics.js-integration-criteo
+https://app.dreamdata.io/settings
+https://www.getdrip.com/settings/site
+https://github.com/segment-integrations/analytics.js-integration-eloqua
+https://github.com/segment-integrations/analytics.js-integration-email-aptitude
+https://platform.epica.ai/login
+https://github.com/segment-integrations/analytics.js-integration-friendbuy

scripts/checklinks-external.js

@@ -22,41 +22,61 @@ const checkForDeadExternalUrls = async () => {
     const ph = posthtml([
       require('posthtml-urls')({
         eachURL: (url) => {
-          if (!url.startsWith('http://0') && !url.startsWith('/') && !url.startsWith('https://github.com/segmentio'))  {
+          if (!url.startsWith('http://0') && !url.startsWith('/') && !url.startsWith('https://github.com/segmentio')) {
             urls.add(url)
           }
         },
       }),
     ])
     throbber.succeed()
     throbber.start('Processing files')
-    
+
     // Run the above logic on each file 
     files.forEach((file) => {
       ph.process(fs.readFileSync(file))
     })
 
-   
+
     // Check all the links collected in the section above
+    throbber.succeed()
     throbber.start('Checking the links')
     const results = await checkLinks(
       Array.from(urls).map((url) =>
         url
-      ),
+      )
     )
+
     // If a link returns 'dead' (404), add it to an array
     const deadUrls = Array.from(urls).filter(
-      (url) => results[url].status === 'dead',
+      (url) => results[url].statusCode === 404,
     )
-    
+ 
+    // Get the ignore list
+    throbber.succeed()
+    throbber.start('Get the ignore list')
+    const readFileLines = filename =>
+      fs.readFileSync(filename)
+      .toString('UTF8')
+      .split('\n')
+
+    let ignoreList = readFileLines('ignore-links.txt')
+
+    throbber.succeed()
+
+    // Filter the ignored links
+    throbber.start('Filter the ignored URls')
+    let broke = []
+    broke = deadUrls.filter(val => !ignoreList.includes(val));
+
     // If there are dead URLs, list them here, along with the count. Exit status 1 to indicate an error.
-    if (deadUrls.length > 0) {
-      throbber.fail(`Dead URLS: ${deadUrls.length}\n\n`)
-      console.log(`Dead URLS: ${deadUrls.length}\n\n${deadUrls.join('\n')}`)
+    if (broke.length > 0) {
+      throbber.fail(`Dead URLS: ${broke.length}\n\n`)
+      console.log(`Dead URLS: ${broke.length}\n\n${broke.join('\n')}`)
       process.exit(1)
-    } 
+    }
     // Otherwise, claim that all the links work, and exit the process normally.
     else {
+      throbber.succeed()
       console.log('All links work!')
       process.exit
     }

scripts/test.js

@@ -0,0 +1,10 @@
+const checkLinks = require('check-links')
+
+const check =  async () => {
+  const url = process.argv[2]
+  const results = await checkLinks([url])
+  console.log(results)
+
+}
+
+check()

src/connections/destinations/catalog/actions-braze-web/index.md

@@ -34,7 +34,7 @@ Braze Web Mode (Actions) can use the following features of Braze.
 
 ### In-app Messaging
 
-Find instructions to configure In-app Messaging in the Braze [documentation](https://www.braze.com/academy/Best_Practices/#in-app-message-behavior){:target="_blank"}. Once configured, you can trigger in-app message display as a result of several different event types. By default, all In-App Messages that a user is eligible for are automatically delivered to the user upon a session start event. A new session automatically starts when a user loads your site. If you'd like to force a new session for a user, make an Identify call with the corresponding [userId](/docs/connections/spec/identify/#user-id) for that user.
+Once configured, you can trigger in-app message display as a result of several different event types. By default, all In-App Messages that a user is eligible for are automatically delivered to the user upon a session start event. A new session automatically starts when a user loads your site. If you'd like to force a new session for a user, make an Identify call with the corresponding [userId](/docs/connections/spec/identify/#user-id) for that user.
 
 If you don't want your site to display new In-App Messages as they're received, disable automatic display and register your own display subscribers. To do this:
 
@@ -60,7 +60,7 @@ The `inAppMessages` parameter will be an array of [`appboy.ab.InAppMessage`](htt
 
 ### Push Notifications
 
-1. To support push notifications on Chrome, you'll need to enable FCM/GCM as well as configure your site. Check out steps [one and two here, for detailed instructions on both](https://www.braze.com/documentation/Web/#step-1-to-support-chrome-enable-fcmgcm){:target="_blank"}.
+1. To support push notifications on Chrome, you'll need to enable FCM/GCM as well as configure your site. Check out steps [one and two here for detailed instructions on both](https://www.braze.com/docs/developer_guide/platform_integration_guides/web/initial_sdk_setup#step-1-to-support-chrome-enable-fcmgcm){:target="_blank"}.
 
 2. Browser Registration. In order for a browser to receive push notifications, you must register it for push by calling:
 
@@ -94,13 +94,13 @@ analytics.ready(function() {
 });
 ```
 
-1. Set your GCM/FCM server API key and SenderID on the Braze dashboard. You can find more details for this [here](https://www.braze.com/documentation/Web/#step-4-set-your-gcmfcm-server-api-key-and-senderid-on-the-Braze-dashboard){:target="_blank"}.
+1. Set your GCM/FCM server API key and SenderID on the Braze dashboard. You can find more details for this [here](https://www.braze.com/docs/developer_guide/platform_integration_guides/web/initial_sdk_setup#step-4-set-your-gcmfcm-server-api-key-and-senderid-on-the-Braze-dashboard){:target="_blank"}.
 
-2. To support push notifications on Safari, add your Website Push ID into your Segment Settings UI and Segment sends it when the Braze Web SDK initializes. To get your Website Push ID, follow the first two bullet points in [these instructions](https://www.braze.com/documentation/Web/#step-5-configure-safari-push){:target="_blank"}.
+2. To support push notifications on Safari, add your Website Push ID into your Segment Settings UI and Segment sends it when the Braze Web SDK initializes. To get your Website Push ID, follow the first two bullet points in [these instructions](https://www.braze.com/docs/developer_guide/platform_integration_guides/web/initial_sdk_setup#step-5-configure-safari-push){:target="_blank"}.
 
 ### Soft Push Prompts
 
-1. Follow [step one](https://www.braze.com/documentation/Web/#soft-push-prompts){:target="_blank"} to create a "Prime for Push" in-app messaging Campaign on the Braze dashboard.
+1. Follow [step one](https://www.braze.com/docs/developer_guide/platform_integration_guides/web/initial_sdk_setup#soft-push-prompts){:target="_blank"} to create a "Prime for Push" in-app messaging Campaign on the Braze dashboard.
 
 2. Add the following snippet to your site:
 
@@ -141,7 +141,7 @@ analytics.ready(function() {
  });
 ```
 
-For more details on this snippet, see Braze's documentation [here](https://www.braze.com/documentation/Web/#soft-push-prompts){:target="_blank"}.
+For more details on this snippet, see Braze's documentation [here](https://www.braze.com/docs/developer_guide/platform_integration_guides/web/initial_sdk_setup#soft-push-prompts){:target="_blank"}.
 
 > info ""
 > Place this snippet outside of your [Segment Snippet](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/#step-2-copy-the-segment-snippet) within your `script` tag.

src/connections/destinations/catalog/actions-friendbuy-web/index.md renamed to src/connections/destinations/catalog/actions-friendbuy/index.md

@@ -0,0 +1,23 @@
+---
+title: Voyage (Actions) Destination
+hide-boilerplate: true
+hide-dossier: true
+---
+{% include content/plan-grid.md name="actions" %}
+
+[Voyage SMS](https://www.voyagesms.com){:target="_blank"} is a message commerce and SMS marketing platform that empowers brands to engage, convert, and delight customers through 1:1 personalized messaging at scale.
+
+> success ""
+> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Voyage Segment destination.
+
+
+## Getting Started
+
+1. From the Segment web app, click **Catalog**, then click **Destinations**.
+2. Find the Destinations Actions item in the left navigation, and click it.
+3. Click **Configure Actions Voyage**.
+4. Select an existing Source to connect to Voyage (Actions).
+5. Enter your Voyage **API Key**. You can create a new API Key or find your existing API Key in the Advanced section of your [Voyage Settings Page](https://app.voyagetext.com/dashboard/settings/advanced){:target="_blank"}.
+6. Select **Quick Setup** to start with a pre-populated subscriptions, or **Customized Setup** to configure each action from scratch. Click **Configure Actions**.
+
+{% include components/actions-fields.html %}

src/connections/destinations/catalog/actions-voyage/index.md

@@ -145,7 +145,7 @@ Segment's server-side integration is not open-source. Let's explore what happens
 
    **Important**: The Android library can collect the `userAgent` automatically - however, the iOS library cannot do so. However, since Segment does collect other contextual metadata about a device, it can render a valid iOS userAgent string to populate your Mobile Web Reports.
 
-6. If you are using the [Marketing Cloud ID Service](https://marketing.adobe.com/resources/help/en_US/mcvid/mcvid_overview.html), you can pass the **Marketing Cloud Visitor ID** as an destination specific setting and which Segment sets as `<marketingCloudVisitorID>`.
+6. If you are using the Marketing Cloud ID Service, you can pass the **Marketing Cloud Visitor ID** as a destination specific setting and which Segment sets as `<marketingCloudVisitorID>`.
 
  (In Node.js)
  ```javascript

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

@@ -267,7 +267,7 @@ When you make a `page` call, here's what Segment does from the browser when you
 
 3. Checks if the page call is associated with a `userId` from a previous `.identify()` call. If so, Segment sets the `userId` as `window.s.visitorID`.
 
-  **IMPORTANT**: Adobe Analytics [does not support setting visitorID](https://marketing.adobe.com/resources/help/en_US/sc/implement/timestamps-overview.html) if you are sending a timestamped call. So Segment first checks if your **Timestamp Option** is `disabled` _and_ that a `userId` exists on the event, and only then sets `window.s.visitorID`.
+  **IMPORTANT**: Adobe Analytics doesn't support setting visitorID if you send a timestamped call. So Segment first checks if your **Timestamp Option** is `disabled` _and_ that a `userId` exists on the event, and only then sets `window.s.visitorID`.
 
 4. Checks for some common properties, and sets them on the `window.s` object:
 

src/connections/destinations/catalog/adobe-analytics/settings.md

@@ -10,8 +10,7 @@ published: false
 coding and set up hassles of A/B testing to help you quickly discover which
 offers, experiences and messages truly engage your visitors.
 
-_**NOTE:** Adobe Target is currently in beta, and this doc was last
-updated on March 7, 2018. This means that there may still be some bugs for us to
+_**NOTE:** Adobe Target is currently in beta. This means that there may still be some bugs for us to
 iron out, and we're excited to hear your thoughts. If you are interested in
 joining or have any feedback to help us improve the Adobe Target
 Destination and its documentation, [let us know](https://segment.com/help/contact)!_

src/connections/destinations/catalog/adobe-target/index.md

@@ -4,7 +4,6 @@ title: Alexa Destination
 ---
 [Alexa](https://www.alexa.com/) helps improve your website's SEO and conduct competitive analysis. They help your business get better marketing results. The Alexa Destination is open-source. You can browse the code [on GitHub](https://github.com/segment-integrations/analytics.js-integration-alexa).
 
-This document was last updated on October 16, 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)!
 
 ## Getting Started
 

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

@@ -8,9 +8,11 @@ redirect_from: '/connections/destinations/catalog/algolia/'
 
 [Algolia Insights](https://www.algolia.com/products/analytics/) lets you push events related to how your product is being used. Sending those events is a required step for using several Algolia features:
 
-- Click analytics
+- Click and conversion analytics
 - A/B Testing
+- AI Re-Ranking
 - Personalization
+- Algolia Recommend
 
 This destination is maintained by [Algolia](https://www.algolia.com/). For any issues with the destination, [contact the Algolia team](mailto:[email protected]).
 
@@ -26,7 +28,7 @@ This destination is maintained by [Algolia](https://www.algolia.com/). For any i
 _**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._
 
 
-You can read more about how to send Algolia-related data to Segment from [the documentation at Algolia](https://www.algolia.com/doc/guides/getting-insights-and-analytics/connectors/segment/).
+You can read more about how to send Algolia-related data to Segment from [the documentation at Algolia](https://www.algolia.com/doc/guides/sending-events/implementing/connectors/segment/).
 
 
 ## Track

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

@@ -4,8 +4,6 @@ title: Amazon Kinesis Firehose Destination
 ---
 [Amazon Kinesis Firehose](https://aws.amazon.com/kinesis/data-firehose/) provides way to load streaming data into AWS. It can capture, transform, and load streaming data into Amazon Kinesis Analytics, Amazon S3, Amazon Redshift, and Amazon Elasticsearch Service, enabling near real-time analytics with existing business intelligence tools and dashboards you're already using today. It's a fully managed service that automatically scales to match the throughput of your data and requires no ongoing administration. It can also batch, compress, and encrypt the data before loading it, minimizing the amount of storage used at the destination and increasing security.
 
-This document was last updated on February 05, 2020. 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)!
-
 ## Getting Started
 
 {% include content/connection-modes.md %}

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

@@ -5,8 +5,6 @@ title: Ambassador Destination
 
 [Ambassador](https://www.getambassador.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) empowers companies to easily create, track & manage custom incentives that drive referrals and evangelize their users. The Ambassador Destination is open-source. You can browse the code [on GitHub](https://github.com/segment-integrations/analytics.js-integration-ambassador).
 
-This document was last updated on September 03, 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)!
-
 ## Getting Started
 
 {% include content/connection-modes.md %}