PostHog
Experimentation close to your product analytics
Research checked 2026-09-18 · Provisional research review
Scores reflect the evidence checked so far. Unverified capabilities may earn no points; this is not proof they are absent. Feature badges link to supporting sources.
The short verdict.
PostHog is worth shortlisting when its documented workflow matches the people who will run your experiments. PostHog fits a product team that wants experiments connected to behavioral data. Its code-based experiment path assumes someone can instrument events and implement variations. This is a provisional research review, not a hands-on benchmark or a recommendation. Use the component evidence below to challenge the score, then validate one representative experiment, the contract scope and the data path before committing.
What you’re evaluating
PostHog fits a product team that wants experiments connected to behavioral data. Its code-based experiment path assumes someone can instrument events and implement variations.
AI readiness,
piece by piece.
Official MCP access, public documentation and warehouse exports create a strong documented surface. The score gives assistive AI credit without treating beta self-driving features as GA. The remaining machine-readable checks are not verified. Product integration effort is reflected on the ease axis rather than being hidden inside the AI score.
Price the whole workflow.
Usable monthly free tier; experiments billed through feature flags. Usage-based paid expansion.
Check vendor pricing ↗| Pricing visibility | Public entry pricing |
|---|---|
| Price band | 1/5 |
| Trial / free plan | Free Plan |
| Before signing | Confirm traffic definition, export access and billing term. |
Who needs to be involved?
Connect
Install and define your conversion event.
Validate
Check assignment, consent and an A/A test.
Ship & learn
Launch a variation with a rollback owner.
4/10: SDK/code-based experiment path. Engineering must instrument events and implement variations. This score does not describe every optional product mode. Our evaluation approach: start with one low-risk variation and a known conversion event. Verify assignment persistence, exposure logging, consent behavior and the treatment of returning visitors. Run an A/A test before trusting a lift estimate. Check mobile rendering and the interaction with your existing analytics. Name the person responsible for rollback, and make sure that responsibility survives the trial. Ease is an editorial assessment of the documented path, not a measured time-to-launch promise.
Check the handoffs.
| Connection | What matters in your trial | Evidence |
|---|---|---|
| Analytics | Assignment IDs and consistent conversion events. | Verify your setup |
| CMS / application | Consent gating, template compatibility and QA. | Verify your setup |
| Warehouse | Raw data, latency and plan entitlement. | Export documented |
Evaluation criteria, not a claim of native support for every integration.
Specific evidence.
Specific scope.
Published certification evidence
The security handbook identifies SOC 2 Type II and describes GDPR obligations with DPA references. Tier 2 is the evidenced classification here. A HIPAA arrangement is not assumed from a comparison article.
A good fit is specific.
Shortlist it when…
- Product teams with developer ownership
- Teams wanting analytics and experiments in one workflow
- Teams that need raw event and warehouse portability
Look elsewhere when…
- Marketers needing every variation built without code
- Teams without a reliable event model
- Buyers equating a free allowance with zero operating cost
What users report.
Evidence before endorsements.
We haven’t verified a third-party review snapshot for this tool yet. No star rating or customer quote is displayed until a dated source has been checked.
A different path?
Statsig
Code-led experimentation with a usable free entry
Compare side by side ↗LaunchDarkly
Feature delivery with experimentation and agent controls
Compare side by side ↗Before you decide.
Does PostHog have an MCP server?
An official server is documented. Read the AI section for the scope, account requirements and limitations; docs retrieval alone is not experiment management.
Is this a final product ranking?
No. This research preview awards points only for evidence checked in this pass. Unverified components receive no points yet, so totals are provisional evidence floors, not proof that a capability is absent.
What should we validate in a trial?
Use a real variation, the conversion event you care about and your normal release process. Check assignment, consent, event quality, export behavior and rollback before making a purchasing decision.
Sources & verification.
| Evidence | Checked |
|---|---|
| Product scope | 2026-09-18 |
| Free tier and pricing model | 2026-09-18 |
| Experiment implementation | 2026-09-18 |
| Official MCP | 2026-09-18 |
| Machine-readable documentation | 2026-09-18 |
| Raw events and warehouse export | 2026-09-18 |
| Security and DPA links | 2026-09-18 |
| Public MCP source | 2026-09-18 |