Merge pull request #61 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-10-11 
+# destination categories last updated 2021-10-13 
 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-10-11 
+# destination data last updated 2021-10-13 
 items:
 - display_name: 2mee
   name: 2mee
@@ -7753,7 +7753,7 @@ items:
   components:
   - code: https://github.com/segmentio/integrations/tree/master/integrations/hubspot
     type: server
-  browserUnbundlingSupported: true
+  browserUnbundlingSupported: false
   browserUnbundlingPublic: true
   replay: false
   connection_modes:
@@ -20682,6 +20682,58 @@ items:
     description: "Please set a Startdeliver user custom field to match a Segment event on. You can find your custom fields here –\_https://app.startdeliver.com/settings/fields."
     required: true
     label: Startdeliver user custom field to match on
+- display_name: Statsig
+  name: Statsig
+  slug: statsig
+  hidden: false
+  url: connections/destinations/catalog/statsig
+  previous_names:
+  - Statsig
+  website: https://www.statsig.com
+  status: PUBLIC_BETA
+  categories:
+  - A/B Testing
+  - Analytics
+  logo:
+    url: https://cdn.filepicker.io/api/file/LC02PCIyQaR7Lpt0Ulk1
+  mark:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/476760b5-b915-42ea-9682-ce1217f47af0.svg
+  methods:
+    track: true
+    identify: true
+    group: true
+    alias: true
+    page: true
+  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: >-
+      Copy the Statsig Server Secret Key for your Statsig Project here:
+      https://console.statsig.com/api_keys
+    required: true
+    label: API Key
 - display_name: Stitch Data
   name: Stitch Data
   slug: stitch-data

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source cateogries last updated 2021-10-11 
+# source cateogries last updated 2021-10-13 
 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-10-11 
+# sources last updated 2021-10-13 
 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-10-11 
+# warehouse data last updated 2021-10-13 
 items:
 - display_name: Azure SQL Data Warehouse
   slug: azuresqldw

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

@@ -0,0 +1,75 @@
+---
+title: Statsig Destination
+---
+
+[Statsig](https://www.statsig.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) helps companies safely A/B test features in production before rolling them out, avoiding product debates and costly mistakes when shipping out new features. Statsig automates the grunt work so that A/B tests are always running automatically and you always know how your features are performing.
+
+This destination is maintained by Statsig. For any issues with the destination, [contact the Statsig 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 “Statsig” in the Destinations Catalog, and select the “Statsig” destination.
+3. Choose which Source(s) should send data to the “Statsig” destination.
+4. Go to the [Statsig dashboard](https://console.statsig.com/api_keys), find and copy the Statsig "Server Secret Key”.
+5. Enter the Statsig “Server Secret Key” in the “Statsig” destination settings in Segment.
+
+## Supported methods
+
+Statsig supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
+
+### Page
+
+Send [Page](/docs/connections/spec/page) calls to Statsig. For example:
+
+```js
+analytics.page("Home")
+```
+
+Segment sends Page calls to Statsig as:
+
+```js
+{
+  "event": "segment_page:Home"
+}
+```
+
+These events are included in any experiments running on Statsig and will show up in all Metrics data.
+
+### Screen
+
+Send [Screen](/docs/connections/spec/screen) calls to Statsig. For example:
+
+```obj-c
+[[SEGAnalytics sharedAnalytics] screen:@"Home"];
+```
+
+Segment sends Screen calls to Statsig as:
+
+```js
+{
+  "event": "segment_screen:Home"
+}
+```
+
+These events are included in any experiments running on Statsig and will show up in all Metrics data.
+
+### Track
+
+Send [Track](/docs/connections/spec/track) calls to Statsig. For example:
+
+```js
+analytics.track('Login Button Clicked')
+```
+
+Segment sends Track calls to Statsig as:
+
+```js
+{
+  "event": "segment_track:Login Button Clicked"
+}
+```
+
+These events are included in any experiments running on Statsig and will show up in all Metrics data.