Back
Plausible
Mentioned in 49 todos by 30 makers.
Mentions over time
Loading...
Sentiment
Loading...
Praised in 6.1% of mentions (site average 9.9%), complaints in 4.1% (average 3.7%).
What makers are doing
Loading...
Often used together with
Do you make Plausible?
See everything makers say about it: every mention with praise and complaints, sentiment trends, weekly email digests, and CSV export.
Explore InsightsRecent todos mentioning Plausible
replace Plausible with Pirsch tracking and admin metrics #startupmarketingtools
Wow, I accidentally configured something in Plausible. Now they're demanding $150, or my account is suspended.
I tried to reason with them and told them it was an accident. They said, "It's been 2 months, you're too late. Pay up or else. Ridiculous.
My self-hosted Plausible CE v2 instance went down due to running out of disk space.
So what did I do?
Naturally, I went on a complete DERAIL and started rearranging things:
1. Moving it to another domain
2. Launching Plausible CE v3
3. Cleaning up my Plausible VPS
4. Freeing up disk space
Random Tip - Export all of your Analytics (GA, Plausible), Orders or payments (Stripe, WooCom, Shopify, Lemon S.), Email automations & Campaigns (Klayvio, Resend, Convert Kit) data.
Make it AI accessible via Chroma or dump into large context LLM and have it create a report, Example prompt:
Based on our email campaign and flow data what useful insights can you provide:
- What works
- What doesn't work
- Where can we improve
- What are your key insights
Do you have any ideas for new types of campaigns? Do you have any ideas for automated email flows? Is there any quick wins we may be missing?
Be very detailed and reply with a clean and structured output.
Go through each report and load up whatever todo list software you use. I found a bunch of awesome fixes or strategies to improve.
#huskyarmory
I decided to redesign the top errors view for
#telebugs
The previous version was an experiment inspired by Plausible, but after a Monday of reflection, I realized it wasn’t the right direction.
So, I went with a more traditional approach.
What's new:
✅ Removed "top culprits"
✅ Replaced it with a simple, familiar table for the error list.