zeekay
1b367e2b62
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.
2.7 KiB
List the persons behind one step of a funnel insight — either those who converted through it or those who dropped off at it.
Pair this with query-funnel: first run the funnel query to read the per-step counts, then call this tool with the same funnel query as source. There are two mutually exclusive modes, and the selectors you use must match the source funnel's funnelsFilter.funnelVizType.
Step mode (the default — source funnelVizType: "steps")
Use funnelStep to pick a step. The sign picks the direction:
- Positive
funnelSteplists actors who converted through that step. - Negative
funnelSteplists actors who dropped off at that step.
Steps are 1-based. Examples for a 3-step funnel:
funnelStep: 1— entered the funnel (reached step 1).funnelStep: 2— converted through step 2.funnelStep: -2— dropped off at step 2 (reached step 1 but not step 2).funnelStep: 3— converted through the whole funnel.funnelStep: -3— dropped off at step 3.
You cannot drop off at the entry step, so the smallest negative value is -2. To list every person at each step, call this tool once per (step, direction) you care about — a single call returns one cohort, not all steps.
funnelStepBreakdown(optional): scope to one breakdown series. Pass the breakdown value(s) from the matchingquery-funnelresult row verbatim (an array, e.g.["Chrome"]). Omit for the baseline (non-breakdown) series.
Trends-dropoff mode (source funnelVizType: "trends")
For a funnel-trends (conversion-over-time) insight, drill into one point on the chart:
funnelTrendsDropOff:truelists actors who dropped off,falselists those who converted.funnelTrendsEntrancePeriodStart: the entrance period as aYYYY-MM-DD HH:mm:ssstring (e.g.'2024-01-15 00:00:00'), taken from the point the user is asking about.
Use these two together. Do not mix them with funnelStep.
The funnel
time_to_convertviz type has no persons drilldown — this tool does not support it.
Response
Each returned row contains distinct_id, email, and name, plus a recordings column when includeRecordings is set (default true). Results are limited to the top 100 actors.
Guidance
- Keep the
sourcefunnel query identical to the one whose step the user is asking about — the series order, date range, conversion window, and filters all determine who converts at each step. - Make sure the mode matches the source's
funnelVizType:funnelStepneeds"steps"(the default),funnelTrendsDropOffneeds"trends". Mixing them returns wrong or empty results. - For large cohorts, tighten the source (date range, filters) rather than expecting more than 100 rows.