You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/add-destination.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -131,7 +131,7 @@ You can add multiple instances of a destination using the Segment Config API. Se
131
131
-**Mobile sources, and the legacy Project source, cannot connect to multiple instances of a destination.**
132
132
-**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.
133
133
-**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.
134
-
-**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.
134
+
-**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.
135
135
-**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.
136
136
137
137
For more information see [the compatible destination lists below](#multi-instance-compatible-destinations).
@@ -169,7 +169,7 @@ In this example:
169
169
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/).
170
170
171
171
##### Cloud-mode and device-mode
172
-
The following destinationscan receive data from an unlimited number of sources in cloud-mode, and **up to one device-mode connection**.
172
+
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**.
@@ -183,7 +183,7 @@ The following destinations can receive data from an unlimited number of sources
183
183
184
184
##### Cloud-mode only
185
185
186
-
The following destinationscan receive data from an unlimited number of sources in cloud-mode, but do not support device-mode connections at all.
186
+
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.
[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.
6
+
7
+
This destination is maintained by Cliff.ai. For any issues with the destination, [contact the Cliff Support team](mailto:[email protected]).
8
+
9
+
## Getting Started
10
+
11
+
{% include content/connection-modes.md %}
12
+
13
+
1. Go to the [Cliff Integrations library](https://app.cliff.ai/apps/anomaly-detection/integrations/inbound).
14
+
2. Find "Segment" in the list of available integrations and click **Start**.
15
+
3. Name your integration and click **Authorise Segment**.
16
+
4. Select your Workspace and Source and click **Allow**.
17
+
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**.
18
+
19
+
**Note**: Cliff ingests _only_ the events you select in this screen.
20
+
6. Select how often Cliff should batch the data that Segment sends.
21
+
22
+
23
+
24
+
## Track
25
+
26
+
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:
27
+
28
+
```js
29
+
analytics.track('Login Button Clicked')
30
+
```
31
+
32
+
Segment sends Track calls to Cliff as a `track` event.
33
+
34
+
## Page
35
+
36
+
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:
37
+
38
+
```js
39
+
analytics.page()
40
+
```
41
+
42
+
Segment sends Page calls to Cliff as a `pageview`.
43
+
44
+
## Screen
45
+
46
+
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:
47
+
48
+
```objc
49
+
[[SEGAnalytics sharedAnalytics] screen:@"Home"];
50
+
```
51
+
52
+
Segment sends Screen calls to Cliff as a `screenview`.
53
+
54
+
## Identify
55
+
56
+
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:
Segment sends Identify calls to Cliff as an `identify` event.
65
+
66
+
## Group
67
+
68
+
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:
69
+
70
+
```js
71
+
analytics.group("0e8c78ea9d97a7b8185e8632", {
72
+
name:"Initech",
73
+
industry:"Technology",
74
+
employees:329,
75
+
plan:"enterprise",
76
+
"total billed":830
77
+
});
78
+
```
79
+
80
+
Segment sends Group calls to Cliff as a `group` event.
The `ip` field is required if you are opting in users server side.
97
97
98
-
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.
98
+
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.
**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)
127
+
**Important:**You must have a Zendesk[Sunshine plan](https://www.zendesk.com/pricing/?variant=a#platform) to make track calls.
128
128
129
-
When you call `track` we will send data about a user's activity to Zendesk.
129
+
When you make a Track call, Segment sends data about the user's activity to Zendesk.
130
130
131
131
We will only send `track` events when the following two conditions are met:
132
132
133
133
1. The call is listed in the "Events" setting.
134
134
2. A `userId` is included.
135
135
-**Note:** If the `userId` doesn't match any existing users in Zendesk, we will return an error.
136
136
137
+
**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.
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:
Copy file name to clipboardExpand all lines: src/personas/identity-resolution/use-cases.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ If a company needs to understand a user's activity across all apps, we recommend
27
27
28
28
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.
29
29
30
-
_Note: Each workspace has two spaces by default. contact your CSM to enable additional spaces._
30
+
_Note: Each workspace has two spaces by default. Contact your CSM to enable additional spaces._
31
31
32
32
For an eCommerce example, see [here](/docs/personas/identity-resolution/ecommerce-example/)
0 commit comments