Skip to content

Commit f67935d

Browse files
Update add-destination.md (#1615)
* Update add-destination.md Added information to indicate: - mobile and project sources now support sending to multiple instances of cloud-mode only destinations - Amplitude is a cloud-mode only destination, not a cloud-mode and device-mode destination, so I moved it out of the first list and into the 2nd list. - Made it super clear that the integrations object does not support sending data to individual destination instances, as there was confusion about this * Update src/connections/destinations/add-destination.md Co-authored-by: LRubin <[email protected]> Co-authored-by: LRubin <[email protected]>
1 parent 908ac76 commit f67935d

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

src/connections/destinations/add-destination.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -127,11 +127,10 @@ You can add multiple instances of a destination using the Segment Config API. Se
127127

128128
### Multi-instance destinations and Device-mode
129129

130-
131-
- **Mobile sources, and the legacy Project source, cannot connect to multiple instances of a destination.**
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.
133130
- **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 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.
131+
- **Mobile sources, and the legacy Project source, can connect to multiple instances of cloud-mode only destinations.** See the list of [cloud-mode only destinations](#cloud-mode-only). Moble and Project sources cannot connect to multiple instances of [cloud-mode and device-mode destinations](#cloud-mode-and-device-mode).
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+
- **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 sending to a destination in device-mode sends 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.
135134
- **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.
136135

137136
For more information see [the compatible destination lists below](#multi-instance-compatible-destinations).
@@ -162,7 +161,7 @@ In this example:
162161

163162
- Events sent with this `Mixpanel` setting are **not** sent to instances of Mixpanel.
164163
- Events sent to any Adobe Analytics destinations with this `Adobe Analytics` setting use the same `marketingCloudVisitorId` value specified.
165-
164+
You can not use the [integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object) to send data to individual destination instances.
166165

167166
### Multi-instance compatible destinations
168167

@@ -172,7 +171,6 @@ The sections below list the most popular multi-instance Segment destinations. Th
172171
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**.
173172

174173
- [Adobe Analytics](/docs/connections/destinations/catalog/adobe-analytics/)
175-
- [Amplitude](/docs/connections/destinations/catalog/amplitude/)
176174
- [Braze](/docs/connections/destinations/catalog/braze/)
177175
- [Customer.io](/docs/connections/destinations/catalog/customer-io)
178176
- [Google Analytics](/docs/connections/destinations/catalog/google-analytics/)
@@ -193,6 +191,7 @@ For the following destinations, a single source can connect to up to 10 instance
193191
- [Amazon Kinesis Firehose](/docs/connections/destinations/catalog/amazon-kinesis-firehose/)
194192
- [Amazon Lambda](/docs/connections/destinations/catalog/amazon-lambda/)
195193
- [Amazon Personalize](/docs/connections/destinations/catalog/amazon-personalize/)
194+
- [Amplitude](/docs/connections/destinations/catalog/amplitude/)
196195
- [Attribution](/docs/connections/destinations/catalog/attribution/)
197196
- [Attune](/docs/connections/destinations/catalog/attune/)
198197
- [Autopilot](/docs/connections/destinations/catalog/autopilothq/)

0 commit comments

Comments
 (0)