Merge branch 'master' into link-checker

Author: markzegarelli

devguide.md

@@ -21,6 +21,17 @@ If using OSX:
   * Run server, `make dev`
   * Visit http://localhost:4000/docs/
 
+## Changing a DevCenter Destination's name
+
+Occasionally, a destination will change names. This shouldn't be too difficult to handle, but make sure you do the following:
+- Change the name of the file **to match destination's new slug**
+- Check in the Partner Portal that the name change has appropriately filled out the `previousNames` field. There should be two (or more if this has aliases/many name changes).
+- Add a `redirect_from` frontmatter item, with the url of the old doc. This funnels anyone arriving at the old page from a link outside the docs site to the page at the new name.
+- Run a `make catalog` to pick up the name change.
+- Run `make docs` and test that:
+  1. The page shows up correctly at the url you specified using the new slug.
+  2. The programmatic content appears (cmodes, settings, previous names)
+  3. The redirect from the old page URL works.
 
 
 ## Developer information

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# destination categories last updated 2020-08-12 
+# destination categories last updated 2020-08-28 
 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 2020-08-12 
+# destination data last updated 2020-08-28 
 items:
 - display_name: ActiveCampaign
   slug: activecampaign
@@ -2670,31 +2670,6 @@ items:
     page_view: false
     track: true
   settings:
-  - name: obscureTextEmails
-    display_name: Obscure text emails
-    type: BOOLEAN
-    deprecated: false
-    required: false
-    description: Do not record email addresses
-    settings: []
-  - name: obscureTextNumbers
-    display_name: Obscure text numbers
-    type: BOOLEAN
-    deprecated: false
-    required: false
-    description: Do not record any numeric text
-    settings: []
-  - name: projectId
-    display_name: Project ID
-    type: STRING
-    deprecated: false
-    required: false
-    string_validators:
-      regexp: ''
-    description: >-
-      The ID associated with your project. You can find in Preferences ->
-      Projects in your Asayer app.
-    settings: []
   - name: siteId
     display_name: Site ID
     type: STRING
@@ -2703,8 +2678,8 @@ items:
     string_validators:
       regexp: ''
     description: >-
-      The ID associated with your website. You can find in Preferences -> Sites
-      -> Tracking Code in your Asayer app.
+      The ID associated with your project. You can find in Preferences ->
+      Projects in your Asayer app.
     settings: []
   connection_modes:
     device:
@@ -5443,7 +5418,7 @@ items:
     alias: false
     group: false
     identify: true
-    page_view: false
+    page_view: true
     track: true
   settings:
   - name: apiKey
@@ -11919,26 +11894,27 @@ items:
       server: true
   previous_names:
   - Kustomer
-- display_name: LaunchDarkly-subscription
-  slug: launchdarkly-subscription
-  name: catalog/destinations/launchdarkly-subscription
+- display_name: LaunchDarkly Events
+  slug: launchdarkly-events
+  name: catalog/destinations/launchdarkly-events
   description: >-
     This destination sends track events to LaunchDarkly experiments.
     LaunchDarkly is a feature management platform that empowers development
     teams to safely deliver and control software through feature flags. 
   hidden: false
-  url: connections/destinations/catalog/launchdarkly-subscription
+  url: connections/destinations/catalog/launchdarkly-events
   status: PUBLIC_BETA
   logo:
     url: >-
-      https://public-segment-devcenter-production.s3.amazonaws.com/9d3b780d-d6a6-413d-b606-49ce7b9af1a9.svg
+      https://public-segment-devcenter-production.s3.amazonaws.com/92c1e362-6226-441c-bd09-8ccb93c0b955.svg
   mark:
     url: >-
-      https://public-segment-devcenter-production.s3.amazonaws.com/e15902da-fbab-4789-82a0-09da26f51d8a.svg
+      https://public-segment-devcenter-production.s3.amazonaws.com/c590eaef-de6d-46e7-b208-1b4fb3568f47.svg
   categories:
   - A/B Testing
   - Analytics
-  components: []
+  components:
+  - type: CLOUD
   platforms:
     browser: true
     server: true
@@ -11960,20 +11936,20 @@ items:
     string_validators:
       regexp: '^.{8,}$'
     description: >-
-      Generate a token in the Authorization tab in LaunchDarkly Account
-      Settings.
+      Find and copy the client-side ID from your default project in LaunchDarkly
+      Account Settings.
     settings: []
   connection_modes:
     device:
       web: false
       mobile: false
       server: false
     cloud:
-      web: false
-      mobile: false
-      server: false
+      web: true
+      mobile: true
+      server: true
   previous_names:
-  - LaunchDarkly-subscription
+  - LaunchDarkly Events
 - display_name: Lazy Lantern
   slug: lazy-lantern
   name: catalog/destinations/lazy-lantern
@@ -13050,6 +13026,13 @@ items:
       required: false
       description: Map your Segment properties to the Marketo Activity Fields
       settings:
+      - name: primaryKey
+        display_name: Set as Primary Key
+        type: BOOLEAN
+        deprecated: false
+        required: false
+        description: Mark this property as the Primary field in Marketo.
+        settings: []
       - name: segmentProperty
         display_name: Segment Property Name
         type: STRING
@@ -13085,13 +13068,6 @@ items:
           - date
         description: Enter the Marketo Field type.
         settings: []
-      - name: primaryKey
-        display_name: Set as Primary Key
-        type: BOOLEAN
-        deprecated: false
-        required: false
-        description: Mark this property as the Primary field in Marketo.
-        settings: []
     - name: event
       display_name: Segment Event Name
       type: STRING
@@ -17099,13 +17075,6 @@ items:
       required: false
       description: Map your Segment properties to Responsys Columns
       settings:
-      - name: primaryKey
-        display_name: Set as Primary Key
-        type: BOOLEAN
-        deprecated: false
-        required: false
-        description: Mark this property as a Primary Key in Responsys.
-        settings: []
       - name: columns
         display_name: Segment Property Name
         type: STRING
@@ -17141,6 +17110,13 @@ items:
           - TIMESTAMP
         description: Enter the Responsys column type.
         settings: []
+      - name: primaryKey
+        display_name: Set as Primary Key
+        type: BOOLEAN
+        deprecated: false
+        required: false
+        description: Mark this property as a Primary Key in Responsys.
+        settings: []
     - name: mapEmail
       display_name: Map Email
       type: BOOLEAN
@@ -21697,6 +21673,61 @@ items:
   previous_names:
   - useriq
   - UserIQ
+- display_name: UserLeap
+  slug: userleap
+  name: catalog/destinations/userleap
+  description: >-
+    UserLeap is a microsurvey platform that continuously identifies
+    opportunities to build better experiences. Gain clarity into customer needs
+    and grow faster.
+  hidden: false
+  url: connections/destinations/catalog/userleap
+  status: PUBLIC_BETA
+  logo:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/2ad4508d-5be6-4358-a7f7-45b97dd54d22.svg
+  mark:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/b6a1db0f-1b55-4651-9cc5-d78d8365a447.svg
+  categories:
+  - Customer Success
+  - Analytics
+  - Surveys
+  - Personalization
+  components: []
+  platforms:
+    browser: true
+    server: true
+    mobile: true
+  browserUnbundlingSupported: false
+  browserUnbundlingPublic: false
+  methods:
+    alias: true
+    group: false
+    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: 'Find your API key here https://app.userleap.com/settings/installation'
+    settings: []
+  connection_modes:
+    device:
+      web: false
+      mobile: false
+      server: false
+    cloud:
+      web: false
+      mobile: false
+      server: false
+  previous_names:
+  - UserLeap
 - display_name: UserVoice
   slug: uservoice
   name: catalog/destinations/uservoice

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# source cateogries last updated 2020-08-12 
+# source cateogries last updated 2020-08-28 
 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 2020-08-12 
+# sources last updated 2020-08-28 
 items:
 - display_name: .NET
   slug: net

src/_data/sidenav/main.yml

@@ -186,6 +186,8 @@ sections:
         title: Data Lakes vs Warehouses
       - path: /connections/storage/catalog/data-lakes
         title: Set up Data Lakes
+      - path: /connections/storage/data-lakes/sync-reports
+        title: Sync Reports and error reporting
     - section_title: Data Warehouses
       slug: connections/storage/warehouses
       section:
@@ -223,6 +225,8 @@ sections:
     title: Integration Error Codes
   - path: /connections/schema-unique-limits
     title: Are there limits on my Segment Schema?
+  - path: /connections/rate-limits
+    title: Rate Limits and SLA
 - section_title: Personas
   section:
   - path: /personas

src/connections/destinations/catalog/launchdarkly-subscription/index.md renamed to src/connections/destinations/catalog/launchdarkly-events/index.md

@@ -1,6 +1,7 @@
 ---
 title: LaunchDarkly Events Destination
 rewrite: true
+redirect_from: /connections/destinations/catalog/launchdarkly-subscription
 ---
 LaunchDarkly is a feature management platform that empowers development teams to safely deliver and control software through feature flags.
 

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

@@ -190,7 +190,7 @@ If you're not familiar with the Segment Specs, take a look to understand what th
 ```javascript
 analytics.alias('newUserId')
 ```
-**Important:** Calling `alias` is required for Mixpanel in all libraries in order to connect anonymous visitors to identified users.
+**Important:** Calling `alias` used to be required for Mixpanel in all libraries in order to connect anonymous visitors to identified users. However, with the release of Mixpanel's New [identity merge feature](https://help.mixpanel.com/hc/en-us/articles/360039133851#enable-id-merge) this is no longer necessary if you enable the ID Merge Setting under Mixpanel -> Project Settings -> Identity Merge. **If you aren't using this setting, please continue with the instructions below.**
 
 As soon as you have a `userId` for a visitor that was previously anonymous you'll need to [`alias`](/docs/connections/spec/alias/) their old anonymous `id` to the new `userId`. In Mixpanel only **one** anonymous user history can be merged to **one** identified user. For that reason you should only call `alias` once, right after a user registered, but before the first `identify`.
 

src/connections/destinations/catalog/personas-display-video-360/index.md

@@ -88,7 +88,13 @@ To create audiences based on website browsing events, set up the Segment-to-Goog
 1. Create a “[Javascript Website](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/)” source in Segment.
 2. Follow [the Analytics.js Quickstart guide](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/quickstart/).
 3. In your workspace, click **Catalog**, and search for **DoubleClick Floodlight**.
-4. Connect the destination to the source you created in the first step, and leave all settings blank.
+4. Select the source you created in the first step, so that it sends data to the Doubleclick Floodlight destination.
+5. Enter or enable the following destination settings for the Doubleclick destination:
+    - Set **Get DoubleclickId** to `On`
+    - For the **Google Network Id** enter `segment`.
+    - Enter the write key from the source you created in step 1 as your **Segment Write Key**.
+      You can get this from source's Settings page, and usually looks something like `k8mJ77kAbCNMOgmj1OFfVphvqXd8mLCx.
+5. Turn the DoubleClick Floodlight destination on.
 
 > success ""
 > **Tip**: The field "DoubleClick Advertiser ID” is required, but you can enter any value.

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

@@ -0,0 +1,63 @@
+---
+title: UserLeap
+rewrite: true
+---
+
+[UserLeap](https://userleap.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is a microsurvey platform that continuously identifies opportunities to build better experiences. Gain clarity into customer needs and grow faster.
+
+This destination is maintained by UserLeap. For any issues with the destination, contact [the UserLeap 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 "UserLeap" in the Destinations Catalog, and select the UserLeap destination.
+3. Choose which Source should send data to the UserLeap destination.
+4. Go to the [UserLeap dashboard](https://app.userleap.com/settings/installation), find and copy the **API key**.
+5. Enter the UserLeap API Key that you copied in the UserLeap destination settings in Segment.
+
+**Note**: UserLeap's Segment integration does not support In-Product Surveys
+
+## 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', {
+  firstName: 'Laura',
+  lastName: 'Gibbon'
+})
+```
+
+Use Segment's Identify method to identify your users in UserLeap. Segment `traits` map to UserLeap `attributes`.
+
+**Important:** Only Identify calls can create new users in UserLeap.
+
+## 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('Button Clicked');
+```
+
+Use Track calls to track events and use them as filtering criteria for your Surveys.
+
+Create Triggered Events in your UserLeap [Events dashboard](https://app.userleap.com/events) and map them to your Segment Track event names before you start sending Segment data to UserLeap.
+
+## 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 UserLeap as a `pageview` which you can use as filtering criteria for your surveys.
+
+Add Page URLs  in your UserLeap [Events dashboard](https://app.userleap.com/events) and map them to your Segment Page call's `properties.url` field before you start sending Segment data to UserLeap.
+
+## 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');
+```