Merge branch 'master' into DOC-116_SQL-trait-payload-size

Author: markzegarelli

.gitignore

@@ -11,3 +11,4 @@ node_modules/
 src/assets/docs.bundle.js
 yarn-error.log
 # Make sure to update `analytics` to the full path to your Typewriter client.
+.vscode/spellright.dict

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# destination categories last updated 2021-01-14 
+# destination categories last updated 2021-01-25 
 items:
 - display_name: Email Marketing
   slug: email-marketing

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# destination data last updated 2021-01-14 
+# destination data last updated 2021-01-25 
 items:
 - display_name: ActiveCampaign
   slug: activecampaign
@@ -3500,9 +3500,6 @@ items:
       for more info. **Please ensure you read
       [this](https://segment.com/docs/connections/destinations/catalog/braze/#migrating-to-v2-of-the-braze-web-sdk)
       section of our documentation carefully before changing this setting.**
-
-
-      Note: version 3.1 is in pre-release and not available to all customers.
     settings: []
   - name: customEndpoint
     display_name: Custom API Endpoint
@@ -7479,7 +7476,7 @@ items:
   description: >-
     The Facebook Pixel integration lets you measure and optimize the performance
     of your Facebook Ads.
-  hidden: false
+  hidden: true
   url: connections/destinations/catalog/facebook-conversions-api
   status: PUBLIC_BETA
   logo:
@@ -11145,60 +11142,6 @@ items:
       server: false
   previous_names:
   - Inspectlet
-- display_name: Intellimize
-  slug: intellimize
-  name: catalog/destinations/intellimize
-  description: >-
-    Intellimize helps companies keep more of their hard-earned customers through
-    continuous, machine learned personalization. Intellimize optimizes desktop
-    and mobile websites to drive users to action, like signing up, stopping a
-    cancellation flow, or engaging more deeply with your product.
-  hidden: false
-  url: connections/destinations/catalog/intellimize
-  status: PUBLIC
-  logo:
-    url: 'https://cdn.filepicker.io/api/file/yGpukMPGSAWl3Looo7jd'
-  mark:
-    url: 'https://cdn.filepicker.io/api/file/2bHRWqHAQA6eVmnz5HEq'
-  categories:
-  - Personalization
-  components:
-  - type: CLOUD
-  platforms:
-    browser: true
-    server: true
-    mobile: true
-  browserUnbundlingSupported: false
-  browserUnbundlingPublic: true
-  methods:
-    alias: true
-    group: true
-    identify: true
-    page_view: true
-    track: true
-  settings:
-  - name: apiKey
-    display_name: API Key
-    type: STRING
-    deprecated: false
-    required: true
-    string_validators:
-      regexp: ''
-    description: >-
-      Please contact your Intellimize account representative or
-      [email protected] to receive your API Key.
-    settings: []
-  connection_modes:
-    device:
-      web: false
-      mobile: false
-      server: false
-    cloud:
-      web: true
-      mobile: true
-      server: true
-  previous_names:
-  - Intellimize
 - display_name: Interana
   slug: interana
   name: catalog/destinations/interana
@@ -17748,15 +17691,6 @@ items:
       required: false
       description: Map your Segment properties to Responsys Columns
       settings:
-      - name: columns
-        display_name: Segment Property Name
-        type: STRING
-        deprecated: false
-        required: true
-        string_validators:
-          regexp: ''
-        description: Enter the Segment Property Name.
-        settings: []
       - name: fieldName
         display_name: Responsys Column Name
         type: STRING
@@ -17790,6 +17724,15 @@ items:
         required: false
         description: Mark this property as a Primary Key in Responsys.
         settings: []
+      - name: columns
+        display_name: Segment Property Name
+        type: STRING
+        deprecated: false
+        required: true
+        string_validators:
+          regexp: ''
+        description: Enter the Segment Property Name.
+        settings: []
     - name: mapEmail
       display_name: Map Email
       type: BOOLEAN
@@ -18336,6 +18279,153 @@ items:
       server: false
   previous_names:
   - Rollbar
+- display_name: SIGNL4 Alerting
+  slug: signl4-alerting
+  name: catalog/destinations/signl4-alerting
+  description: >-
+    Lightweight, app-based alerting of operational teams by app push, SMS text
+    and voice call including tracking, escalation, collaboration and duty
+    planning.
+  hidden: false
+  url: connections/destinations/catalog/signl4-alerting
+  status: PUBLIC_BETA
+  logo:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/051d6c4b-15cd-44b7-b4df-0834410ccdfe.svg
+  mark:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/692d01ee-6911-4f17-9535-e34c2ac3574d.svg
+  categories:
+  - Analytics
+  - SMS & Push Notifications
+  - Security & Fraud
+  - Performance Monitoring
+  components: []
+  platforms:
+    browser: true
+    server: true
+    mobile: true
+  browserUnbundlingSupported: false
+  browserUnbundlingPublic: false
+  methods:
+    alias: true
+    group: true
+    identify: true
+    page_view: true
+    track: true
+  settings:
+  - name: apiKey
+    display_name: API Key
+    type: STRING
+    deprecated: false
+    required: true
+    string_validators:
+      regexp: '^.{8,}$'
+    description: Your SIGNL4 team secret.
+    settings: []
+  - name: message
+    display_name: Message
+    type: STRING
+    deprecated: false
+    required: false
+    string_validators:
+      regexp: ''
+    description: Alert message.
+    settings: []
+  - name: s4AlertingScenario
+    display_name: S4 Alerting Scenario
+    type: STRING
+    deprecated: false
+    required: false
+    string_validators:
+      regexp: ''
+    description: >-
+      Pass 'single_ack' if only one person needs to confirm this alert. Pass
+      'multi_ack' in case this alert must be confirmed by the number of people
+      who are on duty at the time this alert is raised.
+    settings: []
+  - name: s4ExternalId
+    display_name: S4 External ID
+    type: STRING
+    deprecated: false
+    required: false
+    string_validators:
+      regexp: ''
+    description: >-
+      If the event originates from a record in a 3rd party system, use this
+      parameter to pass the unique ID of that record. That ID will be
+      communicated in outbound webhook notifications from SIGNL4, which is great
+      for correlation/synchronization of that record with the alert.
+    settings: []
+  - name: s4Filtering
+    display_name: S4 Filtering
+    type: BOOLEAN
+    deprecated: false
+    required: false
+    description: >-
+      Specify a boolean value of true or false to apply event filtering for this
+      event, or not. If set to true, the event will only trigger a notification
+      to the team, if it contains at least one keyword from one of your services
+      and system categories (i.e. it is whitelisted).
+    settings: []
+  - name: s4Location
+    display_name: S4 Location
+    type: STRING
+    deprecated: false
+    required: false
+    string_validators:
+      regexp: ''
+    description: >-
+      Transmit location information ('latitude, longitude') with your event and
+      display a map in the mobile app.
+    settings: []
+  - name: s4Service
+    display_name: S4 Service
+    type: STRING
+    deprecated: false
+    required: false
+    string_validators:
+      regexp: ''
+    description: Assigns the alert to the service/system category with the specified name.
+    settings: []
+  - name: s4Status
+    display_name: S4 Status
+    type: STRING
+    deprecated: false
+    required: false
+    string_validators:
+      regexp: ''
+    description: >-
+      If you want to resolve an existing alert by an external id
+      (X-S4-ExternalID), you can add this status parameter. It has two possible
+      values: 'new' and 'resolved'. Sending an event with the status 'new' will
+      create a new alert. If you want to resolve a alert, make sure to set the
+      X-S4-Status to 'resolved' and provide an external ID via the
+      'X-S4-ExternalID' parameter for the alert(s) you want to resolve. It is
+      only possible to resolve a alert with a provided external id that
+      initially triggered it. If you set the status to any other value the event
+      will be discarded. This means no alert will trigger from it.
+    settings: []
+  - name: title
+    display_name: Title
+    type: STRING
+    deprecated: false
+    required: false
+    string_validators:
+      regexp: ''
+    description: Alert title.
+    settings: []
+  connection_modes:
+    device:
+      web: false
+      mobile: false
+      server: false
+    cloud:
+      web: false
+      mobile: false
+      server: false
+  previous_names:
+  - SIGNL4 Alerting
 - display_name: SMBStreams
   slug: smbstreams
   name: catalog/destinations/smbstream
@@ -20329,6 +20419,56 @@ items:
       server: false
   previous_names:
   - Snapboard
+- display_name: Snapchat Audiences
+  slug: snapchat-audiences
+  name: catalog/destinations/snapchat-audiences
+  description: >-
+    The Snapchat Audiences destination lets you sync audiences of users into
+    Snapchat. The Personas product is required to use this destination.
+  hidden: false
+  url: connections/destinations/catalog/snapchat-audiences
+  status: PUBLIC
+  logo:
+    url: 'https://cdn.filepicker.io/api/file/4pYPZIcPTDqRNgD9s6Pb'
+  mark:
+    url: 'https://cdn.filepicker.io/api/file/Up1KJzLMSg27dHkBdb7v'
+  categories:
+  - Advertising
+  components:
+  - type: CLOUD
+  platforms:
+    browser: false
+    server: true
+    mobile: false
+  browserUnbundlingSupported: false
+  browserUnbundlingPublic: true
+  methods:
+    alias: false
+    group: false
+    identify: false
+    page_view: false
+    track: true
+  settings:
+  - name: account
+    display_name: account
+    type: STRING
+    deprecated: false
+    required: true
+    string_validators:
+      regexp: ''
+    description: Choose your Snapchat Ads Account.
+    settings: []
+  connection_modes:
+    device:
+      web: false
+      mobile: false
+      server: false
+    cloud:
+      web: false
+      mobile: true
+      server: true
+  previous_names:
+  - Snapchat Audiences
 - display_name: Spinnakr
   slug: spinnakr
   name: catalog/destinations/spinnakr

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# source cateogries last updated 2021-01-14 
+# source cateogries last updated 2021-01-25 
 items:
 - display_name: Server
   slug: server

src/_data/catalog/sources.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# sources last updated 2021-01-14 
+# sources last updated 2021-01-25 
 items:
 - display_name: .NET
   slug: net

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

@@ -20,7 +20,7 @@ This document was last updated on April 27, 2018. If you notice any gaps, outdat
 
 #### Additional device-mode set up for iOS 14 support
 
-Segment updated the AppsFlyer iOS SDK to use version `6.0 beta` to prepare for tracking changes in iOS 14. The SDK beta version is compatible with the beta version of iOS 14 released by Apple, and supports both AppsFlyer's aggregate attribution, and Apple's `AppTrackingTransperancy` framework, and more. See [the AppsFlyer blog post](https://www.appsflyer.com/blog/privacy-centric-attribution-ios14/) about AppsFlyer's new privacy-centric attribution model.
+Segment updated the AppsFlyer iOS SDK to use version `6.0 beta` to prepare for tracking changes in iOS 14. The SDK beta version is compatible with the beta version of iOS 14 released by Apple, and supports both AppsFlyer's aggregate attribution, and Apple's `AppTrackingTransparency` framework, and more. See [the AppsFlyer blog post](https://www.appsflyer.com/blog/privacy-centric-attribution-ios14/) about AppsFlyer's new privacy-centric attribution model.
 
 To use the latest AppsFlyer SDK to collect IDFAs, do the following:
 

src/connections/destinations/catalog/facebook-conversions-api/index.md

@@ -0,0 +1,5 @@
+---
+title: 'Facebook Conversions API Destination'
+hidden: true
+beta: true
+---

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

@@ -1,17 +1,13 @@
 ---
 title: Intellimize Destination
 beta: true
+hidden: true
 ---
 
 This destination is maintained by the Intellimize team. contact their Support team at [email protected].
 
-## Getting Started
-
-{% include content/connection-modes.md %}
-
-You can enable Intellimize in your Segment Destinations dashboard. You will need to authorize the destination with your Intellimize API key. To retrieve your API key, contact your account representative at Intellimize.
-
-Intellimize supports the `identify`, `page`, `screen`, `track`, `group`, and `alias` methods. Make sure that `identify` calls include a userID. The `identify` call is the most important method to drive improved performance for now. Segment will automatically send these calls to Intellimize's endpoint at https://api.intellimize.co/segment once enabled.
+> warning "The Intellimize destination has been deprecated"
+> The Intellimize Destination was deprecated on 2021-01-25 and is no longer supported or maintained. It is no longer available in the Segment catalog, but remains available to existing users.
 
 ## Identify