- Budget-constrained, high-volume event products
- If an organization expects rapid event growth (tens of millions+ per month), community feedback suggests billing can increase substantially and may be difficult to justify unless platform usage is broad across teams.
- If an organization requires self-hosting or full data control
- Open-source/self-hosted alternatives such as PostHog are typically selected when self-hosting, transparency, and internal control are mandatory.
- If basic web analytics suffice
- GA4 or lighter-weight tools (e.g., Plausible) may be sufficient when advanced event-based product analytics are not required.
- If the workflow is primarily qualitative UX research
- Specialist session-replay and UX tools (FullStory, Hotjar) may provide deeper behavioral tooling depending on the use case.
- If security incident optics are a procurement deal-breaker
- Some organizations will exclude vendors with high-profile security incidents regardless of current certifications; this depends on procurement risk tolerance.
- Pricing unpredictability at scale
- Community feedback frequently cites event-volume billing as a source of unexpected costs, particularly when teams instrument many low-value events.
- Instrumentation governance burden
- Maintaining consistent event naming, identity resolution, and property hygiene requires ongoing governance.
- Data accuracy skepticism
- Discrepancies versus raw warehouse data commonly stem from instrumentation differences, identity stitching, processing filters, or sampling; teams should validate definitions and pipelines.
- Security incident history
- Documented incidents in 2018 and reporting in 2025 are relevant for diligence; procurement teams should request up-to-date security documentation and incident summaries.
- Roadmap and feature entitlement uncertainty
- Session replay entitlements and included volumes have varied over time; buyers should confirm current entitlements per plan and how replay usage is counted toward quotas.