Everything Product events gives you
- 01
Four SDKs, unchanged
PostHog capture, batch, e, decide and flags; Segment track, identify, page, screen, group, alias and batch; Mixpanel track, import, engage; GA4.
- 02
Bodies as SDKs send them
JSON, gzip or form-encoded bodies are all read, so the app's real SDK is used as is.
- 03
Events per user
Every event with its user and properties; event_people lists the users events arrived for, with counts.
- 04
Tracking plans
A plan lists the events a flow must send and the properties each needs, as {event, props, min}.
- 05
Fail CI on gaps
check_events answers ok: false with the missing events and properties, so a test run can fail on it.
- 06
Personal data flagged
E-mail addresses, CPFs and card numbers found in properties are flagged on the event, before they reach a real tool.
- 07
Wait for an event
wait_for_event returns the event once the app sends it, optionally with a property value.
- 08
A collector that fails
The next answers are 400, 413, 429 with Retry-After, slow, or half the events silently lost.
The screens
Each number is a control or a reading on the real screen. Everything you can click there, your agent can do with a tool.
A plan, checked against what arrived

PostHog, Segment, Mixpanel and GA4, each with the calls it accepts and its count.
Point each SDK at its path on :8025; nothing else in the app changes.
workspace_created arrived without plan, which the plan requires.
trial_started never arrived: check_events answers ok: false.
- Per source
PostHog, Segment, Mixpanel and GA4, each with the calls it accepts and its count.
- SDK hosts
Point each SDK at its path on :8025; nothing else in the app changes.
- Missing property
workspace_created arrived without plan, which the plan requires.
- Missing event
trial_started never arrived: check_events answers ok: false.
Writing a plan

One plan per flow, such as signup and invite.
How much of the plan the app really sent in the window.
Properties after a colon; the same plan works from set_event_plan.
Saved in events/plans.yaml, so tests and CI read the same plan.
- Plans
One plan per flow, such as signup and invite.
- 4 of 7 arrived
How much of the plan the app really sent in the window.
- One event a line
Properties after a colon; the same plan works from set_event_plan.
- Save the plan
Saved in events/plans.yaml, so tests and CI read the same plan.
Break it on purpose
The failures you need to test, exactly when you ask: from the screen or by a tool call, each one shown on the timeline with who caused it.
Bad requestThe collector answers 400
force_events_failure 400Payload too largeThe collector answers 413
force_events_failure 413Rate limited429 with Retry-After
force_events_failure 429Slow collectorEach answer takes 3 s
force_events_failure slowHalf lostHalf the events dropped, 200 anyway
force_events_failure drop_half
Why not the real sandbox
Tracking is tested
Analytics breaks silently in production. A plan in CI fails the build when an event or property goes missing.
No real project polluted
Test runs do not pollute a real PostHog, Segment, Mixpanel or GA4 project, and cost nothing.
Personal data caught early
E-mails, CPFs and card numbers in properties are flagged before the app sends them to a real tool.
One place, four SDKs
Apps that use several analytics tools are checked in one list and one plan.
Your AI agent drives it
Claude Code, Codex or any MCP client connects to /mcp (or calls /api over plain HTTP), sets the stand-in up, breaks it on cue and reads what your app did.
Run the signup flow and tell me which tracking events are missing.
MCP tools
list_product_eventsEvents, newest first, with user, properties and personal dataevent_peopleThe users events arrived forwait_for_eventWait until the app sends an eventcheck_eventsCompare what arrived with a planlist_event_plansThe plans and their eventsset_event_planAdd or replace a plandelete_event_planRemove a planforce_events_failureMake the collector's next answers fail
The same over HTTP
- GET
/api/events - GET
/api/events/wait - POST
/api/events/check - PUT
/api/events/plans - POST
/api/events/force
- Plans live in events/plans.yaml.