@koda-sl/baker-cli 0.307.1 → 0.309.0

package/dist/cli.js

@@ -13654,7 +13654,7 @@ var SEND_PLATFORM_SPECS = {
   },
   googleAds: {
     title: "Google Ads",
-    eventMeans: "The id of one of the account's conversion actions \u2014 copy it from `conversionActions`, never type one",
+    eventMeans: "One of the account's conversion actions, picked from its list",
     eventKind: "id",
     credentialFields: ["oauthProviderId"],
     setupHint: "Connect the Google Ads conversion tag to a Google Ads account in Tracking"
@@ -13856,9 +13856,12 @@ var sendsResponseSchema = z28.object({
          * The conversions the platform already holds, by the id a send's `event`
          * takes and the name the person gave them. Google Ads only: its `event`
          * is an id Google issued, and an id the account does not hold is
-         * accepted and files against nothing.
+         * accepted and files against nothing. `label` is the conversion label
+         * the account's tag setup shows (`AW-…/<label>`) — how the person knows it.
          */
-        conversionActions: z28.array(z28.object({ id: z28.string(), name: z28.string(), primaryForGoal: z28.boolean() })).optional()
+        conversionActions: z28.array(
+          z28.object({ id: z28.string(), name: z28.string(), primaryForGoal: z28.boolean(), label: z28.string().optional() })
+        ).optional()
       })
     ),
     /** Every field a send forwards. Nothing to map. */
@@ -30348,7 +30351,7 @@ var args = {
   },
   event: {
     type: "string",
-    description: 'What the platform calls it \u2014 `platforms[].eventMeans` says what each one takes: a Meta or Google Analytics event name (Purchase, Lead, generate_lead), a Google Ads conversion action id copied from `platforms[].conversionActions` (never typed: an id the account does not hold is refused), a LinkedIn conversion rule id, an X event tag id. On Meta and Google Analytics it may be WRITTEN FROM THE EVENT with the same {{path}} mentions --parameter takes: --event {{properties.plan}} sends each event under the plan it carries, --event "Purchase {{properties.tier}}" mixes text and a field. An event carrying nothing there is not uploaded. Google Ads, LinkedIn and X take an id THEY issued, so a template is refused there \u2014 pass what varies as a --parameter instead. For a GOOGLE ADS id, list the account\'s conversion actions first and pick by name \u2014 `baker ads google query "SELECT conversion_action.id, conversion_action.name, conversion_action.primary_for_goal FROM conversion_action WHERE conversion_action.status = \'ENABLED\'"` \u2014 never guess: Google accepts an upload against an id the account does not hold and files it against nothing',
+    description: 'What the platform calls it \u2014 `platforms[].eventMeans` says what each one takes: a Meta or Google Analytics event name (Purchase, Lead, generate_lead), a Google Ads conversion action id copied from `platforms[].conversionActions`, or the conversion label the person gives you (staged as its id; never type an id: one the account does not hold is refused), a LinkedIn conversion rule id, an X event tag id. On Meta and Google Analytics it may be WRITTEN FROM THE EVENT with the same {{path}} mentions --parameter takes: --event {{properties.plan}} sends each event under the plan it carries, --event "Purchase {{properties.tier}}" mixes text and a field. An event carrying nothing there is not uploaded. Google Ads, LinkedIn and X take an id THEY issued, so a template is refused there \u2014 pass what varies as a --parameter instead. For a GOOGLE ADS id, list the account\'s conversion actions first and pick by name \u2014 `baker ads google query "SELECT conversion_action.id, conversion_action.name, conversion_action.primary_for_goal FROM conversion_action WHERE conversion_action.status = \'ENABLED\'"` \u2014 never guess: Google accepts an upload against an id the account does not hold and files it against nothing',
     required: false
   },
   account: {