Setup Guide Beta
Set up and configure Intercom v2 as a destination in RudderStack.
2 minute read
This guide will help you set up Intercom v2 as a destination in the RudderStack dashboard. It also lists the configuration settings required to correctly send data from the supported sources to Intercom v2.
Connection compatibility
| Destination Information | |||
|---|---|---|---|
| |||
| Connection Modes | |||
|---|---|---|---|
| Source | Cloud mode | Device mode | Hybrid mode |
| AMP |  |  | |
| Android (Java) | | | |
| Android (Kotlin) | | | |
| Cloud | | | |
| Cordova | | | |
| Flutter | | | |
| iOS (Obj-C) | | | |
| iOS (Swift) | | | |
| React Native | | | |
| Unity | | | |
| Warehouse | | | |
| Web | | | |
| Supported sources | | | | | | | | |
Setup
In your RudderStack dashboard, add a source. Then, from the list of destinations, select Intercom v2.
Connection settings
| Setting | Description |
|---|---|
| Name | Assign a name to uniquely identify the destination in RudderStack. |
| oAuth settings | Click Create Account > Connect with Intercom v2 and give RudderStack the required permissions to access your Intercom account. |
| API server | Select your Intercom workspace server. By default, RudderStack sets it to Standard (US) and provides two other options - EU (Europe) and AU (Australia). |
Configuration settings
Configure the below settings to receive your data correctly in Intercom.
| Setting | Description |
|---|---|
| Send anonymous ID as secondary user ID | Toggle on this setting to send anonymous ID as the secondary user ID. Note: This setting is applicable only for Event Stream connections. |
| Consent management provider | Configure the consent management settings for the specified source by choosing the Consent management provider from the dropdown and entering the relevant consent category IDs. See Consent Management in RudderStack for more information on this feature. |
