Analytics · Beta
Hotjar
API integration
Ship Analytics features without building the integration. Full Hotjar API access via Proxy and 4 MCP-ready tools for AI agents — extend models and mappings to fit your product.
Built for specific customer use cases. Issues are resolved quickly.
Talk to usUse Cases
Why integrate with Hotjar
Common scenarios for SaaS companies building Hotjar integrations for their customers.
Enrich customer health scores with NPS feedback
Customer success platforms can pull Hotjar survey responses into customer profiles, letting their users trigger At-Risk alerts when Detractors submit feedback and attach the originating session recording to the account timeline.
Surface session replays inside support tickets
Helpdesk and ticketing products can match an end user's email to Hotjar survey data and expose the recording URL inside the agent view, cutting time to resolution by letting agents watch the bug happen instead of asking for screenshots.
Automate GDPR data subject deletion requests
Privacy and compliance SaaS can route Right to be Forgotten requests through Hotjar's user lookup endpoint, scrubbing recordings and hits automatically and producing an audit trail without manual admin work in Hotjar.
Bridge quantitative funnel data with qualitative recordings
Product analytics platforms can let analysts click on a drop-off cohort and immediately pull the matching Hotjar recording URLs, giving their customers the 'why' behind the 'what' without leaving the dashboard.
Map Hotjar surveys to internal campaigns
Marketing and CRO tools can list a customer's Hotjar surveys during setup so their users can bind a specific NPS or feedback survey to an internal campaign, segment, or workflow trigger.
What You Can Build
Ship these features with Truto + Hotjar
Concrete product features your team can ship faster by leveraging Truto’s Hotjar integration instead of building from scratch.
Survey picker during integration setup
Use list_all_hotjar_surveys to render a searchable dropdown so your users can pick which Hotjar survey feeds into a given workflow or report.
NPS response ingestion pipeline
Poll list_all_hotjar_survey_responses on a schedule to stream answers, sentiment, and user attributes into your product's customer records or event stream.
Session recording links in your UI
Attach the recording_url from each survey response to tickets, accounts, or bug reports so your users get a one-click replay of what the respondent experienced.
Automated DSAR deletion workflow
Fire create_a_hotjar_user_lookup with delete_all_hits set to true whenever an end user submits a privacy request, and log the result for compliance evidence.
User identity resolution
Use hotjar_user_id and user_attributes from survey responses to match Hotjar sessions back to the corresponding user in your platform's database.
Survey detail viewer
Call get_single_hotjar_survey_by_id to display question structure, type, and sentiment analysis settings inline when a user configures a survey-based automation.
SuperAI
Hotjar AI agent tools
Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.
list_all_hotjar_surveys
List Hotjar surveys for a site. Returns survey objects with id, name, type, is_enabled, created_time, url, responses_url, questions, and sentiment_analysis_enabled. Required: site_id. Max 100 per page.
get_single_hotjar_survey_by_id
Get a single Hotjar survey for a site by id. Returns: id, url, created_time, updated_time, is_enabled, name, responses_url, type, questions, sentiment_analysis_enabled. Questions are always included. Required: site_id, id.
list_all_hotjar_survey_responses
List Hotjar survey responses for a survey, sorted newest first. Returns: id, answers, browser, country, created_time, device, hotjar_user_id, is_complete, os, recording_url, response_origin_url, user_attributes, window_size. Required: site_id, survey_id.
create_a_hotjar_user_lookup
Perform a Hotjar user lookup for a data subject, optionally deleting all found data. Returns an empty 202 Accepted response on success. Required: organization_id. The body must include data_subject_email or data_subject_site_id_to_user_id_map; with delete_all_hits false, a report-link email is sent to the data subject instead of deleting.
Why Truto
Why use Truto’s MCP server for Hotjar
Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 900+ integrations.
Auto-generated, always up to date
Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.
Fine-grained access control
Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.
Multi-tenant by design
Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.
Works with every MCP client
Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.
Built-in auth, rate limits, and error handling
Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.
Expiring and auditable servers
Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.
How It Works
From zero to integrated
Go live with Hotjar in under an hour. No boilerplate, no maintenance burden.
Link your customer’s Hotjar account
Use Truto’s frontend SDK to connect your customer’s Hotjar account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.
We handle authentication
Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.
Call our API, we call Hotjar
Truto’s Proxy API is a 1-to-1 mapping of the Hotjar API. You call us, we call Hotjar, and pass the response back in the same cycle.
Unified response format
Every response follows a single format across all integrations. We translate Hotjar’s pagination into unified cursor-based pagination. Data is always in the result attribute.
FAQs
Common questions about Hotjar on Truto
Authentication, rate limits, data freshness, and everything else you need to know before you integrate.
How does authentication to Hotjar work through Truto?
Truto handles the Hotjar authentication flow for you, so your end users connect their Hotjar account through a hosted or embedded link and you receive a ready-to-use connected account. You never need to store or refresh Hotjar credentials yourself.
Which Hotjar operations are supported today?
The current toolkit includes list_all_hotjar_surveys, get_single_hotjar_survey_by_id, list_all_hotjar_survey_responses, and create_a_hotjar_user_lookup. Additional endpoints can be added on request as part of Truto's build-on-demand model.
How fresh is the survey response data?
Truto exposes list_all_hotjar_survey_responses as a standard polling endpoint, so you can pull new responses on whatever cadence your product requires. Truto handles pagination so you can iterate through full response history without writing cursor logic.
Can we delete user data from Hotjar for GDPR requests?
Yes. The create_a_hotjar_user_lookup tool accepts a data_subject_email and an organization_id, and setting delete_all_hits to true scrubs the user's recordings and hits from Hotjar. Setting it to false triggers Hotjar's automated privacy report to the data subject instead.
Does the survey response payload include session recording links?
Yes. Each response in list_all_hotjar_survey_responses includes the recording_url, hotjar_user_id, user_attributes, and device context such as browser and OS, which is what makes replay-in-ticket and funnel-to-recording features possible.
How does Truto handle Hotjar's API quirks and rate limits?
Truto normalizes pagination, retries, and error handling for Hotjar at the platform layer, and automatically backs off on rate limit responses. Your integration code stays focused on business logic rather than API-specific plumbing.
Hotjar
Get Hotjar integrated into your app
Our team understands what it takes to make a Hotjar integration successful. A short, crisp 30 minute call with folks who understand the problem.