Merge branch 'master' into dependabot/npm_and_yarn/hosted-git-info-2.8.9

Author: markzegarelli

README.md

@@ -189,6 +189,7 @@ Each piece of frontmatter does something special!
 #### Content-related frontmatter
 - `beta`: default false. When true, show an "in beta" warning in the page layout (see the warning in `_includes/content/beta-note.md`)
 - `rewrite`: defaults to false. This is a legacy frontmatter flag that comes from the old `site-docs` repo, and which labels any destination that was rewritten in ~2018 to a standardized template. It disables the duplicate "connection modes" table that would otherwise show up in the boilerplate content at the end of the page.
+- `hide-dossier`: defaults to false. When true, hides the "quick info" box at the top of a destination page.
 - `hide-boilerplate`: defaults to false. When true, none of the content from `destination-footer.md` is appended to the destination page.
 - `hide-cmodes`: defaults to false. A renaming of "rewrite" for more clarity, hides the connection modes table in the boilerplate.
 - `hide-personas-partial`: defaults to false. When true, hides the section of content from `destination-footer.md` that talks about being able to receive personas data.

netlify.toml

@@ -6,7 +6,7 @@
 
 [context.deploy-preview]
   command = "yarn develop"
-  ignore = "git log -1 --pretty=%B | ( grep -q '\\[netlify\\-ignore\\]' )"
+  ignore = "./scripts/ignore.sh"
 
 [[redirects]]
   from = "/docs/*"

scripts/ignore.sh

@@ -0,0 +1,27 @@
+#!/usr/bin/env bash
+
+# grab the latest entry from git log
+log=$(env -i git log -1 --pretty=%B)
+
+# run a series of checks for common reasons that we shouldn't preview build.
+# if no checks match, exit with code 1 to run the build
+
+# ignore for simple typo fixes
+if echo "$log" | grep -q 'typo'; then
+exit
+# ignore link / url updates
+elif echo "$log" | grep -q 'link'; then
+exit
+# ignore when the ignore tag is explicitly added
+elif echo "$log" | grep -q 'netlify\-ignore'; then
+exit 
+# ignore dependabot updates
+elif echo "$log" | grep -q 'dependabot'; then
+exit
+# ignore when master is merged into a branch
+elif echo "$log" | grep -q 'Merge branch \SMaster\S'; then
+exit
+else
+exit 1
+fi
+

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PLATFORM API. DO NOT EDIT
-# destination data last updated 2021-05-07 
+# destination data last updated 2021-05-12 
 items:
 - display_name: ActiveCampaign
   slug: activecampaign
@@ -5281,17 +5281,18 @@ items:
   description: >-
     Cliff.ai automatically monitors your metrics, looks out for unexpected
     behaviour and notifies you immediately about it.
-  hidden: true
+  hidden: false
   status: PUBLIC_BETA
   previous_names:
   - Cliff
   logo:
     url: >-
-      https://public-segment-devcenter-production.s3.amazonaws.com/6bf01c63-71fc-4da2-9643-c070eaae3c99.svg
+      https://public-segment-devcenter-production.s3.amazonaws.com/5e874601-08cc-4217-b938-ab715153caf7.svg
   mark:
     url: >-
       https://public-segment-devcenter-production.s3.amazonaws.com/cb3f2dd4-01bc-451c-92a3-18db9c3e562b.svg
   categories:
+  - Analytics
   - Performance Monitoring
   methods:
     alias: false
@@ -19135,15 +19136,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
@@ -19177,6 +19169,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
@@ -24872,6 +24873,60 @@ items:
       libraries. You can find your `auth_token` on <a
       href="http://www.getvero.com/account">Vero's account page</a>.
     settings: []
+- display_name: Vespucci
+  slug: vespucci
+  name: catalog/destinations/vespucci
+  url: connections/destinations/catalog/vespucci
+  description: Vespucci is a technology that turns data into insights.
+  hidden: false
+  status: PUBLIC_BETA
+  previous_names:
+  - Vespucci
+  logo:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/64713dea-0a55-4641-b107-8689604761c2.svg
+  mark:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/0535cde9-3bdf-4e72-a9b9-b092297ae675.svg
+  categories:
+  - A/B Testing
+  - Analytics
+  - Heatmaps & Recordings
+  methods:
+    alias: false
+    group: false
+    identify: true
+    page_view: true
+    track: true
+  components: []
+  platforms:
+    browser: true
+    server: true
+    mobile: true
+  browserUnbundlingSupported: false
+  browserUnbundlingPublic: 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
+    display_name: API Key
+    type: STRING
+    deprecated: false
+    required: true
+    string_validators:
+      regexp: '^.{8,}$'
+    description: You can find your API key on the Vespucci dashboard.
+    settings: []
 - display_name: Vidora
   slug: vidora
   name: catalog/destinations/vidora
@@ -27137,6 +27192,65 @@ items:
       Look for the [API Key](https://app.hydra.ai/settings#api_info) under the
       settings menu, Integrations.
     settings: []
+- display_name: journy io
+  slug: journy-io
+  name: catalog/destinations/journy-io
+  url: connections/destinations/catalog/journy-io
+  description: >-
+    Empower your marketing, sales and support teams with actionable customer
+    insights, needed to improve conversions, increase sales, and reduce churn,
+    right in the tools they already use.
+  hidden: false
+  status: PUBLIC_BETA
+  previous_names:
+  - journy io
+  logo:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/f75def40-3bed-413e-bc20-3a4b9fd2c285.svg
+  mark:
+    url: >-
+      https://public-segment-devcenter-production.s3.amazonaws.com/5e1d3591-f51d-4a61-8daa-a5cb5fe64ef4.svg
+  categories:
+  - Enrichment
+  - Personalization
+  - Raw Data
+  methods:
+    alias: true
+    group: true
+    identify: true
+    page_view: true
+    track: true
+  components: []
+  platforms:
+    browser: true
+    server: true
+    mobile: true
+  browserUnbundlingSupported: false
+  browserUnbundlingPublic: 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
+    display_name: API Key
+    type: STRING
+    deprecated: false
+    required: true
+    string_validators:
+      regexp: '^.{8,}$'
+    description: >-
+      Add Segment as source in the connections and choose "Manual setup" to copy
+      the API key.
+    settings: []
 - display_name: mabl
   slug: mabl
   name: catalog/destinations/mabl

src/_includes/content/current-version.html

@@ -7,12 +7,12 @@
 {% for release in changelog.releases limit:1 %}
 
 
-
+{% unless release.url == "" %}
 <div class="current-version">
 
 <p>Current Version: <a href="{{release.url}}" target="_blank">{{release.version}}</a></p>
 <p>Release Date: {{release.date | date: "%b %d, %Y" }}</p>
-{% endfor %}
+
 <div class="links">
 <a href="https:///github.com/segmentio/{{page.repo}}" target="_blank"><img src="/docs/images/github.svg" /></a>
 <a href="https:///github.com/segmentio/{{page.repo}}/tags.atom" target="_blank"><img src="/docs/images/atom.svg" /></a>
@@ -21,3 +21,5 @@
 {% endif %}
 </div>
 </div>
+{% endunless %}
+{% endfor %}

src/connections/destinations/add-destination.md

@@ -131,7 +131,7 @@ You can add multiple instances of a destination using the Segment Config API. Se
 - **Mobile sources, and the legacy Project source, cannot connect to multiple instances of a destination.**
     - **Warning**: If you bundle one instance of a destination in a mobile source but have other instances of that destination connected to that source you might see unexpected and inconsistent data.
 - **You can connect a source to up to 10 instances of a destination if all of the instances use cloud-mode.** Destinations using cloud-mode receive data directly from the Segment servers.
-- **Non-mobile sources can only connect to one *device-mode* instance of a destination, in addition to unlimited cloud-mode instances.** A web browser device-mode instance of a destination receives data directly from the user’s browser (instead of through the Segment servers), by bundling a copy of destination’s code with the Segment SDK. Segment can’t bundle multiple copies of the destination SDK and so it can’t send data to multiple instances of the destination from the browser.
+- **Non-mobile sources can only connect to one *device-mode* instance of a destination, in addition to up to 10 cloud-mode instances.** A web browser device-mode instance of a destination receives data directly from the user’s browser (instead of through the Segment servers), by bundling a copy of destination’s code with the Segment SDK. Segment can’t bundle multiple copies of the destination SDK and so it can’t send data to multiple instances of the destination from the browser.
 - **You cannot connect a source to more than one instance of a destination that operates in device-mode only**. These destinations can only accept data from code directly on the user’s device, and Segment cannot include duplicates of that code for a single source.
 
 For more information see [the compatible destination lists below](#multi-instance-compatible-destinations).
@@ -169,7 +169,7 @@ In this example:
 The sections below list the most popular multi-instance Segment destinations. This list is not exhaustive. If you don’t see your favorite destination in these lists, [contact Segment Customer Success](https://segment.com/help/contact/).
 
 ##### Cloud-mode and device-mode
-The following destinations can receive data from an unlimited number of sources in cloud-mode, and **up to one device-mode connection**.
+For the following destinations, a single source can connect to up to 10 instances of the destination in cloud-mode, and **up to one instance in device-mode**.
 
 - [Adobe Analytics](/docs/connections/destinations/catalog/adobe-analytics/)
 - [Amplitude](/docs/connections/destinations/catalog/amplitude/)
@@ -183,7 +183,7 @@ The following destinations can receive data from an unlimited number of sources
 
 ##### Cloud-mode only
 
-The following destinations can receive data from an unlimited number of sources in cloud-mode, but do not support device-mode connections at all.
+For the following destinations, a single source can connect to up to 10 instances of the destination in cloud-mode, but these destinations do not support a device-mode connection at all.
 
 - [ActiveCampaign](/docs/connections/destinations/catalog/activecampaign/)
 - [Akita](/docs/connections/destinations/catalog/akita/)

src/connections/destinations/catalog/cliff/images/cliff1.png

@@ -1,5 +1,80 @@
 ---
-title: 'Cliff Destination'
-hidden: true
-beta: true
----
+title: Cliff Destination
+rewrite: true
+---
+[Cliff](https://cliff.ai/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) monitors all your metrics in real time, detects unexpected changes (such as a sudden spike or dip), and notifies you immediately. It also shows you the root cause behind the unexpected change.
+
+This destination is maintained by Cliff.ai. For any issues with the destination, [contact the Cliff Support team](mailto:[email protected]).
+
+## Getting Started
+
+{% include content/connection-modes.md %}
+
+1. Go to the [Cliff Integrations library](https://app.cliff.ai/apps/anomaly-detection/integrations/inbound).
+2. Find "Segment" in the list of available integrations and click **Start**.
+3. Name your integration and click **Authorise Segment**.
+4. Select your Workspace and Source and click **Allow**.
+5. [Create a Data Stream on Cliff](https://app.cliff.ai/apps/anomaly-detection/data-streams/create-streams). Choose which Segment events and dimensions to start monitoring. Enter the name of the event and click the blue **+** button. Repeat to add dimensions. Click **Continue**.
+   ![](images/cliff1.png)
+   **Note**: Cliff ingests _only_ the events you select in this screen.
+6.  Select how often Cliff should batch the data that Segment sends.
+![](images/cliff2.png)
+
+
+## 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 Cliff as a `track` event.
+
+## 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 Cliff as a `pageview`.
+
+## 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:
+
+```objc
+[[SEGAnalytics sharedAnalytics] screen:@"Home"];
+```
+
+Segment sends Screen calls to Cliff as a `screenview`.
+
+## 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 Cliff as an `identify` event.
+
+## 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 Cliff as a `group` event.