Intercom Integration Not Syncing User Data Correctly From Website | Community
Skip to main content
Answered

Intercom Integration Not Syncing User Data Correctly From Website

  • February 9, 2026
  • 1 reply
  • 63 views
J

Hi everyone,

I’ve integrated Intercom into my website to handle customer messaging, onboarding, and support, but I’m running into issues with how user data is being synced from the site into Intercom.

While the Intercom widget loads correctly on the frontend, user attributes such as email, user ID, signup date, and custom properties are not always updating or appearing as expected in the Intercom dashboard. In some cases, users show up as anonymous even after logging in, and conversations don’t always attach to the correct user profile. This behavior seems inconsistent and makes it difficult to track user history accurately.

I’ve reviewed the JavaScript installation, checked that the identify/update calls are firing at the correct times, and confirmed that the attribute names match what’s defined in Intercom. There haven’t been any recent major changes to the site’s authentication flow, but the issue started appearing after some recent updates to other third-party integrations, so I’m wondering if there could be conflicts or timing issues involved.

Has anyone else experienced similar problems with Intercom integrations on a live website? Are there specific best practices around identifying users, handling SPA page loads, or syncing custom attributes that I should be following? I can share more details about my setup or logs if that helps with troubleshooting.

Thanks in advance for any advice or insights.

Best answer by Nico Magbiray

Hi,

I think the core issue is likely a race condition or a session conflict between the "anonymous" visitor cookie and your logged-in user state. In Single Page Apps (SPAs) or sites with many scripts, the quickest fix is to call Intercom('shutdown'); immediately upon login, followed by a fresh Intercom('boot', {...}); containing the user_id and signed JWT. This forced reset clears out the old visitor session and ensures the conversation history and attributes attach to the correct profile. Also, double-check that "Require verified updates" isn't accidentally blocking your frontend data, if it’s enabled, any attributes not included in your backend-signed JWT will be ignored by the dashboard.

Let me know if that worked.

1 reply

Nico Magbiray
Innovator ✨
Forum|alt.badge.img+4
  • Nico Magbiray
  • Innovator ✨
  • Answer
  • February 10, 2026

Hi,

I think the core issue is likely a race condition or a session conflict between the "anonymous" visitor cookie and your logged-in user state. In Single Page Apps (SPAs) or sites with many scripts, the quickest fix is to call Intercom('shutdown'); immediately upon login, followed by a fresh Intercom('boot', {...}); containing the user_id and signed JWT. This forced reset clears out the old visitor session and ensures the conversation history and attributes attach to the correct profile. Also, double-check that "Require verified updates" isn't accidentally blocking your frontend data, if it’s enabled, any attributes not included in your backend-signed JWT will be ignored by the dashboard.

Let me know if that worked.

Terms & ConditionsAccessibility statement