@koda-sl/baker-cli 0.430.0 → 0.431.0

package/README.md

@@ -1462,7 +1462,7 @@ Shared flags: `--days <n>` (default 30) or `--start-date` / `--end-date` (`YYYY-
 
 **`tracking` answers "can this account be reported on at all", and it reads the ad account to do it.** `analytics ads` can only describe parameters that have already arrived, which leaves two blind spots that mislead in the expensive direction: a platform with no traffic in the window looks exactly like a platform whose ads carry nothing, and a dimension arriving under a name nobody has mapped looks exactly like one nothing carries. `baker analytics tracking` reads the mapping, the traffic **and** the client's own Google tracking templates / Meta URL parameters, so it can answer for a platform that has not had a click yet. Every dimension comes back in one of four states, and they are four different jobs: `covered` is done; `unmapped` means the URLs already carry it under a name Baker does not read, so run the `mapCommand` in the response — free, and it repairs the traffic already collected; `missing` means nothing carries it; `unknown` means no visit arrived *and* the account could not be read, which is not a finding and must never be reported as untagged.
 
-**`fix` says which level to put the missing pairs at, and who can write it.** Not a field name — the levels that platform accepts tagging at, widest first (the widest is the one to prefer: it covers campaigns nobody has created yet), which of them Baker can stage and which the user has to do by hand, and how each field treats a value already in it. That last part is the one people skip and it differs per platform: a Google **campaign** final URL suffix *replaces* the account one rather than merging, LinkedIn's `url-params` call *sets the ad set's whole parameter set* and Baker cannot read back what is in it, and a Meta creative is immutable so a live ad cannot be retagged through Baker at all. `suffix` is only ever the **missing** pairs, so the rule everywhere is the same: read what is there, work out what is missing, write the union. Where `fix` says Baker has no write surface — Microsoft, TikTok, Reddit, Pinterest, Snapchat — that is a request to hand the user with the exact string and the exact screen, never a reason to stop on the platforms it can write.
+**`fix` says which level to put the missing pairs at, and who can write it.** Not a field name — the levels that platform accepts tagging at, widest first (the widest is the one to prefer: it covers campaigns nobody has created yet), which of them Baker can stage and which the user has to do by hand, and how each field treats a value already in it. That last part is the one people skip and it differs per platform: a Google **campaign** final URL suffix *replaces* the account one rather than merging, LinkedIn's `url-params` call *sets the ad set's whole parameter set* and Baker cannot read back what is in it, and a Meta creative is immutable so a live ad cannot be retagged through Baker at all. `suffix` is only ever the **missing** pairs, so the rule everywhere is the same: read what is there, work out what is missing, write the union. Where `fix` says Baker has no write surface — Microsoft, TikTok, Reddit, Pinterest, Snapchat — that is a request to hand the user with the exact string and the exact screen, never a reason to stop on the platforms it can write. ChatGPT Ads is one Baker can write: its campaign and ad group `--tracking-template` (`baker ads chatgpt campaigns|ad-groups update`), which should carry `campaign_id={campaign_id}&ad_group_id={ad_group_id}&ad_id={ad_id}` — an id that only rides in `utm_campaign` or `utm_content` is reported as that UTM and never as the campaign or the ad, so `--platform chatgpt --role adgroup_id` has nothing to split by.
 
 **The one recommendation about the ad account itself.** `baker analytics ads --platform <p>` warns when that platform's traffic carries no campaign id, ad group id or ad id — the three tiers every "which ad worked" question is grouped by — and returns the exact URL suffix, in the platform's own macro language, that would start sending the missing ones. It is the only mapping gap that cannot be fixed afterwards: naming a parameter Baker already captures corrects the history, because roles are resolved when a report is read, but a parameter the ads never sent has no stored values for a meaning to apply to. The hint stays quiet for a platform with little traffic, and defers to the untagged-account finding rather than repeating it.
 

package/dist/cli.js

@@ -37858,7 +37858,7 @@ var SHARED_ARGS = {
   "max-bid": { type: "string", description: "Bid in account currency, e.g. 2.50 \u2014 fixed_bid only" },
   "tracking-template": {
     type: "string",
-    description: "Query string added to this ad group's landing pages, e.g. utm_content={ad_group_id} \u2014 none clears"
+    description: "Query string added to this ad group's landing pages, e.g. ad_group_id={ad_group_id} \u2014 none clears"
   },
   "audience-bids": {
     type: "string",
@@ -38048,7 +38048,7 @@ var SHARED_ARGS2 = {
   },
   "tracking-template": {
     type: "string",
-    description: "Query string added to this card's landing page, e.g. utm_content={ad_id} \u2014 none clears"
+    description: "Query string added to this card's landing page, e.g. ad_id={ad_id} \u2014 none clears"
   },
   status: { type: "string", description: "paused (default) | active" }
 };
@@ -38505,7 +38505,7 @@ var SHARED_ARGS3 = {
   },
   "tracking-template": {
     type: "string",
-    description: "Query string added to every landing page, e.g. utm_source=chatgpt&utm_campaign={campaign_id}&click_id={oppref} \u2014 none clears"
+    description: "Query string added to every landing page, e.g. utm_source=chatgpt&utm_campaign={campaign_id}&campaign_id={campaign_id}&ad_group_id={ad_group_id}&ad_id={ad_id} \u2014 keep the ids under those names, which Baker analytics splits by; the oppref click id is added by ChatGPT Ads itself. none clears"
   },
   platforms: {
     type: "string",
@@ -44049,7 +44049,8 @@ var AD_PLATFORMS2 = [
   "tiktok",
   "reddit",
   "pinterest",
-  "snapchat"
+  "snapchat",
+  "chatgpt"
 ];
 function isAdPlatform(value2) {
   return AD_PLATFORMS2.includes(value2);
@@ -44236,6 +44237,16 @@ var SNAPCHAT = {
     { role: "ad_name", macro: "{{creative.name}}", names: ["ad_name", "creative_name"] }
   ]
 };
+var CHATGPT = {
+  platform: "chatgpt",
+  label: "ChatGPT Ads",
+  docs: "https://help.openai.com/en/articles/20001212-create-ads-for-chatgpt",
+  dimensions: [
+    { role: "campaign_id", macro: "{campaign_id}", names: ["campaign_id", "campaignid"] },
+    { role: "adgroup_id", macro: "{ad_group_id}", names: ["ad_group_id", "adgroup_id"] },
+    { role: "ad_id", macro: "{ad_id}", names: ["ad_id", "adid"] }
+  ]
+};
 var AD_PLATFORM_DEFINITIONS = {
   google: GOOGLE,
   meta: META,
@@ -44244,7 +44255,8 @@ var AD_PLATFORM_DEFINITIONS = {
   tiktok: TIKTOK,
   reddit: REDDIT,
   pinterest: PINTEREST,
-  snapchat: SNAPCHAT
+  snapchat: SNAPCHAT,
+  chatgpt: CHATGPT
 };
 var ESSENTIAL_ROLES = ["campaign_id", "adgroup_id", "ad_id", "keyword", "match_type"];
 function essentialAdDimensions(platform) {
@@ -65222,7 +65234,7 @@ var SHARED_ARGS4 = {
   },
   platform: {
     type: "string",
-    description: "Read the whole report in one ad platform's vocabulary, and from its traffic only: google, meta, microsoft, linkedin, tiktok, reddit, pinterest, snapchat. Two effects at once \u2014 --role resolves against the spellings that platform uses (`cid` is TikTok's ad and nobody else's campaign) and the report narrows to the visits that arrived from it. Start here when comparing platforms, because without it every dimension is the union across all of them and one parameter can land under two roles",
+    description: "Read the whole report in one ad platform's vocabulary, and from its traffic only: google, meta, microsoft, linkedin, tiktok, reddit, pinterest, snapchat, chatgpt. Two effects at once \u2014 --role resolves against the spellings that platform uses (`cid` is TikTok's ad and nobody else's campaign) and the report narrows to the visits that arrived from it. Start here when comparing platforms, because without it every dimension is the union across all of them and one parameter can land under two roles",
     required: false
   },
   origin: {
@@ -65678,7 +65690,7 @@ var mapCommand = (() => {
   const args8 = {
     platform: {
       type: "string",
-      description: "Which platform these parameters belong to: google, meta, microsoft, linkedin, tiktok, reddit, pinterest, snapchat. REQUIRED with --set or --remove, because there is no such thing as a parameter that means one thing everywhere \u2014 `cid` is TikTok's ad and everyone else's campaign, and Meta cannot send a keyword at all. Leave it off only to read the whole mapping back",
+      description: "Which platform these parameters belong to: google, meta, microsoft, linkedin, tiktok, reddit, pinterest, snapchat, chatgpt. REQUIRED with --set or --remove, because there is no such thing as a parameter that means one thing everywhere \u2014 `cid` is TikTok's ad and everyone else's campaign, and Meta cannot send a keyword at all. Leave it off only to read the whole mapping back",
       required: false
     },
     set: {
@@ -65722,7 +65734,7 @@ var trackingCommand = (() => {
   const args8 = {
     platform: {
       type: "string",
-      description: "One platform: google, meta, microsoft, linkedin, tiktok, reddit, pinterest, snapchat. Omit to check the ones worth checking \u2014 every platform sending visits, plus Google and Meta, whose accounts Baker can read directly",
+      description: "One platform: google, meta, microsoft, linkedin, tiktok, reddit, pinterest, snapchat, chatgpt. Omit to check the ones worth checking \u2014 every platform sending visits, plus Google and Meta, whose accounts Baker can read directly",
       required: false
     },
     days: { type: "string", description: "Lookback window for the traffic half (default: 30)", required: false }