@koda-sl/baker-cli 0.383.0-dev.2caa8a15e → 0.384.0-dev.4699b7308

package/README.md

@@ -892,7 +892,7 @@ baker ads meta insights --object act_123 --level adset \
 baker ads meta activities --account-id act_123 --days 7
 
 # "Which Page should this ad run from?"
-baker ads meta pages                                                 # Facebook Pages the selected ad accounts can promote
+baker ads meta pages                                                 # Facebook Pages the user manages (tasks shows which can ADVERTISE)
 
 # "What is the lead form collecting, and how many came in?"
 baker ads meta lead-forms --page-id 100635183117758                  # instant forms on a Page + lead counts
@@ -3409,7 +3409,7 @@ baker scheduled-agents templates --delete weekly-posthog-check
 
 ### Marketing Tags (`baker tags`)
 
-Read the client's marketing/analytics tags (Meta pixel, GA4, Google Ads, GTM, Clarity, Hotjar, PostHog, …) — production tags overlaid with the changes staged in this chat.
+Read the client's marketing/analytics tags (Meta pixel, ChatGPT Ads pixel, GA4, Google Ads, GTM, Clarity, Hotjar, PostHog, …) — production tags overlaid with the changes staged in this chat.
 
 **The CLI is read-only.** Every tag change (create, edit, delete) goes through the `request_tag_input` tool (`baker_ui` MCP server): the agent proposes one or more changes — each becomes a tab in one blocking approval form — pre-filling the non-secret fields it knows; the user reviews, edits, fills secret fields, and approves or skips each tab. Approved changes stage on the chat and apply when the chat is published; discarding the chat drops them.
 
@@ -3425,6 +3425,7 @@ Notes:
 - **Both reads restate the write path, on stderr.** `list` and `draft` end with the two lines that say the approval form is the only way to change a tag, that it rides on every turn, and that a tag change is never a Task. They are there because a chat concluded from its tool list alone that the form did not exist, never called it, and filed the change as a Task for the user to carry out by hand. stdout stays the list, so piping it is unaffected; `--json` carries the same lines in the envelope's `hints`.
 - **`list` prints each tag's full readable config.** Every non-secret field is shown in full under the tag — the Clarity `projectId`, GA4 `measurementId`, the entire custom `code` snippet, etc. — so the agent reuses a stored value to pre-fill a follow-up change instead of asking the user for something already installed. Secrets are never among these fields. (`--json` emits the same data as the raw envelope.)
 - **Secrets never travel through this CLI or the chat.** Secret fields (`accessToken`, `apiSecret`, `authorizationToken`, `apiKey`, `conversionToken`, `oauthProviderId`) are entered only in the dashboard's secure tag form and flow straight into the staged draft; tool responses only ever name which secret fields are set/pending.
+- A `chatgptAds` tag takes a Pixel ID. Its optional `apiKey` is the Conversions API key and enables the server copy of page and Form events; the key stays out of the CLI and published page.
 - Staged creates get a server-generated `tag_temp_*` ref (returned in the tool result and printed by `list`). Use it (or a real tag id) as flow side-effect `tagIds` — the published tag keeps resolving under the temp ref.
 - Proposing a delete on a `tag_temp_*` ref drops the staged create instead.
 - Single-instance types (`code`, `posthog`, `datafast`) reject a second instance against the chat's effective view.
@@ -3434,6 +3435,8 @@ Notes:
 
 Read and shape this workspace's Forms (flows). Operates on the local `_data.json` files only; no secret values are ever decrypted or printed.
 
+For ChatGPT Ads conversions, add a `chatgptAds` side effect to the Form step, choose a supported event name, and use `baker flows map` to map `advancedMatching` and optional `eventParams` (`value` and `currency`).
+
 **A Form has two halves, split by a trust boundary.** Its *structure* — steps, conditions, side effects, field mappings — is yours, and the write subcommands below edit exactly that. Its *confidential* half — connection secrets, OAuth accounts, third-party field definitions (HubSpot, Calendly, HighLevel, SavvyCal) — is configured through the `request_flow_input` tool (`baker_ui` MCP server): the agent authors the surrounding structure and references it by `nodeId`/`sideEffectId`, and the user enters secrets, connects accounts, and picks resources in the dashboard. Those values are written (encrypted, where a secret) into the Form on the chat's branch and go live when the chat is published. Nothing any of these commands does touches a live system.
 
 ```bash

package/dist/cli.js

@@ -299,7 +299,6 @@ var chatActionDraftOpViewSchema = z.object({
   targetActionId: z.string().optional(),
   tempId: z.string().optional(),
   tags: z.array(z.string()).optional(),
-  priority: actionPrioritySchema.nullable().optional(),
   reason: z.string().optional(),
   note: z.string().optional(),
   name: z.string().optional(),
@@ -5124,6 +5123,16 @@ var FLOW_SIDE_EFFECT_CATALOG = [
     },
     "`advancedMatching` is how Meta re-identifies the visitor, and it is the difference between a matched conversion and a discarded one. Fill at least `em` and `ph` from the form: `baker flows map <slug> --map em=email --map ph=phone`."
   ),
+  eventSideEffect(
+    "chatgptAds",
+    "Fires a ChatGPT Ads pixel conversion and mirrors it through the Conversions API when a key is configured.",
+    {
+      eventType: "standard",
+      eventParams: [],
+      advancedMatching: matchingSlots("em", "ph", "fn", "ln", "external_id", "ct", "st", "zp", "country")
+    },
+    "Use ChatGPT Ads event names such as lead_created, order_created or appointment_scheduled. For a custom event use a lowercase name of 1\u201364 letters, digits, underscores or dashes. Only value (major currency units) and currency are supported in eventParams. Map em from the form to improve conversion matching."
+  ),
   eventSideEffect("googleAnalytics", "Fires a GA4 event.", { eventType: "custom", eventParams: [] }),
   {
     kind: "side-effect",
@@ -8036,6 +8045,7 @@ var studioImproveResponseSchema = z27.object({ prompt: z27.string(), original: z
 import { z as z28 } from "zod";
 var TAG_TYPES = [
   "meta",
+  "chatgptAds",
   "amplitude",
   "googleAds",
   "tiktok",
@@ -8057,6 +8067,7 @@ var TAG_TYPES = [
 var tagTypeSchema = z28.enum(TAG_TYPES);
 var TAG_IDENTIFYING_FIELD = {
   meta: "pixelId",
+  chatgptAds: "pixelId",
   googleAds: "conversionID",
   tiktok: "pixelCode",
   pinterest: "tagId",
@@ -15027,7 +15038,14 @@ function parseEventKey(key) {
 }
 
 // ../api/src/analytics/sends.ts
-var SEND_PLATFORMS = ["meta", "googleAds", "linkedinInsightTag", "twitterAds", "googleAnalytics"];
+var SEND_PLATFORMS = [
+  "meta",
+  "chatgptAds",
+  "googleAds",
+  "linkedinInsightTag",
+  "twitterAds",
+  "googleAnalytics"
+];
 function isSendPlatform(value) {
   return SEND_PLATFORMS.includes(value);
 }
@@ -15039,6 +15057,13 @@ var SEND_PLATFORM_SPECS = {
     credentialFields: ["accessToken"],
     setupHint: "Add the Conversions API access token to the Meta pixel in Tracking"
   },
+  chatgptAds: {
+    title: "ChatGPT Ads",
+    eventMeans: "A ChatGPT Ads event \u2014 lead_created, order_created, or a custom name",
+    eventKind: "name",
+    credentialFields: ["apiKey"],
+    setupHint: "Add the Conversions API key to the ChatGPT Ads pixel in Tracking"
+  },
   googleAds: {
     title: "Google Ads",
     eventMeans: "One of the account's conversion actions, picked from its list",
@@ -15089,6 +15114,7 @@ function isConversionSend(type) {
 }
 var SERVER_SIDE_SENDER_TAG = {
   metaCapi: "meta",
+  chatgptAdsCapi: "chatgptAds",
   googleAdsCapi: "googleAds",
   linkedinCapi: "linkedinInsightTag",
   twitterAdsCapi: "twitterAds",
@@ -28398,10 +28424,19 @@ var metaMediaCommand = defineCommand68({
 
 // src/commands/ads/meta/pages.ts
 import { defineCommand as defineCommand69 } from "citty";
+function advertisablePages(data) {
+  return data.filter((p) => Array.isArray(p.tasks) && p.tasks.includes("ADVERTISE"));
+}
 function pageSelectionHints(data) {
-  if (data.length > 1) {
+  const advertisable = advertisablePages(data);
+  if (advertisable.length > 1) {
+    return [
+      "MULTIPLE Pages can run ads \u2014 do NOT guess. Confirm with the user which Page an ad should run from before passing --page to `creatives create`; a wrong Page publishes the ad under the wrong brand identity and staging will not catch it."
+    ];
+  }
+  if (data.length > 0 && advertisable.length === 0) {
     return [
-      "MULTIPLE Pages can run ads from the selected Meta ad accounts \u2014 do NOT guess. Confirm with the user which Page an ad should run from before passing --page to `creatives create`; a wrong Page publishes the ad under the wrong brand identity and staging will not catch it."
+      "NO Page can run ads \u2014 none of the connected user's Pages carry the ADVERTISE task. Ask the user to grant Advertise access to the right Page before creating an ad; a readable-but-non-advertising Page still passes staging and would fail or run under the wrong identity."
     ];
   }
   return [];
@@ -28409,7 +28444,7 @@ function pageSelectionHints(data) {
 var pagesCommand = defineCommand69({
   meta: {
     name: "pages",
-    description: `List the Facebook Pages that the selected Meta ad accounts can promote. Every Meta ad publishes from a Page, so use this to identify the Page an ad should run from. If more than one Page is listed, confirm with the user which Page to use \u2014 a wrong Page publishes under the wrong brand identity.
+    description: `List the Facebook Pages the connected user manages. Every Meta ad publishes from a Page, so use this to identify the Page an ad should run from. The 'tasks' field shows what the user can do on each Page (ADVERTISE means it can back ads). If exactly one Page can ADVERTISE, use it; if more than one can, confirm with the user which Page to use; if none can, ask the user to grant Advertise access \u2014 a wrong or non-advertising Page publishes under the wrong brand identity.
 
 Examples:
   baker ads meta pages`
@@ -28670,7 +28705,7 @@ Discovery:
   baker ads meta accounts                                \u2014 accounts in this company's connected scope
   baker ads meta accounts --include-all                  \u2014 every account the token can see
   baker ads meta businesses                              \u2014 Business Manager IDs
-  baker ads meta pages                                   \u2014 Facebook Pages the selected ad accounts can promote (an ad's identity)
+  baker ads meta pages                                   \u2014 Facebook Pages the user manages (an ad's identity)
   baker ads meta lead-forms --page-id 100635183117758    \u2014 instant (lead) forms on a Page, with lead counts
   baker ads meta leads --form-id 987654321               \u2014 the leads one form collected (contact details masked)
 
@@ -49560,6 +49595,14 @@ var MAPPING_SLOTS = {
   code: [PAYLOAD("eventProperties")],
   datafast: [PAYLOAD("goalParams")],
   meta: [PAYLOAD("eventParams"), { kind: "record", key: "advancedMatching", allowed: META_MATCHING }],
+  chatgptAds: [
+    PAYLOAD("eventParams"),
+    {
+      kind: "record",
+      key: "advancedMatching",
+      allowed: ["em", "ph", "fn", "ln", "external_id", "ct", "st", "zp", "country"]
+    }
+  ],
   tiktok: [
     PAYLOAD("eventParams"),
     { kind: "record", key: "identify", allowed: ["email", "phone_number", "external_id"] }