Revenue Institute needed Intercom live across its sales platform — user creation, segmentation, live chat, and product demos — but chat and demos weren't working and the team didn't know why. I audited the Segment-to-Intercom pipeline against all four acceptance criteria and traced the failures to their source.
Role Led the Intercom integration audit — traced identify-call, identity-verification, and chat/demo failures across the Segment-to-Intercom pipeline
Revenue Institute sells sales products to sales professionals, and managers wanted Intercom to surface new signups, segment them, and open live chat and product demo conversations automatically.
New users on Revenue Institute needed an Intercom record the moment they signed up, so sales had a single source of truth on who to engage.
Sales managers wanted to segment users on event or property criteria so they could start the right sales conversation at the right moment.
Logged-in users were expected to see a working live chat widget and product demo tour as core conversion touchpoints.
Three separate failures — partial user sync, a rejected API call, and missing company data — were all blocking the same downstream features.
Intercom user creation worked on the signup journey, but broke on page refresh and on subsequent logins — identify calls weren't firing consistently.
Intercom's identity verification was enabled but the user_hash wasn't being passed correctly, and the domain wasn't allowlisted — producing 403 Forbidden errors on event calls.
Live chat and the product tour both required company and company_id from identify calls post-login — without them, Intercom rejected events with "company_id cannot be blank."
Each fix traced one acceptance criterion back to its Segment configuration, isolating exactly where the data dropped.
Tested identify calls across signup, page refresh, and login, confirming signup worked but refresh and login did not yet create or update Intercom users.Intercom · Identify calls
Reviewed Segment's Intercom mappings — Auth, Identify, Account Email Verified, Auth Login — and confirmed all event types were enabled so managers could segment users on event or property criteria.Segment · Mappings
Identified that the chat widget needed page and identify calls with a valid user_hash, an allowlisted domain, and non-blank company/company_id fields to render and stay enabled.Identity verification · company_id
Confirmed one Segment destination (cloud or web) is sufficient per event, and that unique email counts in Mixpanel and Intercom should match once the system stabilizes in production.Segment destinations · Mixpanel
The same checklist — identify calls on every lifecycle event, user_hash on identity verification, domain allowlisting, and company_id population — applies to any future Segment-to-Intercom rollout.
Consistent identify calls on signup, refresh, and login are the prerequisite for user sync, segmentation, chat, and product tours alike.
Cloud or web mappings alone are sufficient to forward events — running both isn't required for event setup.
Let's talk
Tell me your biggest data or AI bottleneck and I'll send you how I'd approach it — the same way I worked this problem. No résumé dump, no pitch. Just a useful conversation.
Start the conversation →