Skip to content
Back to skills

Simulate New User

ASecurity

Send synthetic first-time-visitor traffic to a URL and confirm that PostHog $pageview events fire. Use when a customer wants to verify that anonymous visitor tracking works, after deploying instrumentation changes, or when debugging "events not arriving" reports.

  • 40,048 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added June 5, 2026
developmentgodebuggingapi

Works with

  • api
  • mcp

Security analysis

A100/100

Scanned June 5, 2026

npx -y skills add PostHog/posthog --skill simulate-new-user --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Simulate New User?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Simulate New User
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/posthog-simulate-new-user/badge)](https://www.skillsdirectory.com/skills/posthog-simulate-new-user)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: simulate-new-user
description: >
  Send synthetic first-time-visitor traffic to a URL and confirm that PostHog
  $pageview events fire. Use when a customer wants to verify that anonymous
  visitor tracking works, after deploying instrumentation changes, or when
  debugging "events not arriving" reports.
---

# Simulate new-user traffic

Drives a fresh browser context for each visit (no cookies, no localStorage),
goes to the given URL, scrolls a bit, and reports which PostHog events fired.
Each visit looks to PostHog like a brand-new anonymous visitor.

## When to use

- Confirm `$pageview` fires on the first visit (no cookies present).
- Confirm an anonymous `distinct_id` is generated and a PostHog request
  is sent within a few seconds of page load.
- Reproduce "events not showing up for new users" reports.

## How to invoke

Call the `simulate_new_user` MCP tool with:

- `url` (required) — the page to visit, e.g. `https://example.com/pricing`.
- `visits` (default `3`) — number of fresh-context visits.
- `interval` (default `5.0`) — seconds between visits.
- `posthog_host` (default `https://us.i.posthog.com`) — set to
  `https://eu.i.posthog.com` for the EU cloud, or your self-hosted host
  (e.g. `https://ph.example.com`).

Each visit takes ~10s of Playwright time plus the interval, so plan accordingly.

## Interpreting the result

The tool returns a structured summary:

```jsonc
{
  "run_id": "a1b2c3d4",
  "scenario": "new-user",
  "total_visits": 3,
  "posthog_requests": 6,
  "posthog_requests_ok": 6,
  "events_by_type": { "$pageview": 3, "$autocapture": 3 },
  "pageviews": 3,
  "errors": [],
  "verified": true,
}
```

- `verified: true` means at least one `$pageview` was captured per visit and
  no errors occurred — the new-user flow works.
- `verified: false` with `pageviews: 0` means PostHog isn't firing pageviews.
  Run `check_posthog_loading` next to see whether the snippet is even loaded.
- `posthog_requests_ok < posthog_requests` means PostHog returned non-2xx
  responses. Check the project's ingestion limits and api_host configuration.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.