Just the Hotjar tracking script. If Hotjar is already loaded on the page, SleekAI detects the global hj function and starts firing events. There is no extra Hotjar plugin to install on WordPress and no extra integration to maintain in Hotjar's own dashboard.

By default sleekai_open when the widget opens, sleekai_handoff when escalation runs, and sleekai_resolved when the visitor closes a chat marked as resolved. You can rename them or add more by editing the chatbot's tracking config. They appear as Custom Events inside Hotjar Recordings.

When the visitor is logged into WordPress, yes. SleekAI calls hj identify with the WP user id and the attributes you configure (role, plan, signup date). For anonymous visitors, the events still fire but no identify call is made, which keeps the privacy posture clean.

No. The events ride on whatever consent state Hotjar already has. If your visitor declined Hotjar tracking, the hj global will not fire and SleekAI's calls become no-ops. If consent is granted, events flow normally alongside the rest of your Hotjar data.

Open Hotjar Recordings, add a filter by Event, and choose sleekai_open, sleekai_handoff, or sleekai_resolved. The recording list narrows to sessions where the event fired. Most teams build saved filters per outcome and reach for them weekly.

No. The events carry only the event name. The actual chat messages stay in the SleekAI conversation log on your WordPress server. If your visitors type sensitive info into chat, the Hotjar recording does not see those keystrokes inside the chatbot iframe by default.

Yes. SleekAI's events fire through the same hj API that both products use. Observe handles the recordings and heatmaps you filter on. Engage uses User Attributes for targeting, which the same identify call populates whenever the WordPress user is signed in.

Hotjar records the host page, not the chatbot iframe contents. The chatbot itself stays out of recordings by default, which is usually the right behaviour for privacy. SleekAI's events still fire from the parent context, so the session timeline shows when the chat opened without recording its contents.