2,192
Visits
▲ 18%
The output
A visit, written out
Not a heatmap you have to interpret or a video you have to sit through. A description of what someone was doing, and what they wanted.
- 0sArrived from a Google search for “memory care near me”, landing on /communities.
- 9sRead the whole comparison table, all 100% of the page.
- 34sSpent 40s on the “Costs & funding” section, longest of any section.
- 1m18sSearched the site for “respite care” and got no results.
- 1m52sOpened two listings in background tabs and came back.
- 2m20sCopied a phone number.
One visit is interesting. Ten thousand of them, in language you can query, tells you what your audience is actually here for, and what you haven’t built yet.
What you learn
Six things your analytics won’t tell you
01
Where your traffic actually comes from
Every session carries its full origin: campaign, keyword, click ID, referrer, or a QR scan on a printed flyer. No more “direct / none” black holes swallowing a third of your visits.
02
What people came looking for
Site searches, the sections they linger in, the listings they compare. Search terms that return nothing are content you should have and don’t.
03
What holds attention
Active engagement time per section, not time-on-page inflated by an abandoned tab. You learn which paragraph people actually read.
04
Where people get stuck
Hunt-scrolling, clicks that do nothing, forms that fight back, error messages nobody told you were firing. The friction a bounce rate can never show you.
05
The touchpoints you’re blind to
Copied phone numbers, printed pages, scanned codes. Real intent that lives offline and never appears in a funnel.
06
Whether speed is costing you
Core Web Vitals recorded per session and joined to what happened next. Not “our LCP is 3.1s” but “slow sessions behave differently, and here is how”.
Online meets offline
QR codes that report back
Generate a code, print it, and see the scans by placement, by hour, and by whether the same phone came back. Redirect a code that is already on five thousand flyers without reprinting one of them.
Placement A/B
Window, flyer, table tent, trade-show badge. One campaign, separate codes, and a real answer about which physical spot works.
Scans vs sessions
Scans are recorded before the redirect, so a code with plenty of scans and no visits tells you the landing page is the problem.
Dynamic destinations
Send scans somewhere different by time of day, day of week, or once a run sells out. The printed code never changes.
Install
One line, then it’s running
No tag manager, no build step, no rewrite of your site.
<script src="https://spooly.com/s.js" data-site="YOUR_KEY" defer></script>
14.9 KB, async, every listener passive. It is never the reason your page feels slow.
Track more, store less
Rich data without the baggage
Spooly captures more signal than a replay tool and keeps far less of the material that makes analytics awkward to own. You get the detail. You skip the liability.
Nothing to redact
Form values are never read. Spooly knows a field took 22 seconds and was left empty, never what someone typed into it. No customer PII ends up sitting in your analytics waiting to become a problem.
Nothing to subpoena
There are no screen recordings, so there is no video library to store, secure, retain, or hand over. The thing that makes replay tools a legal conversation simply does not exist here.
A smaller compliance surface
Anonymous IDs, hashed IPs with a salt you can rotate, optional IP truncation, and no cross-site tracking. Less to explain in a vendor review, and less to argue about with legal.
Pricing
From $15 a month, tried free for 14 days
Every plan gets the full product; they differ only in traffic. Roughly half the price of the replay tools, because we never store video and video is what makes them expensive.
Find out what your traffic wants
Add one line, then read your first sessions in plain language within minutes.
Start free