Hotjar vs PostHog for website research and product analytics
Pick the current Contentsquare route for Hotjar-style website research, heatmaps and feedback; pick PostHog when product events, replay and engineering work need to connect. Hotjar vs PostHog now includes a product transition: new Hotjar accounts are unavailable and new users join Contentsquare. Compare the current capture allowances and workflow, while existing Hotjar customers check their own migration offer and sampling terms.
On this page
Hotjar vs PostHog comparison
The table separates monthly analytics sessions, events and replay recordings because they are different units.
| Decision | Hotjar's current Contentsquare route | PostHog |
|---|---|---|
| New account | Contentsquare signup | PostHog signup |
| Free analytics allowance | Up to 200,000 sessions/month on Experience Analytics Free | 1 million analytics events/month |
| Free web replay allowance | 5% of sessions, maximum 10,000 replays/month | 5,000 web recordings/month |
| Free data access | 1 month for Experience Analytics and replay | 1 year for analytics; 1 month for free web replay |
| Paid basis | Selected product, session or response volume and plan | Usage per product; analytics and replay billed separately |
Sources: Hotjar's current product page, Contentsquare pricing, PostHog analytics pricing and PostHog replay pricing. A 200,000-session analytics allowance does not mean 200,000 replay recordings.
At Martechdevs, we connect event definitions, capture controls and investigation workflows through product analytics implementation. We would start a website conversion-research pilot with Contentsquare when the team mainly needs to inspect pages and collect feedback. We would start with PostHog when the product team needs to connect a measured behaviour to a recording and an engineering change.
Both candidates now cover more than their older reputations suggest. Contentsquare includes several analytics products, while PostHog includes surveys and web analytics alongside product analytics. Make the choice from the work your team will perform and the specific plan that supports it.
Tool decisions
Contentsquare for Hotjar users
- Best for: Website and experience teams investigating page behaviour, friction and feedback, including teams moving from Hotjar.
- Pros: The current route combines heatmaps, session replay, funnels and survey options. Contentsquare distinguishes Experience Analytics, Voice of Customer and Product Analytics as separate product scopes. Current product structure.
- Cons: An analytics session allowance is different from replay capture. Legacy migration offers can also have account-specific sampling and temporary discounts that differ from a new public offer.
- Free plan and startup offer: Experience Analytics Free includes up to 200,000 monthly sessions, with replay sampled at 5% and capped at 10,000. New accounts receive a 15-day Growth trial. No general startup concession is assumed. Plans and evaluation terms.
- Choose it if: The team can turn page-level observations and feedback into a concrete website change and validate the result.
- Skip it if: The primary requirement is an engineering-led product-event workflow and the proposed Contentsquare scope does not cover that work at an acceptable cost.
For an existing Hotjar customer, begin with the migration notice. Contentsquare says it can apply a custom sampling rate and a one-year Hotjar Loyalty Discount, with the applicable details in the customer's communication. The end of that discount does not automatically change the custom sampling rate. Migration sampling and pricing.
That is a reason to separate the first-year bill from the continuing capture policy. A team can lose a discount while retaining the same sample. Record both terms in the budget and evaluate whether the available recordings answer the intended research question.
PostHog
- Best for: Product and engineering teams connecting event analysis with session-level investigation and release work.
- Pros: Analytics can connect to relevant recordings, and replay can be filtered by events and user properties. This supports an investigation that begins with a measured behaviour and moves to its context. Analytics workflow, session replay.
- Cons: Usage is metered separately across products. Broad capture without event ownership can increase the bill and make analysis harder to interpret.
- Free plan and startup offer: Monthly allowances include 1 million analytics events and 5,000 web recordings. Eligible startups can apply for $50,000 of credits valid for 12 months; company-age, funding, signup and company-email conditions apply. Pricing, startup terms.
- Choose it if: A named team can maintain event meaning, identity, replay settings and the changes prompted by the analysis.
- Skip it if: The organization mainly wants periodic website research and has nobody responsible for an ongoing product-event implementation.
A PostHog pilot should start with a business event that has a dependable meaning. A button click might indicate an attempt, while a server-confirmed completion indicates success. Connect both only if they answer different questions, and keep the event names clear enough for another analyst to use.
The tracking-plan guide helps define that contract. The event-naming guide helps prevent the same action from appearing under several labels. A larger event allowance is useful only if the captured events remain understandable.
Research questions and evidence
Choose a question before choosing recordings. Watching an unstructured collection of sessions can consume time without producing a decision.
| Business question | Quantitative evidence | Session or feedback evidence | Decision owner |
|---|---|---|---|
| Signup abandonment | Completion rate by device and entry route | Failed form interaction or misunderstood step | Growth and product |
| Feature activation | Eligible users completing the activation event | Context before a repeated failed attempt | Product |
| Checkout friction | Attempts and successful orders | Error, interruption or navigation problem | Ecommerce and engineering |
| Confusing page content | Relevant page progression | Survey response and interaction pattern | Website owner |
| A release regression | Before-and-after outcome for comparable users | Reproducible failure in the changed flow | Engineering |
A recording supplies context, not a population rate. If several recordings show the same friction, quantify how often the affected event or page state occurs in the relevant population. If the evidence is sampled, preserve the sampling rule in the research note.
The opposite error is to stop at a funnel. A drop-off rate identifies a location in the journey but may not explain the reason. Use a bounded set of recordings or responses to form a hypothesis, then inspect whether the proposed change addresses it. Assign a person to make the decision and a metric to revisit afterward.
For a wider replay-oriented shortlist, read Fullstory alternatives. If the next step involves in-product education rather than only diagnosis, Amplitude vs Pendo compares the analytics-to-guide workflow.
Capture volumes and cost examples
The example below is hypothetical and concerns web recording only. It assumes 120,000 monthly website sessions and applies Contentsquare Free's published 5% capture rule within its maximum.
| Input or result | Calculation | Amount | Unit |
|---|---|---|---|
| Eligible site traffic | Assumed | 120,000 | Sessions/month |
| Illustrative replay sample | 120,000 × 5% | 6,000 | Recordings/month |
| Published replay ceiling | Plan limit | 10,000 | Recordings/month |
| Unrecorded sessions under the assumed sample | 120,000 minus 6,000 | 114,000 | Sessions/month |
The 6,000 figure is an expected sample size under the stated assumption, rather than a promise of exact captured volume. Capture eligibility, implementation and traffic patterns can affect the observed result. The plan inputs come from Contentsquare's replay and analytics table.
For a separate PostHog example, assume 1.5 million analytics events and 10,000 web recordings in one month. Assume standard first-tier USD rates, no startup credits, no platform package, no other products and no tax.
| Meter | Billable quantity after free allowance | Unit rate, USD | Monthly amount, USD |
|---|---|---|---|
| Analytics events | 500,000 | $0.00005/event | $25 |
| Web recordings | 5,000 | $0.005/recording | $25 |
| Combined example | Separate meters | Stated assumptions | $50 |
Rates and free allowances: PostHog analytics, PostHog web replay. Higher volumes have different tiers. The example deliberately stays within the first paid tier and is not a like-for-like quote for the Contentsquare sample.
The useful cost comparison holds the required evidence constant. Decide the analytics population, the sessions needing replay, retention and the people accessing the data. Then request or calculate each configuration. Use the software pricing tool to keep usage, implementation and ongoing analysis work in the same budget.
Capture quality and privacy controls
Test capture using an ordinary journey and a deliberately sensitive test value. Check displayed text, form fields, URLs, console output and any enabled network capture. A masked form field does not establish that the same value is absent from another part of the page or request.
PostHog documents browser-side or app-side masking and masks web inputs by default. It also provides more granular settings. Treat the actual SDK and configuration as the test subject, then inspect the resulting recording and payload before expanding capture. PostHog privacy controls.
For the Contentsquare route, validate the chosen capture settings on the actual pages being studied. Include login, account switching, confirmation screens and any embedded content relevant to the journey. Keep unnecessary identifiers out of tracked URLs and events. A replay tool's privacy feature needs a configuration and an acceptance test in the implemented site.
The tracking-plan audit skill can help organize the event and capture review. Keep an owner for changes to the event list or masking rules. A new interface component can introduce a new capture surface even when the analytics tag remains unchanged.
Legacy Hotjar transition
Existing Hotjar customers should compare their migration offer with a new PostHog implementation using the actual captured evidence. Contentsquare describes a move from daily Hotjar caps to sampling distributed through the month. Under a custom 20% sample, approximately one in five sessions is recorded, and a traffic surge can consume the quota before month end. Transition sampling.
A daily limit and a monthly sample can produce different research coverage during a campaign. Record the traffic pattern you need to study, including peak days, devices and key journeys. Confirm the quota behaviour and the process for requesting a sampling change rather than assuming old settings transfer unchanged.
Do not cancel the old working setup before validating the replacement. Run a bounded overlap where permitted by the implementation plan, compare a known journey and verify access to required historical evidence. Name the system responsible for each ongoing report so two trackers do not create an unresolved disagreement about the same metric.
Best fit by operating model
| Company size or operating model | Best fit | Runner-up | Decision reason |
|---|---|---|---|
| Marketing team researching website conversion | Contentsquare Experience Analytics | PostHog | Page research and feedback define the work |
| SaaS team with engineers maintaining event contracts | PostHog | Contentsquare scoped plan | Product events and debugging share an owner |
| Existing Hotjar account with a transition offer | An offer-specific comparison | PostHog | Sampling and second-year price need explicit review |
| Small site needing occasional replay | A qualified free configuration | The other free configuration | Capture coverage and data access matter more than headline volume |
| Product team planning targeted onboarding guides | A guide-focused shortlist | Replay-only investigation | The action after diagnosis changes product scope |
Evaluation workflow
The first branch follows the team's recurring job. Both candidates must pass event, replay and capture-control validation before the budget is accepted.
Read diagram as text
- Recurring research question to Product-event workflow priority.
- Product-event workflow priority to PostHog pilot: Yes.
- Product-event workflow priority to Contentsquare pilot: No.
- PostHog pilot to Capture and result validation.
- Contentsquare pilot to Capture and result validation.
- Capture and result validation to Evidence and privacy acceptance.
- Evidence and privacy acceptance to Tracking and masking repair: No.
- Tracking and masking repair to Capture and result validation.
- Evidence and privacy acceptance to Usage and retention budget: Yes.
- Usage and retention budget to Selected research workflow
A repaired event or masking rule returns to the same validation sample. Verify that the change protects the intended information while preserving enough context to answer the research question. The final decision includes the person responsible for reviewing evidence and making changes, not just the person installing the tag.
Analytics selection checklist
- Define the recurring website or product question and its decision owner.
- Separate sessions, events, recordings and survey responses in the budget.
- Confirm current Contentsquare terms or the applicable legacy Hotjar offer.
- Record the required replay sample, retention and access period.
- Validate successful, failed and interrupted journeys against known events.
- Inspect masking, URLs and enabled network or console capture.
- Recheck the complete sample after tracking or privacy repairs.
- Approve the ordinary post-discount bill and ongoing research responsibility.
Keep reading
Browse all Product Analytics guides
Product AnalyticsFullstory alternatives for replay, product analysis and adoption
Compare Fullstory alternatives by replay, product analysis and adoption work, with current free limits, data-use terms, billing units and migration checks.
Jafrin Akter AloLast updated 12 min read
Product AnalyticsAmplitude vs Pendo for product analysis and in-app adoption
Choose Amplitude or Pendo by product decision, guide operations and identity. Compare current event and MAU limits, audience eligibility and renewal scope.
Jafrin Akter AloLast updated 11 min read
Product AnalyticsBest Product Analytics Tools for Startups: 7 Options Compared by the Job They Do
Compare GA4, Mixpanel, Amplitude, PostHog, Heap, Pendo and Statsig on free tiers, experiments, server-side events, raw data export and warehouse options.
Jafrin Akter AloLast updated 27 min read
Product analytics
See the implementation scope, deliverables and acceptance checks.
Questions people ask
Can a new customer still open a standalone Hotjar account?
A new customer cannot open a standalone Hotjar account through the current offer. Hotjar's official product page directs new users to Contentsquare and says new Hotjar accounts are unavailable. Existing customers should review their own transition communication because migration pricing and sampling can differ from a new public subscription. Current Hotjar route.
Does Contentsquare Free include 200,000 replay recordings each month?
Contentsquare Free does not equate its 200,000-session analytics allowance with replay recordings. The current Experience Analytics table lists replay capture at 5% of sessions with a maximum of 10,000 monthly replays. It also lists one month of replay access. Keep the analytics and replay allowances separate when estimating research coverage. Contentsquare limits.
Are PostHog analytics events and replay recordings billed together?
PostHog analytics events and replay recordings use separate meters and allowances. Analytics has one million free monthly events, while web replay has five thousand free monthly recordings. Calculate each product's billable usage and applicable tier, then add any other selected products or platform charges. A single website visit can contribute to several meters. Analytics, replay.
Will a Hotjar migration discount preserve the same price after a year?
A Hotjar migration discount should not be assumed to preserve the same price after a year. Contentsquare describes the Loyalty Discount as lasting one year, while the custom sampling rate remains in place unless separately adjusted. Use the account's migration communication to budget the post-discount bill and confirm the evidence available at that sampling level. Transition terms.
Can replay observations establish a conversion uplift on their own?
Replay observations cannot establish a conversion uplift on their own. They can reveal a plausible source of friction and help define a change, but the outcome needs a measured comparison with a consistent population and metric. Record the hypothesis, implement the change and assess the relevant conversion result. Keep sampled observations separate from the rate calculated across eligible users.
Sources
- Hotjar's current Contentsquare signup route
- Contentsquare pricing and capture limits
- Hotjar and Contentsquare plan structure
- Hotjar migration sampling and pricing
- PostHog overall pricing
- PostHog product analytics pricing
- PostHog session replay pricing
- PostHog session replay
- PostHog startup program
- PostHog replay privacy controls

Written by
Jafrin Akter AloData Engineer and Co-founder at Martechdevs and Growth and Analytics Partners
Jafrin writes practical guides to marketing technology, customer data, analytics and AI workflows. Martechdevs is a Growth and Analytics Partners company.