01
Visitor → customer funnel
Follow sessions all the way to paying customers by joining on user id and landing page.
4-step funnel
Analytics
Hotjar + Kimo
Heatmaps, recordings and on-site surveys. Bring sessions and events next to your product and billing data, so traffic finally connects to signups.
- Auth
- API key
- Sync
- Daily
- Setup
- ≈ 3 min
Live demo workspace with fictional data · no signup, no credentials needed
kimo / connectors / hotjarSyncing
Sync logdaily
- Succeeded:sessions+1,890 rowsnow
- Succeeded:pages+1,109 rows2m ago
- Succeeded:events+1,052 rows4m ago
- Succeeded:sessions+271 rows6m ago
Rows synced · 30 days
71.7M
Workspaces
16%
What you can do
What teams build with Hotjar
Hotjar on its own answers half the question. Joined with the rest of your stack in Kimo, it answers the other half.
02
Landing pages that convert
Rank pages by signups and revenue, not just pageviews or bounce rate.
Signups per 1k sessions
03
Channel mix over time
See how organic, paid, referral and direct shift week over week, without sampling.
Sessions by channel
Objects & tables
Exactly what gets synced
Kimo maps Hotjar into clean, typed tables with primary keys and incremental cursors, so syncs stay fast and joins just work.
3 tables · 15 fields
Tables
sessions
Incremental≈ 32,400,000 rows| Field | Type | Notes |
|---|---|---|
| session_id | id | Primary key |
| date | date | Incremental cursor |
| source | enum | Low-cardinality dimension |
| medium | enum | Low-cardinality dimension |
| landing_page | string |
Custom fields and extra objects are discovered automatically on each sync. Row counts are illustrative.
Sample model
From raw Hotjar tables to a certified metric
A starter model Kimo suggests the moment Hotjar is connected. Every join is editable.
Hotjar · Web engagement
Sessions and events joined with product signups on landing page and user id.
- Hotjarsessions
- PostgreSQLusers
- Google Search Consolesearch_pages
Model
landing_page · user_id
Measuressessionsconversions
Sessions · last 30 days
11.3K+2.8% wk/wk
Fictional data · hover the chart for daily values
Setup
Connect Hotjar in 3 min
No engineers, no pipelines to maintain. Kimo asks for the minimum access it needs and tells you exactly what it will read.
- 1
Create a read-only key in Hotjar
Use a dedicated key scoped to read access, so it can be rotated independently.
- 2
Paste it into Kimo
Keys are encrypted with a per-workspace key and never shown again.
- 3
Choose streams
Pick which objects to sync, starting with sessions.
- 4
Validate and sync
Kimo tests the key, backfills history and keeps it fresh (daily).
Read-only, encrypted, revocable. Credentials are encrypted with a per-workspace key, never logged, and can be rotated without breaking your models.
Connect Hotjar
Step 2 of 3 · Kimo demo workspace
- Reaching host
- Authenticating
- Reading schema
Read-only access
Illustration only · placeholder values, never real secrets
Works great with
Pair Hotjar with the rest of your stack
Kimo suggests these joins automatically when both sources are connected.
FAQ
Hotjar questions, answered
By default Kimo syncs Hotjar daily. You can change the schedule per table, or trigger a sync manually from the connector page.
Hotjar · API key · Daily
See your Hotjar data in Kimo in 3 min.
Try it on the live demo workspace first, then connect your own account when you are ready.
