Skip to main content
Beton
posthog_business_models_combined posthog_business_models_combined_mvp_v1

Combined coverage (all models)

A single dataset exercising the union of all supported event names across every business-model variant. Use this when you want one dataset that covers every signal type for Grafana-wide inspection or multi-agent testing.

Value metric

Union of event types across all business models

Success event

upgrade_clicked

entity_type: account

Scale

  • 360 accounts
  • 5 users/account (mean)
  • 10 sessions/user (mean)
  • 30 days of history

Research metrics proxied

  • — Coverage across all business models

Signal paths

Positive paths end in upgrade_clicked. Negative paths do not. Every generated event_id belonging to a path is recorded in ground_truth.json.

Positive signals (2)

limit_modal_upgrade ×50
limit_reached → upgrade_modal_shown → upgrade_clicked
cohorts: high_intent, medium_intent, power_user
gate_usage_upgrade ×30
feature_gate_shown → api_request → compute_hours_used → upgrade_clicked
cohorts: high_intent, power_user

Negative signals (2)

instrumentation_without_upgrade ×35
source_connected → $pageview → custom_event_tracked
cohorts: medium_intent, low_intent, lurker
credit_warning_without_upgrade ×30
credits_used → low_balance_warning
cohorts: low_intent, lurker, noisy_bot_like

Generate this dataset

Config file: configs/posthog_business_models_combined_mvp.yaml

Quickstart 
# Dockerized Postgres (recommended for inspection)
docker compose up -d

uv run dryfit \
  -c configs/posthog_business_models_combined_mvp.yaml \
  --dsn postgresql://dryfit_writer:dryfit_writer@127.0.0.1:54329/dryfit \
  --print-summary

# Or local Postgres
./scripts/generate-local -c configs/posthog_business_models_combined_mvp.yaml --print-summary

Full setup instructions are in the repo's README — including local Postgres, Grafana inspection, and dataset restore.

Noise parameters

DryFit injects realistic noise on top of the generated signal paths. These probabilities are per-event. Noise never touches rows referenced by ground_truth.json — your scoring logic can trust the truth file is exact.

missing event probability
5.0%
duplicate event probability
2.0%
out of order probability
3.0%
null property probability
3.0%
anonymous actor probability
1.0%
weird property probability
2.0%

Other scenarios

Contact / record-based SaaS

→ contact_created

Contacts, leads, subscribers, accounts managed

Credits / token-based

→ credits_purchased

Credits consumed, tokens used, compute units

Event-volume SaaS

→ custom_event_tracked

Events tracked, data points ingested, log lines

Feature-gated (tiered) SaaS

→ upgrade_clicked

Plan tier / feature access level
Browse all scenarios →

Benchmark your detector against Combined coverage (all models)

Clone the repo, run the config, check your agent's output against ground_truth.json.

View on GitHub