Merge branch 'master' into update-edit-links

markzegarelli · markzegarelli · commit 81a78a4202f1 · 2021-05-11T13:13:45.000-07:00
diff --git a/src/connections/destinations/add-destination.md b/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/)
diff --git a/src/connections/destinations/catalog/cliff/images/cliff1.png b/src/connections/destinations/catalog/cliff/images/cliff1.png
diff --git a/src/connections/destinations/catalog/cliff/images/cliff2.png b/src/connections/destinations/catalog/cliff/images/cliff2.png
diff --git a/src/connections/destinations/catalog/cliff/index.md b/src/connections/destinations/catalog/cliff/index.md
@@ -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:support@cliff.ai).
+
+## 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: 'john.doe@example.com'
+});
+```
+
+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.
diff --git a/src/connections/destinations/catalog/regal-voice/index.md b/src/connections/destinations/catalog/regal-voice/index.md
@@ -77,14 +77,14 @@ analytics.identify({
     {
       channel: "sms",
       subscribed: true,
-      subscribedAt: "2020-08-25T21:23:43Z",
+      timestamp: "2020-08-25T21:23:43Z",
       ip: "172.16.254.1",
       text: "By clicking the 'Submit' button below, I agree to receive automated marketing SMS and calls."
     }, 
     {
       channel: "voice",
       subscribed: true,
-      subscribedAt: "2020-08-25T21:23:43Z",
+      timestamp: "2020-08-25T21:23:43Z",
       ip: "172.16.254.1",
       text: "By clicking the 'Submit' button below, I agree to receive automated marketing SMS and calls."
   }]
@@ -95,7 +95,7 @@ Supported messaging channels are: `sms`, `voice` and `email`.
 
 The `ip` field is required if you are opting in users server side. 
 
-Make sure to include `subscribedAt` with the exact time the user opted in. Since traits are [cached](/docs/connections/sources/catalog/libraries/website/javascript/identity/#clearing-traits) and sent with subsequent `identify` calls, Regal Voice ignores opt-ins without a `subscribedAt` date. 
+Make sure to include `timestamp` with the exact time the user opted in. Since traits are [cached](/docs/connections/sources/catalog/libraries/website/javascript/identity/#clearing-traits) and sent with subsequent Identify calls, Regal Voice ignores opt-ins that do not have a `timestamp` date. 
 
 
 ## Track
diff --git a/src/connections/destinations/catalog/zendesk/index.md b/src/connections/destinations/catalog/zendesk/index.md
@@ -124,16 +124,28 @@ analytics.track('Article Completed', {
 });
 ```
 
-**Important:** To make track calls, you must sign up for Zendesk's [User Events API early access program](https://develop.zendesk.com/hc/en-us/community/topics/360000030527)
+**Important:** You must have a Zendesk [Sunshine plan](https://www.zendesk.com/pricing/?variant=a#platform) to make track calls.
 
-When you call `track` we will send data about a user's activity to Zendesk.
+When you make a Track call, Segment sends data about the user's activity to Zendesk.
 
 We will only send `track` events when the following two conditions are met:
 
 1. The call is listed in the "Events" setting.
 2. A `userId` is included.
   - **Note:** If the `userId` doesn't match any existing users in Zendesk, we will return an error.
 
+**Mapping Users to an Email**: To map a Segment track event to a Zendesk Sunshine event by email, add the user's email address in the Track call as `properties.email`. This allows Zendesk to tie the event to the user. If there is no `properties.email`, Segment sends the `userId` as `external_id`. If the email is provided in the track call, a javascript call may look like the example below.
+
+```js
+analytics.track('Article Completed', {
+  title: 'How to Create a Tracking Plan',
+  course: 'Intro to Analytics',
+  properties: {
+    email : 'user@example.com',
+  }
+});
+```
+
 ## Group
 
 If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like:
diff --git a/src/connections/sources/catalog/cloud-apps/launchdarkly/index.md b/src/connections/sources/catalog/cloud-apps/launchdarkly/index.md
@@ -5,8 +5,6 @@ title: LaunchDarkly Source
 
 This source is maintained by LaunchDarkly. For any issues with the source, [contact the LaunchDarkly Support team](mailto:support@launchdarkly.com).
 
-{% include content/beta-note.md %}
-
 
 ## Getting Started
 
diff --git a/src/connections/sources/catalog/cloud-apps/regal-voice/index.md b/src/connections/sources/catalog/cloud-apps/regal-voice/index.md
@@ -31,27 +31,39 @@ The table below lists events that Regal Voice sends to Segment. These events app
   </tr>
   <tr>
    <td>contact.subscribed</td>
-   <td>A Contact was subscribed to a marketing channel</td>
+   <td>A contact was subscribed to a marketing channel</td>
   </tr>
   <tr>
    <td>contact.unsubscribed</td>
-   <td>A Contact was unsubscribed from a marketing channel</td>
+   <td>A contact was unsubscribed from a marketing channel</td>
   </tr>
     <tr>
    <td>sms.queued</td>
-   <td>An sms was queued to be sent from RegalVoice to Contact</td>
+   <td>An sms was queued to be sent from RegalVoice to contact</td>
   </tr>
     <tr>
    <td>sms.sent</td>
-   <td>An sms was sent from RegalVoice to Contact</td>
+   <td>An sms was sent from RegalVoice to contact</td>
   </tr>
     <tr>
-   <td>sms.delivered</td>
-   <td>An sms was delivered from RegalVoice to Contact</td>
+   <td>sms.undelivered</td>
+   <td>An sms was undelivered from RegalVoice to contact</td>
   </tr>
     <tr>
-   <td>sms.undelivered</td>
-   <td>An sms was undelivered from RegalVoice to Contact</td>
+   <td>sms.received</td>
+   <td>An sms was received from a contact</td>
+  </tr>
+    <tr>
+   <td>task.created</td>
+   <td>A call or sms task was created</td>
+  </tr>
+    <tr>
+   <td>sms.conversation_completed</td>
+   <td>An SMS conversation between a contact and an agent was completed in the Regal Voice agent desktop</td>
+  </tr>
+    <tr>
+   <td>call.completed</td>
+   <td>An inbound or outbound call with a contact was completed. This includes calls that were not answered</td>
   </tr>
 </table>
 
@@ -64,16 +76,15 @@ The table below lists events that Regal Voice sends to Segment. These events app
   </tr>
   <tr>
    <td>`channel`</td>
-   <td>Marketing channel of the subscription update. Acceptible value are: "voice", "sms", "email"
-</td>
+   <td>The marketing channel: "voice" or "sms"</td>
   </tr>
   <tr>
    <td>`phone`</td>
-   <td>The phone number the subscription update was applied to. Phone number is the unique identifier for a Contact in Regal Voice</td>
+   <td>The phone number the subscription update was applied to. Phone number is the unique identifier for a contact in Regal Voice</td>
   </tr>
   <tr>
    <td>`email`</td>
-   <td>The last email associated with the Contact</td>
+   <td>The last email associated with the contact</td>
   </tr>
   <tr>
    <td>`ip`</td>
@@ -87,18 +98,18 @@ The table below lists events that Regal Voice sends to Segment. These events app
   </tr>
   <tr>
    <td>`text`</td>
-   <td>Only applies to contact.subscribed event. The exact text the Contact was presented for opt in</td>
+   <td>The exact text the contact was presented for opt in</td>
   </tr>
   <tr>
    <td>`timestamp`</td>
    <td>Unix timestamp for when the event took place</td>
   </tr>
   <tr>
    <td>`contact_phone`</td>
-   <td>Phone number of the Contact</td>
+   <td>Phone number of the contact</td>
   </tr>
   <tr>
-   <td>`regal_voice_number`</td>
+   <td>`regal_voice_phone`</td>
    <td>RegalVoice phone number</td>
   </tr>
   <tr>
@@ -107,7 +118,7 @@ The table below lists events that Regal Voice sends to Segment. These events app
   </tr>
   <tr>
    <td>`direction`</td>
-   <td>Direction of the SMS (INBOUND or OUTBOUND)</td>
+   <td>INBOUND or OUTBOUND</td>
   </tr>
   <tr>
    <td>`from_number`</td>
@@ -123,7 +134,87 @@ The table below lists events that Regal Voice sends to Segment. These events app
   </tr>
   <tr>
    <td>`sms_conversation_id`</td>
-   <td>Unique ID of the conversation (if the sms was part of a two-way conversation with an Agent, rather than just an automated outbound sms)</td>
+   <td>Task ID for the conversation. (If the sms was part of a two-way conversation with an Agent, rather than just an automated outbound sms)</td>
+  </tr>
+  <tr>
+   <td>`campaign_friendly_id`</td>
+   <td>Campaign Friendly Id as seen in the App</td>
+  </tr>
+  <tr>
+   <td>`campaign_id`</td>
+   <td>Campaign Id</td>
+  </tr>
+  <tr>
+   <td>`campaign_name`</td>
+   <td>Campaign Name</td>
+  </tr>
+  <tr>
+   <td>`queue`</td>
+   <td>Task Queue</td>
+  </tr>
+  <tr>
+   <td>`scheduling_agent_fullname`</td>
+   <td>Full name of the agent who scheduled the Callback</td>
+  </tr>
+  <tr>
+   <td>`scheduling_agent_id`</td>
+   <td>Email of the agent who scheduled the Callback</td>
+  </tr>
+  <tr>
+   <td>`target_agent_fullname`</td>
+   <td>Full name of the agent who contact (and all contact’s tasks) are assigned to</td>
+  </tr>
+  <tr>
+   <td>`target_agent_id`</td>
+   <td>Email of the agent who contact (and all contact’s tasks) are assigned to</td>
+  </tr>
+  <tr>
+   <td>`task_id`</td>
+   <td>Unique identifier for the task. Will match the call_id or sms_conversation_id of a completed task event.</td>
+  </tr>
+  <tr>
+   <td>`type`</td>
+   <td>Task Type</td>
+  </tr>
+  <tr>
+   <td>`call_id`</td>
+   <td>Task Id for the call</td>
+  </tr>
+  <tr>
+   <td>`disposition`</td>
+   <td>Task disposition</td>
+  </tr>
+  <tr>
+   <td>`objections`</td>
+   <td>Task objections</td>
+  </tr>
+  <tr>
+   <td>`notes`</td>
+   <td>Task notes</td>
+  </tr>
+  <tr>
+   <td>`handle_time`</td>
+   <td>Full duration task was being handled, including talk time and wrap time (completed_at - started_at)</td>
+  </tr>
+  <tr>
+   <td>`wrapup_time`</td>
+   <td>Duration task was in wrap up (completed_at - ended_at)</td>
+  </tr>
+  <tr>
+   <td>`talk_time`</td>
+   <td>Duration of conversation (ended_at - started_at)</td>
+  </tr>
+  <tr>
+   <td>`started_at`</td>
+   <td>UTC timestamp when the conversation was started</td>
+  </tr>
+  <tr>
+   <td>`ended_at`</td>
+   <td>UTC timestamp when the conversation was ended</td>
+  </tr>
+  <tr>
+   <td>`completed_at`</td>
+   <td>UTC Timestamp when the task was completed</td>
   </tr>
 </table>
 
diff --git a/src/personas/identity-resolution/use-cases.md b/src/personas/identity-resolution/use-cases.md
@@ -27,7 +27,7 @@ If a company needs to understand a user's activity across all apps, we recommend
 
 If, however, each app should maintain its own metrics and LTV analysis, regardless of the overlap of users between apps, we recommend creating a separate Personas space per app and only connecting sources related to each app to its space. This will give a siloed view of how users interact with each individual app.
 
-  _Note: Each workspace has two spaces by default. contact your CSM to enable additional spaces._
+  _Note: Each workspace has two spaces by default. Contact your CSM to enable additional spaces._
 
 For an eCommerce example, see [here](/docs/personas/identity-resolution/ecommerce-example/)
 

-Original file line number
+Diff line change
 This source is maintained by LaunchDarkly. For any issues with the source, [contact the LaunchDarkly Support team](mailto:[email protected]).
 -{% include content/beta-note.md %}
+-
 ## Getting Started