Product Analytics Software Resources
Articles, Glossary Terms, Discussions, and Reports to expand your knowledge on Product Analytics Software
Resource pages are designed to give you a cross-section of information we have on specific categories. You'll find articles from our experts, feature definitions, discussions from users like you, and reports from industry data.
Product Analytics Software Articles
G2 Launches New Attribute for Its Heatmap Tools Category
Product Analytics Software Glossary Terms
Product Analytics Software Discussions
I was testing out Keen on a hobby project a couple of years ago and it was pretty neat. Easy to get up and running with nice charts and metrics. Fast-forward a few years, and Keen decides to change their billing to a usage tier based system. I got the mail about it. I checked my usage and I was quite a bit under the 50,000 free events per month, so no sweat. Then I start receiving $150/mo bills from them for my measly 2500 events monthly. Being busy I didn't catch this right away, and now have been charged 3 months at this rate. Once I caught the issue, I wrote to them, expecting to get an easy refund for mistaken charges, but no. They basically pulled a "well in our TOS it says..." on me, claiming that I had been notified by email about the pricing change. I had been notified, but nothing lead me to believe I would start receiving $150/mo bills from them. Now I'm a week into this pain in the ass, and no progress on getting a refund. Is my few hundred dollars really that important to you Keen? Seems like a pretty poor way to build a business if you ask me.
Integrations
The session replay overlap question is what I’m exploring here: is Fullstory worth using alongside a product analytics tool, or does it end up being redundant once a team has solid funnel and event tracking in place?
The split seems practical. Fullstory may still be worth it when teams need to query and analyze session behavior at scale, not just watch individual recordings.
It may feel redundant when native replay already gives enough context inside the analytics workflow. LogRocket overlaps heavily because replay is paired with performance, network, and error context. PostHog connects replay directly to events and funnels. Amplitude Analytics makes replay useful for debugging funnel drop-offs inside the same workflow.
I’d be especially interested in how teams kept reporting usable during migration, and what became hardest to trust first.





