Quick note: I got roasted on Reddit and it fixed my product

Posted an offer in r/Ghost this weekend. Got told my API key claim was wrong (it was — a Ghost expert corrected me), that I needed a privacy policy (fair), and that my replies sounded like AI (they did — guilty, stopped).

Within 48 hours: claim corrected everywhere, privacy page shipped, and I now write my own replies, typos included.

Lesson I'm keeping: strangers who attack your mechanism and never attack your idea are handing you a to-do list, not a verdict. Nobody in that thread said "knowing which content retains paying subscribers is useless." They said "I don't trust how you're doing it yet." Different problem. Fixable problem.

5 things I learned about Ghost this week

1. There's no read-only Admin API key. One key, full permissions — which is why the right hygiene is a dedicated custom integration you delete after use. (Thanks to Cathy Sarisky on the Ghost Forum for the correction.) 2. Ghost 6's native analytics attribute paid conversions

Why signup counts point you at the wrong content

Every newsletter dashboard celebrates the same moment: someone subscribed. Big number goes up. The post that caused it gets the credit. Here's the problem I keep running into while building a revenue analytics tool for newsletters: the subscriber who signs up from a viral hot take and the

Coming soon

This is Building Subloop, a brand new site by Sam packer that's just getting started. Things will be up and running here shortly, but you can subscribe in the meantime if you'd like to stay up to date and receive emails when new content is published!

Read more

5 things I learned about Ghost this week

Why signup counts point you at the wrong content

Coming soon