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
+78-3Lines changed: 78 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -114,7 +114,7 @@ To connect a source to more than one instance of a destination in the Segment we
114
114
115
115
You must give each instance of the destination connected to the same source a unique name. Segment recommends that you use descriptive names rather than numbers, so other Segment users can understand which Segment destinations are linked to which tool instances. For example, you might use "Amplitude North America" and "Amplitude South America", instead of "Amplitude 1" and "Amplitude 2".
116
116
117
-
If you added the first instance of your destination before multi-instance destinations became available, that instance is automatically named for the destination with no other identifiers, for example "Amplitude". You cannot currently edit these first destinations' names.
117
+
If you added the first instance of your destination before multi-instance destinations became available, that instance is automatically named for the destination with no other identifiers, for example "Amplitude". You cannot currently edit these first destinations' names.
118
118
Some destinations do not support having multiple instances connected to the same source. In that case, the option to add a second instance of that destination does not appear.
119
119
120
120
### Connect to more than one instance of a destination using the Config API
@@ -125,8 +125,8 @@ You can add multiple instances of a destination using the Segment Config API. Se
125
125
### Multi-instance destinations and Device-mode
126
126
127
127
128
-
-**_Mobile and Project_ sources cannot connect to multiple instances of a destination.**
129
-
-_Beware_: Bundling one instance of a destination in a mobile source while having other instances of that destination for a given source will have unexpected consequences.
128
+
-**Mobile sources, and the legacy Project source, cannot connect to multiple instances of a destination.**
129
+
-**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.
130
130
-**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.
131
131
-**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.
132
132
-**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.
@@ -171,19 +171,94 @@ The following destinations can receive data from an unlimited number of sources
0 commit comments