@koda-sl/baker-cli 0.396.0 → 0.397.0

package/README.md

@@ -3465,7 +3465,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.
 
@@ -3481,6 +3481,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.
@@ -3490,6 +3491,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

@@ -27117,6 +27117,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",
@@ -30032,6 +30042,7 @@ var studioImproveResponseSchema = z32.object({ prompt: z32.string(), original: z
 import { z as z33 } from "zod";
 var TAG_TYPES = [
   "meta",
+  "chatgptAds",
   "amplitude",
   "googleAds",
   "tiktok",
@@ -30053,6 +30064,7 @@ var TAG_TYPES = [
 var tagTypeSchema = z33.enum(TAG_TYPES);
 var TAG_IDENTIFYING_FIELD = {
   meta: "pixelId",
+  chatgptAds: "pixelId",
   googleAds: "conversionID",
   tiktok: "pixelCode",
   pinterest: "tagId",
@@ -41395,7 +41407,8 @@ var INGEST_CLICK_ID_PARAMS = [
   "msclkid",
   "rdt_cid",
   "epik",
-  "sccid"
+  "sccid",
+  "oppref"
 ];
 
 // ../api/src/event-sources/fields.ts
@@ -41421,7 +41434,8 @@ var CLICK_LABELS = {
   msclkid: "Microsoft click id",
   rdt_cid: "Reddit click id",
   epik: "Pinterest click id",
-  sccid: "Snapchat click id"
+  sccid: "Snapchat click id",
+  oppref: "ChatGPT Ads click id"
 };
 var SOURCE_FIELDS = [
   { field: "event_name", label: "What happened", group: "event" },
@@ -41518,7 +41532,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(value2) {
   return SEND_PLATFORMS.includes(value2);
 }
@@ -41530,6 +41551,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",
@@ -41580,6 +41608,7 @@ function isConversionSend(type) {
 }
 var SERVER_SIDE_SENDER_TAG = {
   metaCapi: "meta",
+  chatgptAdsCapi: "chatgptAds",
   googleAdsCapi: "googleAds",
   linkedinCapi: "linkedinInsightTag",
   twitterAdsCapi: "twitterAds",
@@ -41784,7 +41813,8 @@ var analyticsBeaconClickIdsSchema = z40.object({
   msclkid: z40.string().max(255).optional(),
   rdtCid: z40.string().max(255).optional(),
   epik: z40.string().max(255).optional(),
-  sccid: z40.string().max(255).optional()
+  sccid: z40.string().max(255).optional(),
+  oppref: z40.string().max(255).optional()
 });
 var analyticsBeaconIdentitySchema = z40.object({
   /** Lowercase hex SHA-256. Anything else is dropped rather than stored. */
@@ -42062,6 +42092,7 @@ var IDENTITY_KEY_KINDS = [
   "rdt_cid",
   "epik",
   "sccid",
+  "oppref",
   "fbp",
   "fbc"
 ];
@@ -42087,6 +42118,7 @@ var MATCH_KEY_LABELS = {
   rdt_cid: "Reddit click",
   epik: "Pinterest click",
   sccid: "Snapchat click",
+  oppref: "ChatGPT Ads click",
   fbp: "Meta browser cookie",
   fbc: "Meta click cookie"
 };
@@ -42122,6 +42154,7 @@ var VERBATIM_KINDS = [
   "rdt_cid",
   "epik",
   "sccid",
+  "oppref",
   "fbp",
   "fbc"
 ];
@@ -42264,7 +42297,8 @@ var CLICK_LABELS2 = {
   msclkid: "Microsoft click id",
   rdt_cid: "Reddit click id",
   epik: "Pinterest click id",
-  sccid: "Snapchat click id"
+  sccid: "Snapchat click id",
+  oppref: "ChatGPT Ads click id"
 };
 var PERSON_FIELDS = MATCH_FIELD_FORWARDING.map((row) => ({
   name: row.field,
@@ -44077,7 +44111,7 @@ var analyticsVisitorRowSchema = z44.object({
   /**
    * The click ids this person arrived on, by their own names — `gclid`,
    * `fbclid`, `msclkid`, `li_fat_id`, `ttclid`, `twclid`, `wbraid`, `gbraid`,
-   * `dclid`, `rdt_cid`, `epik`, `sccid`.
+   * `dclid`, `rdt_cid`, `epik`, `sccid`, `oppref`.
    *
    * Only the ones that were present. The endpoint has always returned all eight
    * columns and nothing above it carried them, so the one screen whose subject
@@ -58183,7 +58217,7 @@ var EVENT_FIELDS = [
     name: "the ad click ids",
     need: "optional",
     under: true,
-    takes: "The click id that brought them, if you kept it, under the name the platform stamps on the link: gclid, wbraid, gbraid, dclid, fbclid, ttclid, twclid, li_fat_id, msclkid, rdt_cid, epik, sccid (Snapchat's ScCid, in any case).",
+    takes: "The click id that brought them, if you kept it, under the name the platform stamps on the link: gclid, wbraid, gbraid, dclid, fbclid, ttclid, twclid, li_fat_id, msclkid, rdt_cid, epik, sccid (Snapchat's ScCid, in any case), oppref (ChatGPT Ads).",
     note: "A click id names a person too \u2014 it is enough on its own, and it attributes the event to the campaign that earned it."
   },
   {
@@ -78807,6 +78841,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"] }