Skill 157 · Signals Scout Product Analytics
Subchapter 157.1
references/funnel-maturity.mdMarkdown5 KBView on GitHub
How to read conversion rates for mature entrant windows with query-funnel.
The maturity rule itself is in the body: an entrant window that ends at E is mature only when E + the conversion interval is at or before the cutoff.
This file covers the query that measures those windows without cutting off late conversions.
The funnel dateRange filters the events of every step, not only the entry step.
A steps query with a dateRange of one entrant week ignores every conversion after the week ends.
A person who enters on the last day of the week then gets less than one day to convert, whatever the saved interval is.
Do not score a funnel from a steps query bounded to the entrant window.
Trends mode groups entrants by entrant period, and counts each entrant’s conversions inside the conversion interval, also after the period ends.
series, funnelOrderType, funnelWindowInterval, funnelWindowIntervalUnit and filters into the query. Do not change the measured flow.funnelsFilter.funnelVizType: trends and interval: week (use day only for a daily cadence).dateRange that ends now. Start it at the beginning of an entrant period that is at least one conversion interval, the buffer and N+2 entrant periods before now. Then the latest mature point and N mature baseline points remain after you drop the immature points, and the first point is a full period.call --json query-funnel <json_input>. Put --json before the tool name; do not add output_format to the JSON input. The default optimized output shows only rates and no entrant counts.days, data (conversion %), reached_from_step_count (entrants) and reached_to_step_count, with matching indexes.interval: day, compare a point only to baseline points on the same weekday.reached_from_step_count for the volume gate, the steady-denominator check and the report evidence.Each trends point is the first-to-last rate, and query-funnel has no step selector.
Build each step rate from prefix funnels instead, with the same trends query:
data of the prefix funnel of steps 1..2.
Do not query a one-step prefix, because query-funnel rejects a funnel with fewer than two steps.reached_to_step_count of the longer prefix by that of the shorter prefix at the same index.
For this rate, the denominator is reached_to_step_count of the shorter prefix. Use it for the volume gate and the evidence. Skip a point where it is zero.funnelOrderType is ordered or strict. For an unordered funnel, score only the first-to-last rate.dateRange. Older baseline points have more later attempts, so their conversion can be too high. Do not author a decline for a funnel with exclusions from trends results.optionalInFunnel is valid only in a steps funnel, so the trends query fails. Do not remove the optional setting, because that changes the measured flow. Do not fall back to a steps query bounded to the entrant window.Name such a flow as unscored, with the reason, in the watchlist entry and the run summary.
A saved ordered funnel Signup → project created → first event, with a 14-day conversion interval and a weekly cadence. Now is Wed 24, and weeks start on Monday.
dateRange on a Monday at least 14 days, 6 hours and 6 weeks before now, and end it now.Signup → project created and the full funnel in trends mode with call --json query-funnel <json_input>.