Merge pull request #1370 from segmentio/current-branch-grazi

Current branch grazi

Author: markzegarelli

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-21 
 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-21 
 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
@@ -17748,15 +17745,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 +17778,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 +18333,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

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-21 
 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-21 
 items:
 - display_name: .NET
   slug: net

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/signl4-alerting/index.md

@@ -0,0 +1,94 @@
+---
+title: SIGNL4 Alerting
+rewrite: true
+---
+
+[SIGNL4](https://www.signl4.com) is a lightweight, app-based alerting service of operational teams supporting app push, SMS text and voice call including tracking, escalation, collaboration and duty planning.
+
+When incidents happen, SIGNL4 can alert your teams, engineers, sales, marketing or workers ‘in the field’. SIGNL4 helps to know what is going on – from anywhere and anytime.
+
+This destination is maintained by Derdack SIGNL4. For any issues with the destination, [contact their support team](mailto:[email protected]).
+
+{% include content/beta-note.md %}
+
+## Getting Started
+
+{% include content/connection-modes.md %} 
+
+1. From the Destinations catalog page in your Segment Workspace, click Add Destination.
+2. Search for “SIGNL4” in the Destinations Catalog, and select the SIGNL4 Alerting destination.
+3. Choose which Source should send data to the “SIGNL4 Alerting” destination.
+4. Enter the “API Key” in the “SIGNL4 Alerting” destination settings in your Segment Workspace, this is your SIGNL4 team secret and the first part of your SIGNL4 email address.
+
+Ife you do not have SIGNL4 installed already, you can download the SIGNL4 App from the [Google Play Store](https://play.google.com/store/apps/details?id=com.derdack.signl4) or from the [Apple App Store](https://itunes.apple.com/us/app/signl4/id1100283480). Alternatively, you can get started on the [SIGNL4 web site](https://www.signl4.com/free-trial-test/). Once registered you will get an email with your SIGNL4 API information which includes your SIGNL4 team secret. This is the first part of your SIGNL4 email address ([email protected]).
+
+## Page
+
+If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like:
+
+```js
+analytics.page()
+```
+
+Segment sends Page calls to SIGNL4 Alerting as a `pageview`, which can also be seen under Signls. 
+
+
+## Screen
+
+If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](https://segment.com/docs/connections/spec/screen/) to learn about what it does. An example call would look like:
+
+```obj-c
+[[SEGAnalytics sharedAnalytics] screen:@"Home"];
+```
+
+Segment sends Screen calls to SIGNL4 Alerting as a `screenview`, which can also be seen under Signls. 
+
+
+## Identify
+
+If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like:
+
+```js
+analytics.identify('userId123', {
+  email: '[email protected]'
+});
+```
+
+Segment sends Identify calls to SIGNL4 Alerting as an `identify` event, which can also be seen under Signls.
+
+
+## Track
+
+If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like:
+
+```js
+analytics.track('Login Button Clicked')
+```
+
+Segment sends Track calls to SIGNL4 Alerting as a `track` event, which can also be seen under Signls.
+
+## Group
+
+If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](https://segment.com/docs/connections/spec/group/) to learn about what it does. An example call would look like:
+
+```js
+analytics.group('0e8c78ea9d97a7b8185e8632', {
+  name: 'Initech',
+  industry: 'Technology',
+  employees: 329,
+  plan: 'enterprise',
+  "total billed": 830
+});
+```
+
+Segment sends Group calls to SIGNL4 Alerting as a `group` event, which can also be seen under Signls.
+
+## Alias
+
+If you aren't familiar with the Segment Spec, take a look at the [Alias method documentation](https://segment.com/docs/connections/spec/alias/) to learn about what it does. An example call would look like:
+
+```js
+analytics.alias("507f191e81");
+```
+
+Segment sends Alias calls to SIGNL4 Alerting as an `alias` event, which can also be seen under Signls.