You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-intercom-web/index.md
+33-2Lines changed: 33 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,5 +70,36 @@ If you are seeing 404 responses in your browser's network tab, you've likely enc
70
70
- You set the wrong App ID on the Intercom Actions (Web) destination settings page.
71
71
- You set the wrong Regional Data Hosting value on the Intercom Actions (Web) destination settings page. Intercom gates regional endpoints by plan level, so you may not have access to EU data hosting.
72
72
73
-
### Intercom does not support rETL event batching
74
-
The Intercom (Web) Actions destination does not support the bulk contacts endpoint, and therefore is unable to support batching events in rETL.
73
+
### Intercom does not support Reverse ETL event batching
74
+
The Intercom (Web) Actions destination does not support the bulk contacts endpoint, and therefore is unable to support batching events in Reverse ETL.
75
+
76
+
### Why are my Identify calls not updating or creating Intercom profiles, or not showing users as leads or visitors?
77
+
Intercom requires requests to include user data/traits beyond `email` or `user_hash` to update or create profiles and change user status from leads/visitors. Without additional user data/traits, Intercom assumes no changes were made to a user's data and does not send a "ping" request.
78
+
79
+
In the following example, which only includes an `email` and `user_hash`, Intercom would not send a "ping" request and update the status of this user:
When sending calls to Intercom, always include a trait, like`name`. If you don't have a trait to send with Identify calls, map Segment's `timestamp` field to Intercom's `last_request_at` field.
0 commit comments