mirror of https://github.com/hanzoai/insights.git synced 2026-11-03 00:52:32 +00:00

Files

T

zeekay 1b367e2b62 chore: rebase the tree onto upstream master

The tree was a debranded snapshot of upstream taken around 2026-02-20, and
upstream has moved about five months since. This replaces it with upstream
master, mechanically re-derived: bin/debrand does the rename, and the
pipeline and squashed migrations are restored from the shipped tree.

Not a merge. The previous import replaced the tree wholesale in a single
commit, so there is no shared content history to merge against. Reproducing
the rename on the new tree is what actually converges.

What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints,
compose files, LLM.md, and insights/migrations. The squashed initial
migration is load-bearing — the live database records it by name, so
upstream's ~918 individual migrations cannot come back.

Nine products are dropped as unreferenced. Twenty-one more that we do not run
are kept anyway because the core app still imports them; unpicking those is a
refactor and does not belong in a rebase.

This base does not build yet, and the reasons are not in the rename:
upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against
our 4.2, and the dependency manifests still name upstream packages that we
republish under our own names. Those are decisions, not renames.

2026-08-01 15:44:40 -07:00

2.1 KiB

Raw Permalink Blame History

name, description

name	description
simulate-new-user	Send synthetic first-time-visitor traffic to a URL and confirm that Insights $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 Insights events fired. Each visit looks to Insights 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 Insights 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.
insights_host (default https://us.i.hanzo.ai) — set to https://eu.i.hanzo.ai 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:

{
  "run_id": "a1b2c3d4",
  "scenario": "new-user",
  "total_visits": 3,
  "insights_requests": 6,
  "insights_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 Insights isn't firing pageviews. Run check_insights_loading next to see whether the snippet is even loaded.
insights_requests_ok < insights_requests means Insights returned non-2xx responses. Check the project's ingestion limits and api_host configuration.

2.1 KiB Raw Permalink Blame History

Simulate new-user traffic

When to use

How to invoke

Interpreting the result

2.1 KiB

Raw Permalink Blame History