HTMLRadar · Use case
Track the HTML deck you already built.
Your deck is already HTML — a Claude artifact, a Gamma export, a reveal.js build, a hand-rolled page. The old workflow says: flatten it to PDF so a tracker can handle it. HTMLRadar says: keep the HTML, send a tracked link, see who read each section.
How do you share an HTML file as a tracked link?
Upload the file or paste a URL. You get a link like htmlradar.com/r/swift-falcon about sixty seconds after signing in. Replace the file later and every link you already sent serves the new version — old links keep working.
What do you see when someone reads it?
A live dashboard, per recipient: active read time, scroll depth, and time per section — down to which heading they parked on and for how long. A three-second dwell floor keeps scroll-pasts from counting as reads, and an email lands the moment a real read happens.
Does it work with AI-generated decks?
That's the point. Decks from Claude, Gamma, Tome, and Pitch.com exports are HTML already; reveal.js and hand-coded decks always were. If it opens in a browser, HTMLRadar can serve it through a tracked link — single-file HTML with embedded assets works out of the box.
Making decks in Pitch.com? There's a three-step flow for tracking Pitch decks without PDFifying them.
Common questions
- Does HTMLRadar host the file?
- Yes. Upload the HTML and it is hosted and versioned for you — replace the file and old links keep working. Or paste a URL and the proxy serves it through your tracked link.
- Do I have to add a tracking snippet to my deck?
- No. The tracker is injected automatically when the deck is served through your tracked link. Your original file stays untouched.
- What counts as a read?
- Active time with a three-second dwell floor per section — scroll-pasts and accidental opens don't count as reads.
First 10 documents free. No credit card. AGPLv3 source on GitHub.