Build a quiz funnel and A/B test each question with PostHog

Marketing content & social · checked 2026-10-18

Build a quiz, validate its events, and test one question variant at a time with PostHog. An agent can help plan and read the experiment; you approve launch, copy changes and rollout, including a decision to keep an inconclusive result.

Independent review. IonBin has no partnership with any tool on this page and was not paid for this page. Our evaluation is our own, based on public documentation and our research. Product names are trademarks of their owners and are used for identification only. How disclosure works.

Goal

Improve form completion with measured changes instead of guesses.

Connects through: API · MCP

Steps

  1. Your AI platform

    Builds the quiz form as a small web page that sends one event per answered question

    AI platformConfirmed
  2. PostHog

    Captures the events and serves question variants through an experiment's feature flag

    APIConfirmedSource ↗
  3. Your AI platform

    Estimates sample size and creates an experiment for one question over the PostHog MCP server

    MCPConfirmedSource ↗
  4. Your AI platform

    Reads results and uncertainty, then proposes whether more data or a copy revision is warranted

    MCPConfirmedSource ↗
  5. You

    Approve the new copy and the decision to ship the winning variant

    Human stepConfirmed

Confirmed means the vendor documents it (linked). It doesn't mean IonBin has tested it. AI-platform and human steps need no source.

Human approval

You approve experiment launch, each copy change and every final rollout.

Watch out for

Small lists give noisy results. Don't let an agent rewrite and ship copy in a loop without someone reading it, and tell people how you'll use the email they enter.

Starter prompt

Build a five-question quiz with answer and completion events. Propose an experiment for question 2, including the primary metric, minimum meaningful effect, sample size, runtime and decision rule. Verify instrumentation, then stop for approval before launching. Report uncertainty and do not declare a winner from an inconclusive result.

Written for this workflow. Paste it into your AI platform and adjust it to your situation.

Tools in this workflow

ToolRoleOfficial site
PostHogAPI, MCP posthog.com ↗
ClaudeAI platform claude.ai ↗

Which AI platforms can run it

PlatformStatusWhy
Claude (incl. Claude Code) To verify PostHog: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; Your AI platform: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Your AI platform: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
OpenAI Codex To verify PostHog: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; Your AI platform: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Your AI platform: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Google Antigravity To verify PostHog: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; Your AI platform: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Your AI platform: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
ChatGPT To verify PostHog: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; Your AI platform: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Your AI platform: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Gemini To verify PostHog: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; Your AI platform: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Your AI platform: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it
Perplexity To verify PostHog: verify the API caller, network access and credentials; platform code execution alone does not establish this connection; Your AI platform: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it; Your AI platform: MCP pairing needs route-specific evidence; a named plugin or CLI does not establish it

Readiness considers the connection evidence and unresolved steps. Confirmed: documented access and the proposed steps meet the recorded requirements. MCP and API pairings require an explicit reviewed platform note; a named plugin or CLI alone does not confirm MCP. Inferred: an explicit page note describes a plausible pairing that still needs testing. To verify: a connection or step is unresolved. An API and code execution alone do not establish compatible network access, credentials or permissions. None of this is IonBin testing.

What we checked (2026-10-18)

  • Experiments over MCP. PostHog’s MCP server lets an AI agent estimate sample size and running time, create an experiment with its feature flag, launch it, read results and ship a winning variant.
  • Building the page. Host the quiz as your own web page, install the PostHog SDK, and verify variant assignment and events before running the experiment.
  • Interpreting results. Define the primary metric, minimum meaningful effect, sample-size target and decision rule before launch. Treat inconclusive results as inconclusive; an early numerical lead is not a proven winner. Rewriting and restarting tests repeatedly changes the question being measured.
  • Your list. If the quiz collects email addresses, say how you’ll use them, and send marketing only to people who agreed.

Set it up

  1. Ship the quiz with one event per answered question and a completion event.
  2. Test one question at a time, and ask the MCP server for a sample-size estimate first.
  3. Monitor event quality and guardrail metrics, then make the rollout decision using the planned analysis. Approve both experiment launch and any final rollout.

Credit: the idea comes from a sponsored Instagram reel (PostHog paid for it) by creator Angus Sewell. IonBin rewrote the steps and reviewed the documented PostHog features; this complete funnel has not been tested. IonBin has no relationship with PostHog, and the credit is not an endorsement.

Verification limits and implementation checks

The page is documentation-reviewed; the complete workflow has not been run by IonBin.

  • Run an instrumentation test and a complete experiment before claiming a conversion improvement.

Sources

Related workflows

No affiliate links on this page. No paid placements in workflows. How IonBin makes money.