Overview
Governance classification of this tag is complicated by its dual nature. The same JavaScript snippet serves both customer support and marketing automation (behavioural targeting, product tours). Collects visitor behaviour data including page views, session duration, and custom events, transmitting it to US-based servers. Organisations must carefully delineate which Intercom features are active, because the two uses collect the same data for very different purposes.
Detection capabilities
- Signature count
- 5
- Detection methods
- network
- Property types
- hostnamepathname
Performance impact
Performance Impact
- Script size
- 250 KB
- Requests per page
- 2
Common mistakes
- 1Treating Intercom as purely a customer support tool exempt from consent requirements, when it also collects behavioural data for marketing segmentation and automated messaging
- 2Loading the Intercom messenger widget on all pages without assessing whether the behavioural tracking it performs is proportionate - Intercom tracks page views and session data even when the chat is not used
- 3Not configuring Intercom's identity verification, which can allow impersonation of logged-in users through the client-side API
- 4Failing to assess the data stored in Intercom's platform against data retention policies - conversation histories and user profiles can accumulate significant personal data over time
- 5Using Intercom's product tours and targeted messaging features without recognising that these involve behavioural profiling that may require separate consent
Related services
Scan your site for intercom
Run a free ConsentMark scan to see how intercom is loading on your site, whether it respects consent, and where governance gaps exist across your wider tag estate.
Start a free scan