Merge pull request #22 from segmentio/repo-sync

repo sync

Author: bot-docsteam

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2021-09-23 
+# destination categories last updated 2021-09-29 
 items:
 - display_name: A/B Testing
   slug: a-b-testing

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2021-09-23 
+# destination data last updated 2021-09-29 
 items:
 - display_name: 2mee
   name: 2mee
@@ -1449,7 +1449,7 @@ items:
     label: Role Address
   - name: secretId
     type: string
-    defaultValue: ''
+    defaultValue: '#SEGMENT_WORKSPACE_ID'
     description: >-
       The External ID to your IAM role. This value is read-only. Reach out to
       support if you wish to change it. This value is also a secret and should
@@ -1548,7 +1548,7 @@ items:
     label: Role Address
   - name: secretId
     type: string
-    defaultValue: ''
+    defaultValue: '#SEGMENT_WORKSPACE_ID'
     description: >-
       The External ID to your IAM role. This value is read-only. Reach out to
       support if you wish to change it. This value is also a secret and should
@@ -1664,7 +1664,7 @@ items:
     label: Events
   - name: externalId
     type: string
-    defaultValue: ''
+    defaultValue: '#SEGMENT_WORKSPACE_ID'
     description: >-
       This is an optional string Segment will use to assume the role provided to
       invoke the Lambda function. If this setting is not defined, we'll use the
@@ -1923,7 +1923,7 @@ items:
     label: Events
   - name: externalId
     type: string
-    defaultValue: ''
+    defaultValue: '#SEGMENT_WORKSPACE_ID'
     description: >-
       This is an optional string Segment will use to assume the role provided to
       invoke the Lambda function. If this setting is not defined, we'll use the
@@ -18917,7 +18917,9 @@ items:
   - name: repeatKeys
     type: array
     defaultValue: []
-    description: This is the array of source write keys you want to repeat data into. You can have up to 20 write keys.
+    description: >-
+      This is the array of source write keys you want to repeat data into. You
+      can have up to 20 write keys.
     required: true
     label: Write Keys
   - name: writeKeyAllowed
@@ -20152,6 +20154,60 @@ items:
       integration panel within ScopeAI.
     required: true
     label: API Key
+- display_name: Screeb
+  name: Screeb
+  slug: screeb
+  hidden: false
+  url: connections/destinations/catalog/screeb
+  previous_names:
+  - Screeb
+  website: https://screeb.app
+  status: PUBLIC_BETA
+  categories:
+  - Analytics
+  - Customer Success
+  - Enrichment
+  logo:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/d8c2ed86-7de8-4165-9aed-e7da70e8ee77.svg
+  mark:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/14298557-b66b-4019-a5c5-d3366cd0f10e.svg
+  methods:
+    track: true
+    identify: true
+    group: false
+    alias: true
+    page: false
+  platforms:
+    browser: true
+    mobile: true
+    server: true
+  components: []
+  browserUnbundlingSupported: false
+  browserUnbundlingPublic: false
+  replay: false
+  connection_modes:
+    device:
+      web: false
+      mobile: false
+      server: false
+    cloud:
+      web: false
+      mobile: false
+      server: false
+    summary: No connection mode information available.
+    cmode_type: none
+    case: '0'
+  settings:
+  - name: apiKey
+    type: string
+    defaultValue: ''
+    description: >-
+      You can find your Segment token in the integration section of the Screeb
+      platform
+    required: true
+    label: API Key
 - display_name: Scuba Analytics
   name: Scuba Analytics
   slug: scuba-analytics
@@ -20162,7 +20218,7 @@ items:
   - Interana
   - Scuba Analytics
   website: https://www.interana.com/segment
-  status: PUBLIC_BETA
+  status: PUBLIC
   categories:
   - Analytics
   - Attribution

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source cateogries last updated 2021-09-23 
+# source cateogries last updated 2021-09-29 
 items:
   - display_name: A/B Testing
     slug: a-b-testing

src/_data/catalog/sources.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2021-09-23 
+# sources last updated 2021-09-29 
 items:
   - display_name: .NET
     slug: net

src/_data/catalog/warehouse_papi.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# warehouse data last updated 2021-09-23 
+# warehouse data last updated 2021-09-29 
 items:
 - display_name: Azure SQL Data Warehouse
   slug: azuresqldw

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

@@ -0,0 +1,60 @@
+---
+title: Screeb Destination
+rewrite: true
+---
+
+[Screeb](https://screeb.app/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) helps teams to get actionnable feedback without ruining user experience.
+
+This destination is maintained by Screeb. For any issues with the destination, [contact the Screeb Support team](mailto:[email protected]).
+
+## Getting Started
+
+{% include content/connection-modes.md %} 
+
+1. From the Destinations catalog page in the Segment App, click **Add Destination**.
+2. Search for "Screeb" in the Destinations Catalog, and select the "Screeb" destination.
+3. Choose which Source should send data to the "Screeb" destination.
+4. Go to the [Screeb platform](https://admin.screeb.app/) > Integration, and install the Segment connector.
+5. Find and copy the "API Key".
+6. Enter the "API Key" in the "Screeb" destination settings in Segment.
+
+## 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 Screeb as an `identity` event.
+
+The traits provided along with the identity can be listed on the [Screeb platform](https://admin.screeb.app/) > Settings. Surveys can be customized or displayed according to identity properties.
+
+
+## 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 Screeb as an `event.track` event.
+
+The provided events can be listed on the [Screeb platform](https://admin.screeb.app/) > Settings. Surveys can be displayed according to event rules.
+
+## 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('newUserId')
+```
+
+Segment sends Alias calls to Screeb as an `identity.alias` event.
+
+**Important:** After this call, the Screeb respondent will have 3 aliases for the same identity: previous userId, anonymousId and `newUserId`. Merge of responses and events will be added in the future.
+
+---