RudderStack supports sending event data to Intercom via the following connection modes:
Once you have confirmed that your source platform supports sending events to Intercom, follow these steps:
Assign a name to the destination and click Continue.
To successfully configure Intercom as a destination, you will need to configure the following settings:
Access Token: Enter your Intercom API access token. You can obtain the token by going to your Intercom dashboard and navigating to Settings > Apps & Integrations > Developer Hub. Then, select your app and go to Configure > Authentication. For more information, refer to the Intercom documentation.
App ID: The Intercom app ID is required for sending events via the web and mobile SDKs. You can get this ID from your Intercom dashboard by going to Settings > Installation and selecting the relevant platform. For more information on obtaining the your Intercom app ID, refer to the Intercom Knowledge Base.
Android API Key / iOS API Key: This is required for sending events from your mobile apps to Intercom. You can get it from your Intercom dashboard by going to Settings > Installation and selecting the relevant platform.
Include Context with Identify Calls: Enable this option to send the user context details to Intercom in the identify calls.
Send AnonymousId as Secondary UserId: Enable this option to send anonymousId as the user ID to Intercom when the userId is absent from the event payload.
This option is helpful for tracking anonymous users on your site. For more information on the scenario where this setting is useful, refer to the FAQ section below.
Adding device mode integration
Depending on your platform of integration, follow the steps below to add Intercom to your project:
Your Android app must be on version 5.0 (API level 21) or higher for RudderStack to be able to send events to Intercom.
Follow these steps to add Intercom to your Android project:
In your app-level build.gradle file, add the following repository:
The user_hash is a SHA256 hash of your Intercom API secret and the userId. Note that this hash is not based on the user’s email.
To obtain your Intercom API secret, go to your Intercom dashboard and navigate to Settings > Apps & Integrations > Developer Hub. Then select your app and go to Configure > Basic information. You will find the API secret listed here under Client secret.
RudderStack converts and sends all track event properties as per the Intercom API.
The page call lets you record your website’s page views with any additional relevant information about the viewed page.
A sample page call looks like the following code snippet:
The reset method resets the previously identified user and any related information.
To reset user identification in your Android app, run the following command:
To reset user identification in your iOS app, run the following command:
Does RudderStack support Intercom’s push notification and deep linking features?
Unfortunately, none of the RudderStack SDKs support push notifications and deep linking features currently. Refer to the Intercom documentation for more information on configuring these features for your project.
What happens if both userId or email are missing in the identify / track calls sent to Intercom?
For both identify and track calls, either userId or email is a mandatory field. In case both these fields are missing, RudderStack will drop the event.
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
for the working of basic functionalities of the website. We also use third-party cookies that
analyze and understand how you use this website. These cookies will be stored in your browser
consent. You also have the option to opt-out of these cookies. But opting out of some of these
have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.