@wrangled/cli 0.3.35 → 0.3.36

package/dist/guide.js

@@ -40,13 +40,13 @@ ${brand.name} does not build pages; it hands whoever builds one what is already
 
 ## Which Facebook ads and pages won: winners and flops
 
-\`${cli} winners\` says which Facebook ads won and which flopped, for one Monday-to-Sunday week and for the 30 days ending that Sunday, judged on real sales: each sale goes to the Facebook ad that first brought the buyer in, and payments typed into GoHighLevel by hand never count toward an ad. An ad with no sales that has spent less than twice the account's cost per sale is too new to judge on sales, so it is judged on cost per sign-up and listed apart. Each ad says in a sentence why it is on its list. It judges the landing pages the ads sent people to the same way, and each ad on each page as an ad-and-page pair: a page or pair counts only once the page reader has read the page and it got at least 100 visits in the dates, and pairs are listed only for an ad that sent people to two or more pages, or a page that got people from two or more ads, each naming what the same ad cost on its other pages. \`--week <YYYY-MM-DD>\` picks any day of the week (default: the latest complete week), \`--top <n>\` how many ads, pages or pairs each list shows (default 5, at most 20), and \`--format json\` gives the report as data.
+\`${cli} winners\` says which Facebook ads won and which flopped, for one Monday-to-Sunday week and for the 30 days ending that Sunday, judged on real sales: each sale goes to the Facebook ad that first brought the buyer in, and payments typed into GoHighLevel by hand never count toward an ad. An ad with no sales that has spent less than twice the account's cost per sale is too new to judge on sales, so it is judged on cost per sign-up and listed apart. Each ad says in a sentence why it is on its list. Each currency also says how many of its Facebook sales could be tied to a specific ad (\`adSales\` of \`facebookSales\` in the JSON): a sale whose link names no single ad counts toward Facebook but toward no ad. It judges the landing pages the ads sent people to the same way, and each ad on each page as an ad-and-page pair: a page or pair counts only once the page reader has read the page and it got at least 100 visits in the dates, and pairs are listed only for an ad that sent people to two or more pages, or a page that got people from two or more ads, each naming what the same ad cost on its other pages. \`--week <YYYY-MM-DD>\` picks any day of the week (default: the latest complete week), \`--top <n>\` how many ads, pages or pairs each list shows (default 5, at most 20), and \`--format json\` gives the report as data.
 
 ## What winners and flops taught: lessons
 
-Lessons are short plain sentences about why the winners won and the flops flopped, such as "Ads that open with a retiree's own money worry beat ads that open with a statistic: 4 of the top 5 this week, cost per sale $180 vs $410." A finished page or funnel test, or something learned about a funnel step, makes a lesson too. Each lists what proves it: ads, pages, funnel steps or tests. Read them before writing ads or pages: \`${cli} lessons\` lists the ones that hold, the most often seen first (\`--status retired\` lists the ones no longer true, with why; \`--about ads|pages|funnel\` only the ones with a proof of that kind; \`--dimension <d>\`, repeatable, only the ones along that dimension), and the brief carries them too. No person approves a lesson.
+Lessons are short plain sentences about why the winners won and the flops flopped, such as "Ads that open with a retiree's own money worry beat ads that open with a statistic: 4 of the top 5 this week, cost per sale $180 vs $410." A finished page or funnel test, something learned about a funnel step, or a follow-up email, text or sequence that helps sales makes a lesson too. Each lists what proves it: ads, pages, funnel steps, tests, emails, texts or sequences. A lesson that holds on an ad and an email is one lesson with both as proof. Read them before writing ads or pages: \`${cli} lessons\` lists the ones that hold, the most often seen first (\`--status retired\` lists the ones no longer true, with why; \`--about ads|pages|funnel|messages\` only the ones with a proof of that kind, \`--about cross_channel\` only the ones proven on two or more of ads, pages and messages; \`--dimension <d>\`, repeatable, only the ones along that dimension), and the brief carries them too. No person approves a lesson.
 
-Write one as JSON, \`{"text": "...", "dimension": "hook", "evidence": [{"ad": "<Meta ad id or SKU>", "numbers": "cost per sale $180 vs $410"}], "week": "2026-09-28"}\`, and run \`${cli} lessons add --file lesson.json\`. Each proof names exactly one of \`ad\`, \`page\` (a page's URL, kept as its page key, or a content item id), \`step\` (\`<funnel_key>.<step_key>\`) or \`test\` (a funnel test id or Adzara test_id), with its \`numbers\`. \`dimension\` (hook, angle, format, offer, persona, page, funnel_step or other) and \`week\` (any day of the winners report's week; default the latest complete week) are optional. A lesson with the same words that still holds, or the one named in \`"reinforces": "<id>"\`, is reinforced instead of copied: it counts once more for a week it had not counted, so running the same week again changes no count. \`${cli} lessons retire <id> --note "<why>"\` retires one the numbers no longer back; it is kept with why. The \`lessons\` playbook (\`${cli} skill install lessons\` installs it as the \`${LESSONS_SKILL_NAME}\` skill) writes the week's lessons from the winners report.
+Write one as JSON, \`{"text": "...", "dimension": "hook", "evidence": [{"ad": "<Meta ad id or SKU>", "numbers": "cost per sale $180 vs $410"}], "week": "2026-09-28"}\`, and run \`${cli} lessons add --file lesson.json\`. Each proof names exactly one of \`ad\`, \`page\` (a page's URL, kept as its page key, or a content item id), \`step\` (\`<funnel_key>.<step_key>\`), \`test\` (a funnel test id or Adzara test_id), \`message\` (an email or text's content item id, or its SKU, kept as its item id; one the content library does not have is refused) or \`sequence\` (\`ghl:<workflow id>\` or \`klaviyo:<flow id>\`), with its \`numbers\`. \`dimension\` (hook, angle, format, offer, persona, page, funnel_step, follow_up or other) and \`week\` (any day of the winners report's week; default the latest complete week) are optional. A lesson with the same words that still holds, or the one named in \`"reinforces": "<id>"\`, is reinforced instead of copied: it counts once more for a week it had not counted, so running the same week again changes no count. \`${cli} lessons retire <id> --note "<why>"\` retires one the numbers no longer back; it is kept with why. The \`lessons\` playbook (\`${cli} skill install lessons\` installs it as the \`${LESSONS_SKILL_NAME}\` skill) writes the week's lessons from the winners report.
 
 ## Sending winners to Exodus
 
@@ -348,7 +348,7 @@ ${cli} funnels evidence   prices paid, buyer paths, GoHighLevel funnels, calenda
 ${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
 ${cli} facts propose --file <fact.json>   suggest a fact for a person to confirm
-${cli} lessons [--status active|retired] [--about ads|pages|funnel] [--dimension <d>] | lessons add --file <lesson.json> | lessons retire <id> --note "<why>"   lessons from winners and flops, writing one, retiring one
+${cli} lessons [--status active|retired] [--about ads|pages|funnel|messages|cross_channel] [--dimension <d>] | lessons add --file <lesson.json> | lessons retire <id> --note "<why>"   lessons from winners and flops, writing one, retiring one
 ${cli} tests [--status <status>] [--funnel <key>] [--limit <n>] | tests show <id> | tests draft --file <test.json> | tests start <id> | tests abandon <id> [--note "<why>"]   funnel tests, one change each
 ${cli} ads tags [--ad <id>] [--status <status>] [--limit <n>] | ads tag --file <tags.json>   the marketing tags of ads not made here, and suggesting them
 ${cli} ads autotag [--limit <n>] [--ad <id>]   have the server propose tags for the biggest spenders not yet tagged

package/dist/main.js

@@ -1401,10 +1401,10 @@ const commands = {
         },
     },
     lessons: {
-        usage: "lessons [list] [--status active|retired] [--about ads|pages|funnel] [--dimension <d>]...   what earlier weeks' winners and flops and page and funnel tests taught, the most often seen first",
+        usage: "lessons [list] [--status active|retired] [--about ads|pages|funnel|messages|cross_channel] [--dimension <d>]...   what earlier weeks' winners and flops, page and funnel tests, and follow-up emails and texts taught, the most often seen first",
         async run(args, options) {
             if (!(args.length === 0 || (args.length === 1 && args[0] === "list"))) {
-                throw new CliError("Usage: lessons [list] [--status active|retired] [--about ads|pages|funnel] [--dimension <d>]...", exitCodes.usage);
+                throw new CliError("Usage: lessons [list] [--status active|retired] [--about ads|pages|funnel|messages|cross_channel] [--dimension <d>]...", exitCodes.usage);
             }
             const params = new URLSearchParams();
             if (options.status)
@@ -1425,7 +1425,7 @@ const commands = {
         },
     },
     "lessons add": {
-        usage: "lessons add --file <lesson.json> | < lesson.json   write down a lesson with the ads, pages, funnel steps or tests that prove it, or reinforce the one it repeats",
+        usage: "lessons add --file <lesson.json> | < lesson.json   write down a lesson with the ads, pages, funnel steps, tests, emails, texts or sequences that prove it, or reinforce the one it repeats",
         async run(args, options) {
             if (args.length > 0)
                 throw new CliError("Usage: lessons add --file <lesson.json> | < lesson.json", exitCodes.usage);
@@ -2053,9 +2053,10 @@ function winnersWindowText(title, window) {
                 : s.accountCostPerSale === null
                     ? "no sale credited to a Facebook ad in these dates"
                     : `the account paid ${money(s.accountCostPerSale, s.currency)} per sale`;
+            const tied = s.adSales === null || !s.facebookSales ? "" : ` ${s.adSales} of ${counted(s.facebookSales, "Facebook sale")} could be tied to a specific ad.`;
             const tests = s.tests.map((t) => `- Test ${t.testId}${t.hypothesisId ? ` (idea ${t.hypothesisId})` : ""}: ${counted(t.ads.length, "ad")}, spent ${money(t.spend, s.currency)}, ${counted(t.sales, "sale")}` +
                 `${t.costPerSale === null ? "" : `, ${money(t.costPerSale, s.currency)} per sale`}\n`);
-            return (`\nIn ${s.currency}: ${account}. ${s.adsJudgedOnSales} judged on sales, ${s.adsJudgedOnSignups} judged on sign-ups.\n` +
+            return (`\nIn ${s.currency}: ${account}.${tied} ${s.adsJudgedOnSales} judged on sales, ${s.adsJudgedOnSignups} judged on sign-ups.\n` +
                 s.notes.map((note) => `${note}\n`).join("") +
                 list("Winners", s.winners) +
                 list("Flops", s.flops) +
@@ -2349,8 +2350,9 @@ Options:
   --notes <text>        what changed in the version skill publish adds
   --note <why>          why: what content create and edit changed, why lessons retire says a lesson is no longer true,
                         or why tests abandon drops one
-  --about ads|pages|funnel   with lessons, only the lessons with a proof about ads, pages, or funnel steps and tests
-  --dimension <d>       with lessons, only the lessons along that dimension (hook, angle, format, offer, persona, page, funnel_step, other); repeat for several
+  --about <a>           with lessons, only the lessons with a proof about ads, pages, funnel (steps and tests) or messages
+                        (emails, texts and sequences), or cross_channel: proven on two or more of ads, pages and messages
+  --dimension <d>       with lessons, only the lessons along that dimension (hook, angle, format, offer, persona, page, funnel_step, follow_up, other); repeat for several
   --version <n>         the map version funnels show prints (default: the confirmed one)
   --based-on <n>        the map version funnels draft was written from; refused when someone saved since
                         (leave it out only for the first map, when there is neither a map nor a draft)

package/dist/playbooks.js

@@ -1437,6 +1437,16 @@ export const lessonsExample = {
     ],
     week: "2026-09-28",
 };
+/** A lesson proven on an ad and an email, exported so a test checks the server accepts it. */
+export const lessonsMessageExample = {
+    text: "The retiree money-worry angle that wins on Facebook also wins in the no-show email: the top ad and the top email this week.",
+    dimension: "angle",
+    evidence: [
+        { ad: "ABC-000123", numbers: "cost per sale $180 vs $410 for the account" },
+        { message: "ABC-000140", numbers: "2.1 sales per 1,000 sent vs 0.6" },
+    ],
+    week: "2026-09-28",
+};
 /** A lesson proven by a page and a test, exported so a test checks the server accepts it. */
 export const lessonsPageExample = {
     text: "A short video at the top of the webinar sign-up page beat the long letter: 38% sign-ups vs 29%.",
@@ -1454,7 +1464,7 @@ You work only through the \`${cli}\` CLI. Every command acts on the one workspac
 
 ## Rules that never bend
 
-- **Every lesson rests on ads and numbers.** Name at least one ad (its Meta ad id, or its SKU when it has one) and quote the numbers as the report gives them. A thread seen in one ad is a hunch, not a lesson: write it only when two or more ads show it, or one ad against the account's cost per sale by a wide margin.
+- **Every lesson rests on proof and numbers.** Name at least one ad (its Meta ad id, or its SKU when it has one), or the page, funnel step, test, email, text or sequence that shows it, and quote the numbers as the report gives them. A thread seen in one ad or one email is a hunch, not a lesson: write it only when two or more show it, or one against the account's cost per sale by a wide margin.
 - **Plain and short.** One or two sentences a business owner reads in five seconds, with the numbers in them: "Ads that open with a retiree's own money worry beat ads that open with a statistic: 4 of the top 5 this week, cost per sale $180 vs $410."
 - **Sales first.** Judge on what the report judges on sales. A lesson from ads judged on sign-ups says so in its words.
 - **Never add up money across currencies.** The report gives one section per currency; a lesson quotes one currency's numbers.
@@ -1494,6 +1504,12 @@ Ads are not the only proof. When the week's winners point at the page they send
 ${JSON.stringify(lessonsPageExample)}
 \`\`\`
 
+Follow-up emails, texts and sequences are proof too. Name an email or text as \`message\` (its content item id, or its SKU when it was made here; one the content library does not have is refused) and a whole sequence as \`sequence\` (\`ghl:<workflow id>\` for a GoHighLevel workflow, \`klaviyo:<flow id>\` for a Klaviyo flow), and use the \`follow_up\` dimension for a lesson about them alone. When the same thread wins on an ad and in an email, write it as one lesson with both as proof, not one lesson per channel:
+
+\`\`\`json
+${JSON.stringify(lessonsMessageExample)}
+\`\`\`
+
 Then:
 
 \`\`\`sh
@@ -1520,7 +1536,7 @@ Finish with a short report in plain words for the owner: the lessons you added,
 
 \`\`\`
 ${cli} winners [--week <YYYY-MM-DD>] --format json   the week's winners and flops, with each ad's tags
-${cli} lessons [--status active|retired] [--about ads|pages|funnel] --format json   the lessons that hold, or the retired ones
+${cli} lessons [--status active|retired] [--about ads|pages|funnel|messages|cross_channel] --format json   the lessons that hold, or the retired ones
 ${cli} ads tags --ad <ad id> --format json           one ad's marketing tags
 ${cli} lessons add --file <lesson.json>              write a lesson, or reinforce the one it repeats
 ${cli} lessons retire <id> --note "<why>"            retire a lesson the numbers no longer back

package/package.json

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