FeedPulse is coming soon on PH

Build update: install pages for WordPress, Shopify and Wix

The most common question I get isn't "what does it do", it's "where do I
paste this on my site". So this week I shipped install pages per platform,
with the real menu paths instead of a generic "add it to your HTML":

- WordPress: feed-pulse.com/wordpress
- Shopify: feed-pulse.com/shopify
- Wix: feed-pulse.com/wix

Each widget gets its own page per platform, because the correct place to
paste differs: a comments widget belongs in the blog-post template, a
visitor counter belongs in the footer, a heatmap belongs in the <head>.

Wix was the most interesting to research. Its embeds run in a sandboxed
iframe, so auto-resize is impossible and you set the height by hand —
separately again in the mobile editor. And Settings > Custom Code needs a
connected domain, i.e. Premium, so free wixsite.com users have to use the
embed element instead. Nobody documents that clearly, so it's now written
on every Wix page.

Next up: Webflow and Squarespace. If you're on a platform I haven't
covered, say which one and it jumps the queue.

Build update: why "free forever" isn't a bait-and-switch

A fair question I got last time: what happens when the bill arrives?

Here's the honest shape of it. One shared runtime serves every widget, so a site running four of them pulls almost the same bytes as a site running one. Visitor events are hashed and aggregated server-side — I don't store raw IPs or per-visitor histories, which means there's no storage curve that grows with traffic the way an analytics product's does. Country-level aggregation and a 24-hour dedup window, and that's it.

That's the whole reason the promise is possible. It isn't generosity, it's that the expensive part of analytics is the part I deliberately didn't build.

If costs ever outrun that, the next step is ad-supported, not paywalled — and I'd post here 30 days before any change.

Still taking widget requests. What's the one you've wanted and never found free?