@wrangled/cli 0.3.29 → 0.3.30

package/dist/guide.js

@@ -171,6 +171,8 @@ To change the map, write the whole map as JSON (\`{"offers": [...], "funnels": [
 
 \`${cli} funnels numbers\` counts each step of each funnel in the confirmed map over \`--from\` and \`--to\` (default the last 30 days; \`--funnel <key>\` for one funnel): how many reached it, and how many of those who reached the step before in those days moved on to it within the window, with the drop-off and the median days it took. A step whose rules name a person (webinar, GoHighLevel, payments) counts people and follows the same people from step to step; a step that cannot (ad clicks, page visitors) counts events, and its comparison is a rate of counts. A step whose data is not connected says unknown, never 0. Numbers are worked out after each sync by the rules of the map version confirmed at the time, so a renamed step keeps its numbers. For SQL, read \`saved_funnel_steps\`, \`funnel_step_daily\` and \`funnel_conversion\`.
 
+\`${cli} funnels leaks\` (\`--funnel <key>\` for one funnel, \`--to <date>\` for the last day) finds where each funnel loses people now: each step's rate from the step before over the last 28 days and the last 7, against its own normal rate over the 56 days before. A step doing worse says about how many fewer people moved on (the recent cohort times the rate it fell by) and what they were worth: an estimate, per currency and never added across them, from the offer prices of this step and the later purchase steps at the recent rates. The worst steps are listed first, by money, then people. A step with fewer than 100 people at the step before in either window says too few to tell and is never ranked; the 7-day rate needs 20. For a step counted by people, the recent cohort is also split by each person's first touch as of the day they reached the step before: channel, then the top 5 Meta campaigns and ads. People who reached the step before near the end of the window may not have moved on yet, so a slow step can look slightly worse. Start here before writing a conversion test idea.
+
 \`${cli} funnels evidence\` gathers what the workspace's own data says it sells, to draft a map from: the prices people paid in the last 365 days on each platform with buyer counts, the most common orders in which one person paid (\`1500 → 497 → 3500\`, with the median days between), GoHighLevel funnels and their steps, calendars with bookings and shows, pipeline stages, the most used tags, webinars with sign-ups, viewers and offer clicks, the landing pages ads link to, and active Facebook campaigns with 30-day spend. A part whose source is not connected says so. Ids, counts and amounts only. The \`map-offers\` playbook (\`${cli} skill install map-offers\` installs it as the \`${MAP_OFFERS_SKILL_NAME}\` skill, with a worked example map beside it; \`${cli} docs map-offers\` prints it) walks an agent from the evidence to a draft.
 
 \`${cli} funnels versions\` lists every version with its status (draft, confirmed, replaced or discarded), who wrote and confirmed it and its note; \`--diff <a> <b>\` says what changed from version a to version b.
@@ -311,6 +313,7 @@ ${cli} plans status <plan-id> draft|ready|publishing|live|done|cancelled
 ${cli} trail <plan-id | sku | item-id>   how a plan's items were made, where they ran, and their results
 ${cli} funnels show [--version <n>] | funnels versions [--diff <a> <b>]   the offers and funnels map, as text, and its versions
 ${cli} funnels numbers [--funnel <key>] [--from <date>] [--to <date>]   how many reached each funnel step and moved on
+${cli} funnels leaks [--funnel <key>] [--to <date>]   the steps doing worse than their normal, costliest first
 ${cli} funnels evidence   prices paid, buyer paths, GoHighLevel funnels, calendars and tags, webinars, pages and campaigns, to draft the map from
 ${cli} funnels draft --file <map.json> [--note <why>] [--evidence '<json>' | @file.json] [--based-on <n>] [--counts-from fix|<date>] [--questions @file.json]   save the whole map; it goes live when every step can be counted
 ${cli} facts [--kind <kind>] [--subject <type>[:<ref>]] [--status <status>] [--json] | facts show <id>   settled facts about the data, to treat as true

package/dist/main.js

@@ -1083,6 +1083,17 @@ const commands = {
             process.stdout.write(view.text);
         },
     },
+    "funnels leaks": {
+        usage: "funnels leaks [--funnel <key>] [--to <YYYY-MM-DD>]   the funnel steps doing worse than their normal, costliest first, with what that costs",
+        async run(args, options) {
+            if (args.length > 0 || options.from !== undefined)
+                throw new CliError("Usage: funnels leaks [--funnel <key>] [--to <date>]", exitCodes.usage);
+            const view = await api(await resolveConnection(options.apiUrl), `${FUNNELS_PATH}/leaks${reportQuery(options, { funnel: options.funnel })}`);
+            if (options.format === "json")
+                return printJson(view);
+            process.stdout.write(view.text);
+        },
+    },
     "funnels evidence": {
         usage: "funnels evidence   what the data says the client sells: prices paid, buyer paths, GoHighLevel funnels, calendars and tags, webinars, pages, campaigns, past campaigns",
         async run(args, options) {
@@ -2169,7 +2180,7 @@ Options:
   --counts-from fix|<YYYY-MM-DD>   how funnels draft counts: fix (default) for past dates too, or a change from that day
   --questions <json | @file.json>  the questions funnels draft asks a person, as an array
   --diff <a> <b>        with funnels versions, what changed from version a to version b
-  --funnel <key>        only this funnel's steps in funnels numbers (default: every funnel in the confirmed map);
+  --funnel <key>        only this funnel's steps in funnels numbers and funnels leaks (default: every funnel in the confirmed map);
                         with plans create and --step, the funnel the push is a step of
   --step <key>          with plans create, the step of --funnel this push itself is, as on the confirmed map
   --harness <list>      which agents skill publish marks the skill for: claude, codex, or claude,codex (default)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wrangled/cli",
-  "version": "0.3.29",
+  "version": "0.3.30",
   "description": "Command-line access to your marketing data warehouse, for people and coding agents",
   "type": "module",
   "bin": {