Merge branch 'master' into evanSegment-clarify-object-throughput

Author: markzegarelli

scripts/catalog_papi.js

@@ -259,9 +259,6 @@ const updateSources = async () => {
   const hiddenSources = [
     'amp',
     'factual-engine',
-    'kotlin-android',
-    'kotlin',
-    'swift-ios'
   ]
 
   sources.forEach(source => {
@@ -394,7 +391,7 @@ const updateDestinations = async () => {
       const clonedObj = clone(object);
       const targetKey = clonedObj[key];
       delete clonedObj[key];
-    
+
       clonedObj[newKey] = targetKey;
       return clonedObj;
     };

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2021-09-02 
+# destination categories last updated 2021-09-08 
 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-02 
+# destination data last updated 2021-09-08 
 items:
 - display_name: AB Smartly
   name: AB Smartly
@@ -21,9 +21,9 @@ items:
       https://public-segment-devcenter-production.s3.amazonaws.com/3ddac4d4-066c-43c0-b48a-7e48e68140ea.svg
   methods:
     track: true
-    identify: true
-    group: true
-    alias: true
+    identify: false
+    group: false
+    alias: false
     page: true
   platforms:
     browser: true

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source cateogries last updated 2021-09-02 
+# source cateogries last updated 2021-09-08 
 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-02 
+# sources last updated 2021-09-08
 items:
   - display_name: .NET
     slug: net
@@ -355,7 +355,7 @@ items:
     source_type: cloud-app
     description: >-
       Once you have successfully added your credentials we start syncing your
-      Intercom objects to your warehouse. 
+      Intercom objects to your warehouse.
 
 
       We will update Intercom data every ~3 hours.
@@ -439,7 +439,7 @@ items:
   - display_name: Kotlin
     slug: kotlin
     url: connections/sources/catalog/libraries/server/kotlin
-    hidden: true
+    hidden: false
     source_type: server
     description: The hassle-free way to add Segment analytics to your kotlin app (JVM).
     logo:
@@ -449,7 +449,7 @@ items:
   - display_name: Kotlin (Android)
     slug: kotlin-android
     url: connections/sources/catalog/libraries/mobile/kotlin-android
-    hidden: true
+    hidden: false
     source_type: mobile
     description: >-
       The hassle-free way to add Segment analytics to your kotlin app
@@ -507,7 +507,7 @@ items:
     source_type: cloud-app
     description: >-
       Once you have successfully added your credentials we start syncing your
-      Mailchimp objects to your warehouse. 
+      Mailchimp objects to your warehouse.
 
 
       We will update Mailchimp data every ~3 hours.
@@ -733,7 +733,7 @@ items:
     description: >-
       When you enter your Salesforce credentials and hit save, we will sync
       Salesforce standard objects (and their corresponding properties) to any
-      databases you have turned on. 
+      databases you have turned on.
 
 
       Salesforce data will reflect the state of the object at the time of the
@@ -816,7 +816,7 @@ items:
   - display_name: Swift (iOS)
     slug: swift-ios
     url: connections/sources/catalog/libraries/mobile/swift-ios
-    hidden: true
+    hidden: false
     source_type: mobile
     description: >-
       The hassle-free way to add Segment analytics to your swift app (iOS,
@@ -832,7 +832,7 @@ items:
     source_type: cloud-app
     description: >-
       Once you have successfully added your credentials we start syncing your
-      Twilio objects to your warehouse. 
+      Twilio objects to your warehouse.
 
 
       We will update Twilio data every ~3 hours.
@@ -904,7 +904,7 @@ items:
 
       Zendesk data will reflect the state of the object at the time of the sync:
       so if a ticket status goes from `unassigned` to `assigned` between syncs,
-      on its next sync that tickets status will be `assigned`. 
+      on its next sync that tickets status will be `assigned`.
 
 
       We will update Zendesk data every ~3 hours.

src/_data/catalog/warehouse_papi.yml

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

src/_data/sidenav/main.yml

@@ -149,9 +149,8 @@ sections:
     section:
     - path: /connections/destinations
       title: Destinations Overview
-#    - path: /connections/destinations/actions
-#      title: Destination Actions
-# uncomment once fully rolled out
+    - path: /connections/destinations/actions
+      title: Destination Actions
     - path: /connections/destinations/add-destination
       title: Add a Destination
     - path: /connections/destinations/catalog

src/_data/sidenav/strat.yml

@@ -157,3 +157,20 @@ sections:
   - path: /connections/sources/catalog/libraries/mobile/react-native/changelog
     title: Analytics-React-Native Changelog
 
+- slug: kotlin
+  section_title: Analytics-Kotlin Documentation
+  section:
+  - path: /connections/sources/catalog/libraries/mobile/kotlin-android/index
+    title: Analytics-Kotlin (Mobile)
+  - path: /connections/sources/catalog/libraries/server/kotlin/index
+    title: Analytics-Kotlin (Server)
+  - path: /connections/sources/catalog/libraries/mobile/kotlin-android/migration
+    title: Analytics-Kotlin Migration Guide
+
+- slug: swift
+  section_title: Analytics-Swift Documentation
+  section:
+  - path: /connections/sources/catalog/libraries/mobile/swift-ios/index
+    title: Analytics-Swift
+  - path: /connections/sources/catalog/libraries/mobile/swift-ios/migration
+    title: Analytics-Swift Migration Guide

src/_sass/components/_markdown.scss

@@ -144,7 +144,12 @@
         top: 0;
         left: 0;
       }
-
+      div.highlighter-rouge {
+        margin: 15px auto;
+      }
+      table {
+        margin: 15px auto;
+      }
       &>ul,
       ol {
         margin-top: 0;

src/connections/destinations/catalog/ab-smartly/index.md

@@ -7,13 +7,11 @@ title: AB Smartly Destination
 
 This destination is maintained by A/B Smartly. For any issues with the destination, [contact A/B Smartly's Support](mailto:[email protected]).
 
-> note "Note:"
-> The A/B Smartly Destination is in beta as the team is actively developing the destination. To join the beta program or to provide feedback to help improve A/B Smartly's Destination and documentation, [contact A/B Smartly's support team](mailto:[email protected]).
 
 
 ## Implementation Prerequisite
 
-A/B Smartly works differently than other Segment destinations. Because A/B Smartly SDKs are used to modify and deliver experiences to users, you must be implement them at a point in your website or app that allows them to make visual modifications for users.
+A/B Smartly works differently than other Segment destinations. Because A/B Smartly SDKs are used to modify and deliver experiences to users, you must implement them at a point in your website or app that allows them to make visual modifications for users.
 
 A/B Smartly requires you to integrate the A/B Smartly SDKs natively, before the Segment snippet or implementation.
 
@@ -33,7 +31,7 @@ Segment provides specific implementation details for A/B Smartly in the sections
 6. If the integration requests for an Application name go to your A/B Smartly dashboard (`https://your-org-name.absmartly.com/application/create`) and create an Application named "Segment", or whatever you would like to call it. Use that name in the Application field of the integration settings.
 7. Add also your A/B Smartly Collector endpoint. It's the same endpoint that you are using in all your A/B Smartly SDKs.
 8. Enter the environment from your Environment list (`https://your-org-name.absmartly.com/environment/list`) that should receive your Segment data. Most likely it will be the production one.
-9. And finally a mapping of Segment Identities to A/B Smartly Units(`https://your-org-name.absmartly.com/unit/list`). You should map all your Segment identities that you would like to use in your A/B tests to the units that you already have in A/B Smartly. Check your unit list on A/B Smartly(`https://your-org-name.absmartly.com/unit/list`).
+9. And finally a mapping of Segment Identities to A/B Smartly Units(`https://your-org-name.absmartly.com/unit/list`). You should map all of your Segment identities that you would like to use in your A/B tests to the units that you already have in A/B Smartly. Users must map all the identity types, but not for the individual users. Map all of your ids in your Unit List(`https://your-org-name.absmartly.com/unit/list`).
 10. Optionally go to "Goal Mapping" and start adding the track calls that you would like to see showing up on A/B Smartly as goals. You only need to create a name mapping if the name of the goal on A/B Smartly's platform is different from the name of the track call in Segment.
 
 
@@ -46,7 +44,7 @@ Take a look at the [Page method documentation](/docs/connections/spec/page/) to
 analytics.page()
 ```
 
-Segment sends Page calls to A/B Smartly as a `pageview` goal. The goal name is`<page_name>_pageview`. The page name is lower-cased and any spaces or special characters are replaced with underscores. For example, a view of the "Home" page triggers the `home_pageview` goal. If the goal doesn't exist in the A/B Smartly web console, it is ignored. 
+Segment sends Page calls to A/B Smartly as a `pageview` goal. The goal name is`<page_name>_pageview`. The page name is lower-cased and any spaces or special characters are replaced with underscores. For example, a view of the "Home" page triggers the `home_pageview` goal. If the goal doesn't exist in the A/B Smartly web console, it is ignored.
 
 
 ## Screen