@koda-sl/baker-cli 0.116.0-dev.86609d2a7 → 0.117.0-dev.86609d2a7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -82,7 +82,7 @@ Use `--output` to change format:
82
82
 
83
83
  ### Ad Platforms (`baker ads`)
84
84
 
85
- Multi-platform ad commands. Google, Meta, and LinkedIn support both reads and **staged writes** (create/update campaigns, ad sets/ad groups, ads, creatives, audiences — applied on chat publish); X (Twitter) is read + analytics. TikTok is coming.
85
+ Multi-platform ad data commands. Currently supports Google Ads, with Meta, LinkedIn, and TikTok coming.
86
86
 
87
87
  ---
88
88
 
@@ -939,7 +939,7 @@ The HTTP backend exposes more endpoints (catalogs, ad-studies, ad-images, labels
939
939
 
940
940
  - `spend` is a decimal string in account currency, not an integer.
941
941
  - `effective_status` ≠ `status`. The dashboard shows effective_status (e.g. `WITH_ISSUES`, `PENDING_REVIEW`, `DISAPPROVED`, `ADSET_PAUSED`).
942
- - Meta creatives are effectively immutable once attached. Editing copy/image/CTA = stage a new creative + `ads update <id> --creative <ref>` (or `creatives duplicate`), not an edit of the live creative — see [Staged writes](#staged-writes-baker-ads-meta-campaignsadsetsadscreativesaudiencesmediadraft) above.
942
+ - Meta creatives are effectively immutable once attached. Editing copy/image/CTA = create a new creative + reattach (writes are out of scope for now).
943
943
  - Currency offsets are non-uniform (JPY/KRW = 1, KWD/BHD = 1000, most = 100). Read `account.currency` before doing budget math.
944
944
 
945
945
  ---
package/dist/cli.js CHANGED
@@ -10135,18 +10135,12 @@ var META_LIMITS = {
10135
10135
  /** Feed truncates the primary text past this with "… See more". */
10136
10136
  messageSoftMax: 125,
10137
10137
  messageHardMax: 5e3,
10138
- /** Below this, primary text reads as too thin to carry a hook + value + reason to act. */
10139
- messageGoodMin: 40,
10140
10138
  headlineMax: 255,
10141
10139
  descriptionMax: 300,
10142
10140
  carouselCardsMin: 2,
10143
10141
  carouselCardsMax: 10,
10144
- /** Carousels tell a fuller story and give Meta more to optimize at this many cards. */
10145
- carouselCardsGoodMin: 3,
10146
10142
  dynamicTextsMin: 1,
10147
- dynamicTextsMax: 5,
10148
- /** Dynamic ads mix and match best with at least this many media assets. */
10149
- dynamicAssetsGoodMin: 3
10143
+ dynamicTextsMax: 5
10150
10144
  },
10151
10145
  audience: {
10152
10146
  nameMax: 100,
@@ -11041,7 +11035,7 @@ var adSetsCreateCommand = defineCommand55({
11041
11035
  name: "create",
11042
11036
  description: `Stage a new ad set. ${STAGED_NOTE2}
11043
11037
  Chain to a campaign with --campaign (real id or meta_temp_* ref).
11044
- Example: baker ads meta adsets create --campaign meta_temp_ab12 --name "US 25-54" --optimization-goal LINK_CLICKS --billing-event IMPRESSIONS --daily-budget 50 --targeting-file t.json`
11038
+ Example: baker ads meta ad-sets create --campaign meta_temp_ab12 --name "US 25-54" --optimization-goal LINK_CLICKS --billing-event IMPRESSIONS --daily-budget 50 --targeting-file t.json`
11045
11039
  },
11046
11040
  args: { campaign: { type: "string", description: "Parent campaign id or meta_temp_* ref" }, ...adSetWriteArgs },
11047
11041
  run: async ({ args }) => {
@@ -11054,7 +11048,7 @@ var adSetsUpdateCommand = defineCommand55({
11054
11048
  meta: {
11055
11049
  name: "update",
11056
11050
  description: `Stage changes to an ad set. ${STAGED_NOTE2}
11057
- Example: baker ads meta adsets update 6123 --daily-budget 80`
11051
+ Example: baker ads meta ad-sets update 6123 --daily-budget 80`
11058
11052
  },
11059
11053
  args: { id: { type: "positional", description: "Ad set id or meta_temp_* ref", required: true }, ...adSetWriteArgs },
11060
11054
  run: async ({ args }) => {
@@ -11106,7 +11100,7 @@ var adCreativesCreateCommand = defineCommand55({
11106
11100
  description: `Stage a new ad creative. ${STAGED_NOTE2}
11107
11101
  Single-image/video via flags; carousel/dynamic via --file (creativeType carousel|dynamic).
11108
11102
  Reference media by --image-hash (already on Meta) or --image-ref meta_temp_* (a staged media upload).
11109
- Example: baker ads meta creatives create --page 555 --message "Save now" --link https://x.com --headline "Best cover" --image-hash abc123\u2026 --cta SHOP_NOW`
11103
+ Example: baker ads meta ad-creatives create --page 555 --message "Save now" --link https://x.com --headline "Best cover" --image-hash abc123\u2026 --cta SHOP_NOW`
11110
11104
  },
11111
11105
  args: {
11112
11106
  ...accountArgs2,
@@ -11139,7 +11133,7 @@ var adCreativesUpdateCommand = defineCommand55({
11139
11133
  name: "update",
11140
11134
  description: `Stage name/status changes to an ad creative. ${STAGED_NOTE2}
11141
11135
  Meta creatives are immutable \u2014 to change content, stage a new creative and repoint the ad.
11142
- Amending a staged (meta_temp_*) creative merges fields into the create. Example: baker ads meta creatives update 998 --name "Renamed"`
11136
+ Amending a staged (meta_temp_*) creative merges fields into the create. Example: baker ads meta ad-creatives update 998 --name "Renamed"`
11143
11137
  },
11144
11138
  args: {
11145
11139
  id: { type: "positional", description: "Creative id or meta_temp_* ref", required: true },
@@ -11224,7 +11218,7 @@ var audiencesCreateCommand2 = defineCommand55({
11224
11218
  name: "create",
11225
11219
  description: `Stage a new custom audience shell. ${STAGED_NOTE2}
11226
11220
  LOOKALIKE/WEBSITE/ENGAGEMENT specifics go via --file (lookalike_spec / rule). Member-list upload is not staged in v1.
11227
- Example: baker ads meta audiences create --name "Site visitors 30d" --subtype WEBSITE --file rule.json`
11221
+ Example: baker ads meta custom-audiences create --name "Site visitors 30d" --subtype WEBSITE --file rule.json`
11228
11222
  },
11229
11223
  args: {
11230
11224
  ...accountArgs2,