Users reporting feature issues after installing new in-app tools, how to troubleshoot? | Community
Skip to main content
Answered

Users reporting feature issues after installing new in-app tools, how to troubleshoot?

  • January 26, 2026
  • 1 reply
  • 72 views
K

Hi everyone,

We’ve noticed some users reporting that parts of our in-app widgets stop responding after they add third-party tools to customize their experience. While discussing this with a teammate, we mentioned hub script as one example people often try when experimenting with UI behavior.

Has anyone seen similar conflicts with Intercom widgets, chat triggers, or tracking after users add custom scripts? What’s the best way to isolate whether the issue is coming from Intercom or from external tools?

Best answer by Karla T

Hi ​@kira665 👋 Karla here from the Community team. 

Thanks for raising this. That’s a great question.

Yes, we do occasionally see situations where third-party scripts or UI customization tools interfere with Intercom widgets, chat triggers, or tracking. In most cases, the issue is not a direct conflict with Intercom itself, but rather external scripts modifying the DOM, intercepting events, blocking network requests, or throwing JavaScript errors that prevent the Messenger from initializing correctly.

 

To help isolate whether the issue is coming from Intercom or an external tool, here is a step-by-step approach:

1. Reproduce in a clean environment
Test in an incognito or private window with browser extensions disabled. If the issue disappears, that is a strong indicator that an injected script or extension is responsible.

2. Confirm the Messenger is loading correctly
Open DevTools and go to the Network tab to look for Intercom network requests, often referred to as the "ping."
If no Intercom requests appear, the snippet may be blocked or interrupted.
You can also run Intercom('show') in the console to confirm the library is available.

3. If using a Single Page Application (SPA)
Ensure Intercom('update') is called on route changes so messages and triggers can re-check eligibility. Also confirm boot and shutdown are used correctly when user identity changes.

4. Temporarily disable other scripts
If scripts are managed via GTM or another loader, disable all non-essential scripts and re-enable them in batches. This binary search method is often the fastest way to pinpoint the exact script causing the issue.

5. Check for CSS and DOM manipulation
Custom scripts that modify or restyle Intercom elements, overlay page content, or rewrite class names can prevent launchers or tours from working as expected.

If, after isolating external scripts, the issue still occurs in a clean environment with only the Intercom snippet installed, that would be a good point to escalate. For escalation, it would help to gather:

  • Affected URLs

  • Steps to reproduce

  • Console errors, screenshots are fine

  • HAR or network capture showing Intercom requests

  • Whether the site is an SPA

  • A list of third-party scripts currently running

If you are seeing this behavior persist even after disabling external tools, let me know and I am happy to escalate this to our Inbox team for deeper investigation.

1 reply

Karla T
Intercom Team
Forum|alt.badge.img
  • Karla TIntercom Team
  • Intercom Team
  • Answer
  • March 7, 2026

Hi ​@kira665 👋 Karla here from the Community team. 

Thanks for raising this. That’s a great question.

Yes, we do occasionally see situations where third-party scripts or UI customization tools interfere with Intercom widgets, chat triggers, or tracking. In most cases, the issue is not a direct conflict with Intercom itself, but rather external scripts modifying the DOM, intercepting events, blocking network requests, or throwing JavaScript errors that prevent the Messenger from initializing correctly.

 

To help isolate whether the issue is coming from Intercom or an external tool, here is a step-by-step approach:

1. Reproduce in a clean environment
Test in an incognito or private window with browser extensions disabled. If the issue disappears, that is a strong indicator that an injected script or extension is responsible.

2. Confirm the Messenger is loading correctly
Open DevTools and go to the Network tab to look for Intercom network requests, often referred to as the "ping."
If no Intercom requests appear, the snippet may be blocked or interrupted.
You can also run Intercom('show') in the console to confirm the library is available.

3. If using a Single Page Application (SPA)
Ensure Intercom('update') is called on route changes so messages and triggers can re-check eligibility. Also confirm boot and shutdown are used correctly when user identity changes.

4. Temporarily disable other scripts
If scripts are managed via GTM or another loader, disable all non-essential scripts and re-enable them in batches. This binary search method is often the fastest way to pinpoint the exact script causing the issue.

5. Check for CSS and DOM manipulation
Custom scripts that modify or restyle Intercom elements, overlay page content, or rewrite class names can prevent launchers or tours from working as expected.

If, after isolating external scripts, the issue still occurs in a clean environment with only the Intercom snippet installed, that would be a good point to escalate. For escalation, it would help to gather:

  • Affected URLs

  • Steps to reproduce

  • Console errors, screenshots are fine

  • HAR or network capture showing Intercom requests

  • Whether the site is an SPA

  • A list of third-party scripts currently running

If you are seeing this behavior persist even after disabling external tools, let me know and I am happy to escalate this to our Inbox team for deeper investigation.

Karla T | Leading Community at Intercom
Terms & ConditionsAccessibility statement