Contentsquare (Hotjar)

introduction hotjar is a behavior analytics and feedback tool that helps you understand how users interact with your site through heatmaps, session recordings, and on site surveys by tracking user sessions and interactions, hotjar gives product, ux, and marketing teams a clearer picture of what’s working—and what needs improvement—across the customer journey getting started this is a device mode destination, which means chord helps you send events directly from your site to hotjar to connect hotjar as a cdp destination, you’ll need your hotjar site id you can find this in your hotjar account under settings → sites & organizations → tracking code the site id is the numeric value associated with your site (often shown in or alongside the tracking code, such as the number after hjid= ) make sure you have an active hotjar account and site set up permissions to access the site id any internal approvals required to add or modify tracking on your site connecting to the contentsquare (hotjar) cdp destination log into the chord data platform navigate to the cdp click the “add” button next to destinations select contentsquare (hotjar) from the destination catalog enter a destination name that your team will recognize (e g , “hotjar – production”) enter your contentsquare site id click “create” to connect the destination once connected, chord will begin sending the relevant events to hotjar based on your cdp configuration and tracking setup avoiding duplicate tracking before connecting destinations in the chord cdp, please verify with all destination owners that any non–chord cdp–configured contentsquare (hotjar) tracking (for example, legacy tags installed directly on your site, in your tag manager, or via another platform) is disabled or removed where appropriate running external hotjar tags alongside the configured chord cdp destination can result in duplicate pageview/session data in hotjar inflated heatmaps and session recordings confusing or misleading analytics for product and ux teams if you’re unsure whether legacy hotjar tracking is still installed, coordinate with your engineering or analytics team to review existing tags and scripts before enabling the destination chord events relevant for destination not all chord tracking events are used downstream in your configured destinations the most relevant and important events in the chord tracking plan are mapped within the cdp destination, relayed and then ingested in the destination given this, contentsquare does not support any explicit event filtering an will accept all chord tracking events before connecting destinations in the chord cdp, please verify with all destination owners that all non chord cdp configured destinations are disabled running external destinations alongside configured chord cdp destinations can result in duplicate events downstream