Intercom is a customer platform with a suite of products for live chat, marketing, feedback, and support. Visit Website
Take your company’s email analysis to the next level by adding Intercom as a Source to Segment. We’ll automatically collect objects like
Conversations and load them into your data warehouse.
From your workspace’s
Give the source a nickname and a schema name. The nickname will be used to designate the source in the Segment interface, and the schema name is the namespace you’ll be querying against in your warehouse. Both can be whatever you like, but we recommend sticking to something that reflects the source itself, like
Intercomfor nickname and
intercom_prodfor the schema name.
Note that you can add multiple instances if you have multiple Intercom accounts. That’s why we allow you to customize the source’s nickname and schema name!
Next, provide your API Key and App ID to access your Intercom data. Your App ID and API Keys are available on the API Keys page on Intercom, accessible from your Integration settings. To create a Key, you can click the ‘New API Key’ button on that page. Feel free to use a read only key for the source integration. Your API key will then appear at the bottom of the page.
- Press connect.
Voila! We’ll begin syncing your Intercom data into Segment momentarily, and it will be written to your warehouse at your next Warehouse run.
Our Intercom integration has a sync component, which means we’ll make requests to their API on your behalf on a 3 hour interval to pull the latest data into Segment. In the initial sync, we’ll grab all the Intercom objects (and their corresponding properties) according to the collections table below. The objects will be written into a designated schema corresponding to the source instance’s schema name you designated upon creation. For example, if you went with
users collection will be accessible at
intercom_prod.users in SQL.
Our sync component uses an upsert API, so the data in your warehouse loaded via sync will reflect the latest state of the corresponding resource in Intercom. For example, if the
users.last_seen_ip will be the latest value upon each sync.
The source syncs and warehouse syncs are independent processes. Source runs pull your data into the Segment Hub, and warehouse runs flush that data to your warehouse. Sources will sync with Segment every 3 hours. Depending on your Warehouses plan, we will push the Source data to your warehouse on the interval associated with your billing plan.
At the moment, we don’t support filtering which objects or properties get synced. If you’re interested in this feature, please let us know!
Collections are the groupings of resources we pull from your source. In your warehouse, each collection gets its own table.
|Object||The Users resource is the primary way of interacting with Intercom. You can create, update and delete your users, and add custom attributes describing them. Users can be viewed individually or as a list, and can queried using tags or segments. For more info, check out the Intercom docs|
|Object||Companies allow you to represent commercial organizations using your product. For more info, check out the Intercom docs|
|Object||Leads are useful for representing logged-out users of your application For more info, check out the Intercom docs|
|Object||A segment is a group of your users defined by rules that you set For more info, check out the Intercom docs|
|Object||A tag allows you to label your users and companies and list them using that tag. For more info, check out the Intercom docs|
|Object||Conversation are how you can communicate with users in Intercom. For more info, check out the Intercom docs|
|Object||Admins are how you can view your teams and team members. For more info, check out the Intercom docs|
|Object||Social data about the user For more info, check out the Intercom docs|
|Object||A conversation part describes an element of the conversation. For more info, check out the Intercom docs|