Key differences
| Criterion | PostHog | Heap by Contentsquare |
|---|---|---|
| Center of gravity | Engineering and product-data platform | Autocapture-first product and experience analytics |
| Autocapture | Common web interactions plus reusable Actions | Defining workflow with visual labels and repair |
| Funnels and paths | Funnels, retention, cohorts, and paths | Funnels, retention, segments, and Journeys |
| Replay and heatmaps | Usage-metered web/mobile replay; current and beta heatmap surfaces | Experience Analytics add-on with replay and heatmaps |
| Flags and experiments | Native usage-metered products | Analyzes external experiment data; no native flag-delivery product found |
| Errors and logs | Native separately metered products | Error Analysis add-on; no comparable general log product found |
| B2B accounts | Paid Group Analytics | Account-Based Analytics on qualifying plans |
| Deployment | Cloud plus unsupported MIT-licensed hobby path | No public self-hosted application found |
| Paid pricing | Public product-specific usage rates | Session-based plans and add-ons; most rates require a quote |
Decision spectrum
Where each platform puts its center of gravity
Decision by scenario
| Scenario | Start with | Why | Important limitation |
|---|---|---|---|
| Engineering-led startup | PostHog | Integrated analytics, replay, flags, experiments, and developer tools | Several meters and products need owners |
| Missed historical front-end instrumentation | Heap | Retrospective visual definition and repair are central | Only retained captured evidence can be redefined |
| Enterprise experience team | Heap/Contentsquare | Journeys, replay, heatmaps, friction, and ecosystem alignment | Verify modules, add-ons, regions, and contract |
| Native feature delivery | PostHog | Flags and experiments share the product event model | A specialist may be stronger for complex release governance |
| B2B SaaS accounts | Evaluate both | Both offer paid account/group models | Measure breadth and user concentration explicitly |
| Mobile application | Pilot both | Both document mobile analytics and replay | Test SDK parity, privacy, fidelity, and app impact |
| Self-hosting required | PostHog or another category | Only self-managed path here | Unsupported and customer-operated |
| Customer-success outreach | Another category | Neither is a full CS workflow | Use their behavior as evidence for a separate playbook |
Autocapture and retroactive analysis
Both products autocapture common interactions and let teams add meaning later. Heap makes that workflow more central; PostHog connects the resulting definition to a wider product-engineering platform.
| Question | PostHog | Heap | Hard limit |
|---|---|---|---|
| Automatic evidence | Common web clicks, changes, submissions, and navigation data | Common web interactions and supported mobile capture | Privacy rules can and should suppress fields |
| Definition later | Actions over retained raw events and properties | Visual/manual event labels over retained interactions | Missing properties cannot be invented |
| UI change | Selector/text Actions can drift | Definitions can drift; history and repair workflows help | Both require monitoring |
| Server success | Send an explicit SDK/API event | Send an explicit Track API event | Browser clicks are not authoritative outcomes |
| History | Depends on retained analytics/replay data and plan | Depends on plan, add-ons, and accessible history | Expired data cannot be recovered |
Missing-event investigation
From an untracked release question to a durable metric
- 1ReleaseShip the interface change.
- 2Untracked interactionA new question appears.
- 3Automatic evidenceCheck retained captured behavior.
- 4Semantic reconstructionDefine the interaction over that evidence.
- 5Server outcomeConfirm whether the business action succeeded.
- 6ReplayInspect the surrounding session when retained.
- 7Future instrumentationAdd a stable semantic or server event.
PostHog path
Raw event → ActionApply a reusable definition to retained captured events.Heap path
Captured interaction → visual definition or repairLabel the interaction, inspect history, and repair the definition when the interface changes.Hard limit: If the interaction, required property, error, or outcome was not captured—or the data expired—it cannot be reconstructed retroactively.
Analytics, replay, and B2B accounts
Both support funnels, retention, reusable audiences, paths or journeys, and replay-linked investigation. Heap’s visual definitions and Journeys favor experience-led exploration. PostHog’s cohorts, insights, and replay favor workflows that continue into flags, experiments, errors, and engineering context.
| Capability | PostHog | Heap | Decision implication |
|---|---|---|---|
| Funnels | Ordering, exclusions, windows, cohorts, and filters | Funnels connected to segments and visual definitions | Pilot exact sequence rules |
| Paths/Journeys | Paths and related insights | Prominent user, session, and account Journeys | Heap has the clearer experience-analysis emphasis |
| Replay | Web/mobile usage allowances and report filters | Experience Analytics add-on on qualifying plans | Test framework fidelity and retention |
| Developer evidence | Console, network, errors, flags, releases, and properties | Replay, friction, heatmaps, and Error Analysis emphasis | PostHog fits engineering diagnosis; Heap fits experience diagnosis |
| Accounts | Paid Group Analytics across insights, flags, and experiments | Account-Based Analytics on Pro/Premier | Attach account context at event time |
An account funnel answers whether anyone at a company completed the steps. It does not automatically reveal adoption breadth, user penetration, or champion concentration. Define those separately and inspect the sessions behind material changes. See account vs user adoption and session replay vs product analytics.
Product platform and deployment
PostHog extends beyond analytics into feature delivery, experiments, surveys, errors, logs, AI/LLM observability, warehouses, pipelines, destinations, and workflows. Heap is part of Contentsquare’s broader digital-experience environment, while standalone Heap packaging emphasizes analytics and sells major capabilities such as Experience Analytics, Error Analysis, Heap Connect, and Activate through plan/add-on entitlements.
PostHog’s consolidation can reduce context switching, but each product needs an owner, privacy model, meter, retention rule, and maturity test. Heap’s focused experience workflow can be easier for product teams, but sales-led packaging means buyers must make entitlements and limits explicit in the quote.
Platform layers
What is native, separately metered, or externally supplied?
| Layer | PostHog | Heap by Contentsquare |
|---|---|---|
| Collection | Native | Native |
| Analytics | Native | Native |
| Replay | Native but separately metered | Add-on |
| Experiments | Native | Third-party integration |
| Flags | Native | Not identified in current public packaging |
| Surveys | Native but separately metered | Wider ecosystem or separate contract |
| Errors | Native but separately metered | Add-on |
| Warehouse | Native but separately metered | Add-on |
| Automation | Native but separately metered | Add-on |
For deployment, PostHog Cloud is the documented recommendation for most organizations. The open-source self-hosted path is labeled a hobby deployment without support or guarantees, and paid-plan features are Cloud-only. Heap has no public self-hosted application offering. Self-hosting also does not create compliance automatically: minimization, masking, access, deletion, backups, monitoring, and incident response remain necessary.
Pricing and customer ratings
Pricing and rating data was verified August 9, 2026. PostHog exposes many public meters; Heap exposes a free allowance and session-based packaging, while most paid dollar rates and major add-ons require a quote.
PostHog pricing
PostHog
1M events
- Replay
- 5,000 web and 2,500 mobile recordings
- Flags
- 1M requests
- Groups
- Paid identified-event meter
- Other products
- Separate survey, error, log, warehouse, pipeline, workflow, and AI meters
Heap pricing
Heap by Contentsquare
10K sessions
- History
- Six months on Free; plan/add-on dependent thereafter
- Paid unit
- Monthly sessions plus plan and add-on packaging
- Replay/errors
- Experience Analytics custom-quoted add-on
- Accounts
- Account-Based Analytics on qualifying plans
Detailed pricing cautions
PostHog’s first paid rates differed by anonymous versus identified analytics events and by each product meter. A Heap quote should specify session calculation, environments, history, Account-Based Analytics, Experience Analytics, replay sampling and retention, Error Analysis, Heatmaps, Connect, Activate, regions, support, overages, and contract minimums. Compare the same workload and count implementation, governance, privacy, warehouse, training, and companion tools.
Ratings are directional signals, not benchmarks. Use themes to define a proof of concept; they cannot prove security, performance, data correctness, contract quality, or fit at your scale.
Which should you choose?
| Choice | Choose it when | Implementation caveat |
|---|---|---|
| PostHog | Engineering wants an integrated product-building and evidence platform | Assign owners and budgets to every enabled product |
| Heap | Autocapture, retroactive definition, Journeys, and experience analysis lead | Make every paid entitlement, history rule, and add-on explicit |
| Use both temporarily | You are migrating or validating a release workflow | Historical definitions and replays are not portable |
Pilot the same missed-event investigation, funnel, retention cohort, account analysis, replay diagnosis, and governance repair. Measure time to a trusted answer, maintenance after a UI change, privacy controls, and total operating cost.
Where Hymetry fits
Hymetry is narrower account-centric product intelligence for B2B SaaS. It fits when teams need to understand how Companies and their Users adopt grouped Pages or product areas, how broad and concentrated that adoption is, and which Visits explain a signal.
| Decision | Consider Hymetry when | Choose PostHog or Heap when | Hymetry’s limitation |
|---|---|---|---|
| Primary unit | Customer company and users inside it | General events, persons, sessions, or journeys lead | Narrower analytical surface |
| Investigation | Account signal → adoption breadth → users → Visits | Flexible analysis or broad experience evidence is primary | Smaller ecosystem |
| Platform need | Flags, experiments, errors, and enterprise DX are not central | You need PostHog engineering breadth or Heap/Contentsquare experience breadth | No comparable general platform |
Explore Companies, Users, Pages, and Visits.
Frequently asked questions
Which has stronger autocapture?
Heap makes autocapture, visual definition, history, and repair the center of its product workflow. PostHog also autocaptures common web interactions and supports retrospective Actions, but its center of gravity is the broader engineering platform.
Can both define events retroactively?
Yes, over retained evidence. PostHog Actions can classify previously captured raw events; Heap can label captured interactions and repair definitions. Neither can recover a property, business outcome, or session that was never captured or has expired.
Which has better session replay?
PostHog connects replay to engineering evidence such as flags and errors. Heap connects replay to Journeys, heatmaps, friction, and experience analysis. Test the exact web/mobile framework, masking, search, retention, and plan entitlement.
Which includes feature flags and experiments?
PostHog includes native flag delivery and experiment analysis billed through flag requests. Heap can analyze externally supplied experiment variants but no comparable native standalone flag-delivery product was identified in current public packaging.
Which supports B2B account analytics?
Both do through paid packaging: PostHog Group Analytics and Heap Account-Based Analytics. Both need stable company context. Neither automatically calculates adoption breadth, user penetration, or champion concentration without deliberate definitions.
Which can be self-hosted?
Only PostHog has a documented self-host path, and its own guidance labels it an unsupported hobby deployment without guarantees; paid-plan features are Cloud-only. No public self-hosted Heap application was found.
Sources
Disclosure: Hymetry publishes this comparison and appears only where its narrower B2B account model is relevant. Ownership, product claims, prices, ratings, and video metadata were verified August 9, 2026 and may change.
Methodology and evidence limits
Official PostHog, Heap, and Contentsquare product, pricing, implementation, privacy, and deployment documentation was prioritized. G2 supplied the shared rating source. Vendor and commercial-agency videos provide disclosed workflow orientation only.
No authenticated tenant, quote, or performance benchmark was used. Heap paid dollar pricing remains quote-based, and PostHog rates are point-in-time references.
Full source directory
Ownership and pricing
- Contentsquare completes Heap acquisition and Product Analytics, formerly Heap
- PostHog pricing and Heap pricing
PostHog official sources
- Autocapture, Actions, and event capture
- Funnels, Retention, Group Analytics, and Session Replay
- Feature Flags, Experiments, Error Tracking, and self-hosting disclaimer
Heap and Contentsquare official sources
- Autocaptured Data, labeling events, and Event Repair Flow
- Funnels, Retention, Journeys, and Account Health Analysis
- Session Replay, Experience Analytics, and Heap Connect
Ratings and video context
Additional preserved references
These references supported the original detailed article and remain available for claim verification and further reading.
- Optimizely X integration
- Contentsquare Voice of Customer
- Error events in replay
- Data Warehouses overview
- Heap: Chart Alerts
- Self-host PostHog
- PostHog: Privacy
- 4.5/5 · approximately 1,050 reviews
- Heap’s next chapter in Contentsquare
- Heap by Contentsquare
- PostHog Product Analytics
- Paths
- Replay retention
- Heatmaps
- Surveys
- PostHog: Logs
- AI Observability
- Data warehouse
- Managed warehouse
- Data pipelines
- Workflow builder
- Subscriptions and alerts
- Snapshots overview
- Client-side versus server-side custom events
- Heap Track API
- Single-page applications
- Data Governance overview
- Heap web SDK
- Heap data model
- Segments
- Usage over time
- Heatmap analysis
- Mobile crash events
- Replay privacy and capture FAQs
- Heap Connect schema
- Managing Heap Connect synchronization
- Heap data history
- VWO integration
- A/B testing with Heap
- A/B testing and personalization integrations
- Delighted integration
- Vision Labs product-analytics comparison
- G2 Heap versus PostHog comparison
- self-hosted product analytics
- product usage by company





