Stitch Documentation
has moved!

Please update your bookmarks to https://www.stitchdata.com/docs

If you're not automatically redirected after 5 seconds, click here.

Expected Intercom Data

Now that Intercom is successfully connected to Stitch, what comes next? In this article, we'll cover:

Replicating Intercom Data

Historical Sync

By default, a historical sync of Intercom data goes back one year from the Stitch connection date.

Frequency

Stitch will replicate Intercom data based on the frequency you define. The default setting is every 30 minutes, but you can change it to something less frequent based on your needs.

Replication Method

The majority of Intercom data is replicated using Incremental Replication. This means that every time Intercom data is queued for replication, only new and updated rows will be replicated to your data warehouse.

The exceptions to this, or the tables that use Full Table Replication, are:

  • admins
  • tags

Every time Intercom data is queued for replication, all the rows in the above tables - including new, updated, and existing - will be replicated to your data warehouse.

Intercom Tables in Your Data Warehouse

Below is a list of the Intercom tables and subtables that will be created in your data warehouse. Because Intercom uses nested arrays to structure data in some of its API's endpoints, Stitch will de-nest these arrays and create subtables. Refer to the Handling of Nested Data Structures doc for more info.

Click a table name to view a full list of that table's attributes in Intercom's API documentation.

admins
Primary Key:
_id

The admins table contains information about the admin users in your Intercom account.

Attributes include the admin ID (id), type, name, and email address.

companies
Primary Key:
_id

The companies table contains information about the companies that use your Intercom product.

Attributes include the Intercom company ID (id), name, custom attributes, session count, monthly spend, user count, plan, and creation and updated at dates.

company_segments
Primary Key:
_id

The company_segments table contains information about company segments.

Attributes include the company segment ID (id), name, person type (ex: user), type, and created and updated at dates.

conversations
Primary Key:
_id

The conversations table contains information about user conversations, or conversations initiated by your end-users.

Attributes include the conversation ID (id), starting message, user, assignee, read and open flags, and created at and updated at dates.

Subtables

The composite key for the following tables - made up of the conversation ID and the row ID - can be used to tie it back to its parent table, conversations: _sdc_source_key_id:_sdc_level_0_id.

  • conversations__tags - This subtable is created from the tags array, which contains the tags applied to a conversation.
  • conversations__conversation_parts - This subtable is created from the conversation parts array, which contains the individual parts of conversations.

leads
Primary Key:
_id

Previously known as contacts, the leads table contains information about the logged-out users of your Intercom product.

Attributes include the lead ID (id), user ID, email address, name, custom attributes, request info, location data, social profiles, tags, company info, and created at and updated at dates.

segments
Primary Key:
_id

The segments table contains information about the segments - or groups of users defined by a set of rules - in your Intercom account.

Attributes include the segment ID (id), type, name, and creation and updated at dates.

tags
Primary Key:
_id

The tags table includes the data for the tags in your account.

Attributes include the tag ID (id), type, and name.

users
Primary Key:
_id

The users table includes information about the users in your Intercom account.

Attributes include the user ID (id), type, email address, name, custom attributes, request info, session count, location data, IP address, tags, and creation, sign-up, and updated at dates.

Related

Was this article helpful?
0 out of 0 found this helpful

Comments

Questions or suggestions? If something in our documentation is unclear, let us know in the comments!