Hotjar, joined to everything else.
DataGlue joins what Hotjar records with your other systems, in one view of each customer. Every count shows how it was worked out, and opens to its records.
Hotjar: A behaviour analytics tool for heatmaps, recordings and on-site surveys.
- NO NATIVE CONNECTOR · WEBHOOK
Bring Hotjar and one decision to the call. Tool names are enough; no access needed.
Trusted by
- Webhook
- Automation
- File export
What comes in from Hotjar. Survey and feedback responses come in on each person's timeline.
Webhook
Hotjar sends a webhook to a DataGlue inbound URL when a record is created or changes. Its fields are mapped to people and events once, in the build. Each recorded event keeps Hotjar as its source.
Automation
No direct connector. An automation tool such as Zapier, Make or IFTTT runs in your own account, where it supports Hotjar.
A trigger in Hotjar posts each new record to our REST API.
File export
Export a CSV from Hotjar and import it. Each row keeps its own id, so a re-upload updates the same people and adds no duplicates. Recurring drops are agreed in the build.
There is no native Hotjar connector today; the routes above are how it joins. Deliver results by signed webhook. Read them through our API, ask from an AI assistant that supports MCP, or export on request. Connections are agreed in the build. Before we promise a joined-up journey, we check what the source records, what consent covers and which details link people. Hotjar is a trademark of its owner; this page implies no partnership or endorsement.
Name the result you want. DataGlue shows how it counts, in plain English.
- 01
With Workspace AI on, describe the result you want in plain English. Without it, build the outcome step by step.
- 02
DataGlue drafts the rule from what each field in your data means, Hotjar included, and shows how it counts.
- 03
Use the result in your tools through the open route.
01
With Workspace AI on, describe the result you want in plain English. Without it, build the outcome step by step.
02
DataGlue drafts the rule from what each field in your data means, Hotjar included, and shows how it counts.
03
Use the result in your tools through the open route.
- EXAMPLE OUTCOME 01
Survey answered, then signed
HOW IT COUNTSSurvey answered, then Deal signed within 60 days, for the same person.
- EXAMPLE OUTCOME 02
Low feedback, then a ticket
HOW IT COUNTSLow feedback score given, then Support ticket opened within 7 days, for the same person.
Examples only. Which ones your data supports is checked with you in the working session.
Want one of these from your Hotjar data? We map the route and the first outcome on the call.
Book a CallBring Hotjar and one decision. We'll map the route and the first outcome on the call.
The call is about fit. Any build is a separate engagement, priced before work begins.