Skip to content

Commit 9b6ddd8

Browse files
committed
edits
1 parent e49e6a2 commit 9b6ddd8

File tree

1 file changed

+9
-7
lines changed
  • src/connections/destinations/catalog/actions-intercom-web

1 file changed

+9
-7
lines changed

src/connections/destinations/catalog/actions-intercom-web/index.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -29,18 +29,20 @@ Intercom Web (Actions) provides the following benefits over the classic Intercom
2929
- **Granular control over data sent.** You can customize the conditions under which the events are sent to Intercom.
3030
- **Selectively shows the Intercom chat widget.**
3131

32-
### Chat Widget
33-
[The Intercom Cloud Mode (Actions)](https://segment.com/docs/connections/destinations/catalog/actions-intercom-cloud/) Destination does not have access to Intercom’s chat widget, but only the Intercom Web Actions Destination would have access to this.
32+
### Intercom's chat widget
3433

35-
The difference has to do with how data gets sent to Intercom. If you are using [Analytics.js source](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/) - you can use the Intercom Web Mode (Actions) destination which will send data directly to Intercom from the client-side, by loading the Intercom SDK directly onto your website.
34+
The [Intercom Cloud Mode (Actions)](/docs/connections/destinations/catalog/actions-intercom-cloud/) destination doesn't have access to Intercom’s chat widget. Only the [Intercom Web (Actions)](/docs/connections/destinations/catalog/actions-intercom-web/) destination has access to this.
3635

37-
Whereas, the [Intercom Cloud Mode (Actions)](https://segment.com/docs/connections/destinations/catalog/actions-intercom-cloud/) works by first sending the data to Segment, followed by Segment forwarding the data to Intercom. This allows Segment users to send data to Intercom from sources that are incompatible with their SDK.
36+
If you're using the [Analytics.js source](/docs/connections/sources/catalog/libraries/website/javascript/), use the Intercom Web Mode (Actions) destination which sends data directly to Intercom from the client-side by loading the Intercom SDK directly onto your website.
3837

39-
The [Connection Modes section of our Destinations Overview docs](https://segment.com/docs/connections/destinations/#connection-modes) here do a great job of breaking down the differences between the two types of connection modes that Segment offers.
38+
However, [Intercom Cloud Mode (Actions)](/docs/connections/destinations/catalog/actions-intercom-cloud/) sends data to Segment, after which Segment forwards the data to Intercom. This allows Segment users to send data to Intercom from sources that are incompatible with their SDK.
4039

41-
When you configure the Segment Intercom destination in device-mode, you will have access to the chat widget that gets loaded by the Intercom SDK without the need to load Intercom separately outside of Segment.
40+
When you configure the Segment Intercom destination in device-mode, you'll have access to Intercom's chat widget without loading Intercom separately outside of Segment.
4241

43-
In order to have access to the "Intercom Messaging Box", you'd instead want to configure and connect the Intercom Web Mode (Actions) destination to your Analytics.js source.
42+
To access the Intercom Messaging Box, you'll need to configure and connect the Intercom Web (Actions) destination to your Analytics.js source.
43+
44+
> success ""
45+
> Visit the [Destination Overview docs](/docs/connections/destinations/#connection-modes) to learn the difference between cloud and device modes.
4446
4547
## Getting started
4648

0 commit comments

Comments
 (0)