late-sdk 0.0.950 → 0.0.952

data/openapi.yaml

@@ -10202,7 +10202,29 @@ components:
         matchType: { type: string, enum: [exact, phrase, broad, unknown] }
         status: { type: string, enum: [active, paused] }
         negative: { type: boolean }
-        qualityScore: { type: [integer, "null"], description: 'Google Quality Score, 1-10. Null when unrated.' }
+        qualityScore: { type: [integer, "null"], description: 'Deprecated, use `quality.score`. Google Quality Score, 1-10. Null when unrated.' }
+        quality:
+          type: object
+          description: |
+            Google Quality Score and the three component ratings behind it
+            (`ad_group_criterion.quality_info`). Every field is null until Google has rated the
+            keyword: a keyword with too little traffic is unrated, and negatives are never rated.
+            Google's own UNKNOWN / UNSPECIFIED buckets are reported as null so "unrated" has a
+            single representation.
+          properties:
+            score: { type: [integer, "null"], description: 'Quality Score, 1-10.' }
+            expectedCtr:
+              type: [string, "null"]
+              enum: [BELOW_AVERAGE, AVERAGE, ABOVE_AVERAGE, null]
+              description: 'How the click-through rate compares with other ads in the same position (`search_predicted_ctr`).'
+            adRelevance:
+              type: [string, "null"]
+              enum: [BELOW_AVERAGE, AVERAGE, ABOVE_AVERAGE, null]
+              description: 'How closely the ad matches the intent behind the search (`creative_quality_score`).'
+            landingPageExperience:
+              type: [string, "null"]
+              enum: [BELOW_AVERAGE, AVERAGE, ABOVE_AVERAGE, null]
+              description: 'How relevant and useful the landing page is to people who click (`post_click_quality_score`).'
         syncedAt: { type: [string, "null"], format: date-time }
         metrics:
           type: [object, "null"]
@@ -10215,6 +10237,18 @@ components:
             conversions: { type: number }
             firstPageCpc: { type: [number, "null"], description: Account currency }
             firstPositionCpc: { type: [number, "null"], description: Account currency }
+    AdScheduleWindow:
+      type: object
+      description: 'One ad schedule window as Google stores it. Half-open: it is exclusive of the end minute, so 09:00-12:00 and 12:00-17:00 are adjacent, not overlapping.'
+      properties:
+        criterionId: { type: string, description: 'Google campaign criterion id. Changes whenever the window is rewritten, because Google cannot edit a schedule in place.' }
+        resourceName: { type: string }
+        dayOfWeek: { type: string, enum: [MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, SUNDAY] }
+        startHour: { type: integer, minimum: 0, maximum: 23 }
+        startMinute: { type: integer, enum: [0, 15, 30, 45] }
+        endHour: { type: integer, minimum: 0, maximum: 24, description: '24 means midnight at the end of the day.' }
+        endMinute: { type: integer, enum: [0, 15, 30, 45] }
+        bidModifier: { type: [number, "null"], description: 'Bid adjustment for this window, 0.1-10.0. Null when the window runs at the campaign bid.' }
     KeywordEntry:
       description: 'A Google Search keyword: a bare string (BROAD match), or an object naming the match type.'
       oneOf:
@@ -44412,6 +44446,171 @@ paths:
         '404':
           description: No ads found for this campaign
 
+  /v1/ads/campaigns/{campaignId}/ad-schedule:
+    get:
+      x-resource-group: "ads"
+      operationId: getCampaignAdSchedule
+      tags: ["Ad Campaigns"]
+      x-platforms: ["google"]
+      summary: Read a campaign's ad schedule (dayparting)
+      description: |
+        The windows a Google campaign serves in, with the bid modifier on each, plus the
+        criterion ids Google minted for them.
+
+        An EMPTY `schedule` is meaningful and is not a failed lookup: Google has no
+        "all day" criterion, so a campaign with no ad schedule serves around the clock.
+        `servesAroundTheClock` states that explicitly.
+
+        Set `includePerformance=true` to also get delivery split by day of week and by hour,
+        which is the evidence for deciding what the schedule should be. It is one extra
+        Google call segmented by both dimensions at once, so the two views always agree.
+
+        Google Ads only. The response carries `cachedAt` and `stale`, set when a
+        quota-exhausted call falls back to the last-good copy instead of a live read.
+      security:
+        - bearerAuth: []
+      parameters:
+        - { name: campaignId, in: path, required: true, schema: { type: string }, description: "Numeric Google platform campaign id." }
+        - { name: platform, in: query, required: false, schema: { type: string, enum: [google] }, description: "Disambiguates the campaign id when the connection spans platforms." }
+        - { name: includePerformance, in: query, required: false, schema: { type: boolean }, description: "Also return delivery by day of week and by hour. Costs one extra Google call." }
+        - { name: windowDays, in: query, required: false, schema: { type: integer, minimum: 1, maximum: 90, default: 30 }, description: "Trailing window for the performance split. Ignored when fromDate and toDate are both given." }
+        - { name: fromDate, in: query, required: false, schema: { type: string, format: date }, description: "Start of an explicit performance range (YYYY-MM-DD). Use together with toDate." }
+        - { name: toDate, in: query, required: false, schema: { type: string, format: date }, description: "End of an explicit performance range (YYYY-MM-DD). Must be on or after fromDate." }
+      responses:
+        '200':
+          description: The campaign's ad schedule
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  campaignId: { type: string }
+                  schedule:
+                    type: array
+                    items: { $ref: '#/components/schemas/AdScheduleWindow' }
+                  servesAroundTheClock: { type: boolean, description: 'True when the campaign carries no ad schedule at all, so it can serve at any time.' }
+                  cachedAt: { type: [string, "null"], format: date-time }
+                  stale: { type: boolean, description: 'True when a quota-exhausted read served the last-good copy.' }
+                  performance:
+                    type: object
+                    description: 'Only present when includePerformance=true.'
+                    properties:
+                      windowDays: { type: [integer, "null"], description: 'The trailing window used, or null when an explicit fromDate/toDate range was given.' }
+                      byDayOfWeek:
+                        type: array
+                        description: 'One entry per day that delivered, Monday first.'
+                        items:
+                          type: object
+                          properties:
+                            dayOfWeek: { type: string, enum: [MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, SUNDAY] }
+                            impressions: { type: integer }
+                            clicks: { type: integer }
+                            cost: { type: number, description: 'Account currency, not USD-normalized.' }
+                            conversions: { type: number }
+                      byHour:
+                        type: array
+                        description: 'One entry per hour that delivered, 0-23 in the account time zone.'
+                        items:
+                          type: object
+                          properties:
+                            hour: { type: integer, minimum: 0, maximum: 23 }
+                            impressions: { type: integer }
+                            clicks: { type: integer }
+                            cost: { type: number, description: 'Account currency, not USD-normalized.' }
+                            conversions: { type: number }
+        '400': { $ref: '#/components/responses/BadRequest' }
+        '401': { $ref: '#/components/responses/Unauthorized' }
+        '403':
+          description: "Ads access required. Legacy plans need the Ads add-on; included by default on usage-based plans."
+        '404': { $ref: '#/components/responses/AccountUnavailable' }
+        '501':
+          description: "Not a Google Ads campaign: ad schedules are a Google criterion."
+    put:
+      x-resource-group: "ads"
+      operationId: updateCampaignAdSchedule
+      tags: ["Ad Campaigns"]
+      x-platforms: ["google"]
+      summary: Replace a campaign's ad schedule (dayparting)
+      description: |
+        Replaces the campaign's whole ad schedule with the windows you send. This is a
+        REPLACE, not a merge: windows you leave out stop serving.
+
+        Send `schedule: []` to clear dayparting, which returns the campaign to serving around
+        the clock.
+
+        Google rules enforced here, so you get a named field instead of a criterion error:
+        at most 6 windows per day, a window must end after it starts, windows on the same day
+        may not overlap, `endHour` 24 is midnight and cannot carry minutes, and minutes are
+        quarter-hours only (0, 15, 30, 45). `bidModifier` is 0.1-10.0; Google's 0 means
+        "off" for devices only, so a window is switched off by leaving it out.
+
+        Windows are half-open (Google is exclusive of the end minute), so 09:00-12:00 and
+        12:00-17:00 on the same day are adjacent and both valid.
+
+        Google cannot edit an ad schedule in place (every AdScheduleInfo field is prohibited on
+        update), so this removes the live criteria and creates the new ones in a single atomic
+        mutate. The response is read back from Google and carries the new criterion ids.
+      security:
+        - bearerAuth: []
+      parameters:
+        - { name: campaignId, in: path, required: true, schema: { type: string }, description: "Numeric Google platform campaign id." }
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              type: object
+              required: [schedule]
+              properties:
+                schedule:
+                  type: array
+                  maxItems: 42
+                  description: 'The complete set of windows. Required, so clearing the schedule is always deliberate rather than an omission.'
+                  items:
+                    type: object
+                    required: [dayOfWeek, startHour, endHour]
+                    properties:
+                      dayOfWeek: { type: string, enum: [MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, SUNDAY] }
+                      startHour: { type: integer, minimum: 0, maximum: 23 }
+                      startMinute: { type: integer, enum: [0, 15, 30, 45], default: 0, description: 'Quarter-hours only.' }
+                      endHour: { type: integer, minimum: 0, maximum: 24, description: '24 means midnight at the end of the day.' }
+                      endMinute: { type: integer, enum: [0, 15, 30, 45], default: 0, description: 'Quarter-hours only. Must be 0 when endHour is 24.' }
+                      bidModifier: { type: [number, "null"], minimum: 0.1, maximum: 10, default: null, description: 'Bid adjustment for this window. Null runs it at the campaign bid.' }
+            examples:
+              officeHours:
+                summary: Weekday office hours, bidding up over lunch
+                value:
+                  schedule:
+                    - { dayOfWeek: MONDAY, startHour: 9, endHour: 17 }
+                    - { dayOfWeek: TUESDAY, startHour: 9, endHour: 17 }
+                    - { dayOfWeek: WEDNESDAY, startHour: 9, endHour: 12, bidModifier: 1.5 }
+                    - { dayOfWeek: WEDNESDAY, startHour: 12, endHour: 17 }
+              clearSchedule:
+                summary: Serve around the clock again
+                value: { schedule: [] }
+      responses:
+        '200':
+          description: The schedule as Google stored it
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  campaignId: { type: string }
+                  schedule:
+                    type: array
+                    items: { $ref: '#/components/schemas/AdScheduleWindow' }
+                  servesAroundTheClock: { type: boolean }
+        '400': { $ref: '#/components/responses/BadRequest' }
+        '401': { $ref: '#/components/responses/Unauthorized' }
+        '403':
+          description: "Ads access required. Legacy plans need the Ads add-on; included by default on usage-based plans."
+        '404': { $ref: '#/components/responses/AccountUnavailable' }
+        '422':
+          description: "The schedule breaks a Google rule: too many windows on a day, an overlap, a window that ends before it starts, minutes on hour 24, or a bid modifier outside 0.1-10.0."
+        '501':
+          description: "Not a Google Ads campaign: ad schedules are a Google criterion."
+
   /v1/ads/campaigns/{campaignId}/bidding:
     get:
       x-resource-group: "ads"
@@ -45886,12 +46085,18 @@ paths:
         the campaign's live criteria and sends the removes and the creates in ONE
         `googleAds:mutate`, so the campaign is never left with a half-applied set; criteria
         already in the list keep their criterion ID and history. Excluded (negative)
-        locations are left untouched. Two cases are refused rather than applied: an empty
-        location list returns 400 (a Google campaign with no location criteria targets every
-        country, which is never what "remove my locations" means, so omit the field instead),
-        and radius targeting (`customLocations`) returns 422 because it is a separate Google
-        criterion type that this replacement neither creates nor removes. Send either
-        `targeting.locations` or the top-level geo fields, not both: mixing them returns 400.
+        locations are left untouched. An empty location list returns 400 (a Google campaign
+        with no location criteria targets every country, which is never what "remove my
+        locations" means, so omit the field instead). Send either `targeting.locations` or the
+        top-level geo fields, not both: mixing them returns 400.
+
+        **Google radius targeting:** `customLocations` is editable and is replaced the same
+        way, but as its OWN set. Google models a place (LOCATION) and a point plus radius
+        (PROXIMITY) as different criterion types, so the two are independent: sending
+        `customLocations` replaces every radius and leaves the cities and countries alone,
+        and sending places replaces those and leaves the radius alone. Send
+        `customLocations: []` to drop radius targeting entirely. A circle you re-send
+        unchanged keeps its criterion ID rather than being removed and recreated.
 
         **Google keyword replacement:** These edits affect the ad's entire ad group,
         including sibling ads. Positive (`targeting.keywords`) and negative
@@ -51450,6 +51655,24 @@ paths:
                     account running the ads (same-BC creators only). The creator generates the
                     code in their TikTok app's Promote settings and shares it with the
                     advertiser. Maps to `auth_code` on the creative entry of /v2/ad/create/.
+                promotedObject:
+                  type: object
+                  description: |
+                    TikTok-only on this endpoint. The pixel a Website Conversion ad group
+                    optimizes toward, so a Spark Ad built from an existing organic post can
+                    optimize for a conversion instead of only engagement or traffic. Required
+                    when `goal` is `conversions`; ignored on every other goal, because only a
+                    WEB_CONVERSIONS ad group accepts these fields.
+
+                    Combine freely with `platformPostId` + `sparkAuthCode`: the pixel lives on
+                    the ad group and the Spark item on the creative, so they never conflict.
+                  properties:
+                    pixelId:
+                      type: string
+                      description: 'TikTok Pixel. Either the numeric pixel id or the alphanumeric pixel code from Events Manager, which is resolved for you.'
+                    customEventType:
+                      type: string
+                      description: 'Optimization event, as a TikTok optimization_event code (e.g. ON_WEB_ORDER, SHOPPING, FORM) or the exact event name shown in Events Manager, which is resolved to its code. Omit to let TikTok optimize for the ad group default.'
                 dsaBeneficiary:
                   type: string
                   maxLength: 100

data/spec/api/ad_campaigns_api_spec.rb

@@ -309,6 +309,23 @@ describe 'AdCampaignsApi' do
     end
   end
 
+  # unit tests for get_campaign_ad_schedule
+  # Read a campaign's ad schedule (dayparting)
+  # The windows a Google campaign serves in, with the bid modifier on each, plus the criterion ids Google minted for them.  An EMPTY `schedule` is meaningful and is not a failed lookup: Google has no \"all day\" criterion, so a campaign with no ad schedule serves around the clock. `servesAroundTheClock` states that explicitly.  Set `includePerformance=true` to also get delivery split by day of week and by hour, which is the evidence for deciding what the schedule should be. It is one extra Google call segmented by both dimensions at once, so the two views always agree.  Google Ads only. The response carries `cachedAt` and `stale`, set when a quota-exhausted call falls back to the last-good copy instead of a live read. 
+  # @param campaign_id Numeric Google platform campaign id.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :platform Disambiguates the campaign id when the connection spans platforms.
+  # @option opts [Boolean] :include_performance Also return delivery by day of week and by hour. Costs one extra Google call.
+  # @option opts [Integer] :window_days Trailing window for the performance split. Ignored when fromDate and toDate are both given.
+  # @option opts [Date] :from_date Start of an explicit performance range (YYYY-MM-DD). Use together with toDate.
+  # @option opts [Date] :to_date End of an explicit performance range (YYYY-MM-DD). Must be on or after fromDate.
+  # @return [GetCampaignAdSchedule200Response]
+  describe 'get_campaign_ad_schedule test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   # unit tests for get_campaign_bidding
   # Read a campaign's current bidding
   # Read of the campaign's bidding strategy on Google, cached for the quota window, for pre-filling the bid strategy block before a PUT to /v1/ads/campaigns/{campaignId}. Google Ads only; `platform` is required and rejected when it is anything else, since a `campaignId` is not globally unique. The response carries `cachedAt` and `stale`, set when a quota-exhausted call falls back to the last-good copy instead of a live read.  Maps Google's bidding strategy onto the same triplet PUT accepts: `LOWEST_COST_WITHOUT_CAP` (Maximize Conversions, no target), `COST_CAP` + `bidAmount` (Target CPA), `LOWEST_COST_WITH_MIN_ROAS` + `roasAverageFloor` (Target ROAS), `LOWEST_COST_WITH_BID_CAP` + `bidAmount` (Maximize Clicks with a CPC ceiling). A campaign on a portfolio strategy returns `portfolio` (id + name) and `bidSpec.portfolioBidStrategyId` instead of the triplet. Anything else (Manual CPC, Target Impression Share, ...) returns `bidSpec: null`; show `biddingStrategyType` as-is. 
@@ -572,7 +589,7 @@ describe 'AdCampaignsApi' do
 
   # unit tests for update_ad
   # Update ad
-  # Patch one or more fields on an ad. Status, budget, targeting, and creative changes are propagated to the platform.  Per-platform support: - **Meta** (Facebook + Instagram): all fields supported. - **TikTok**: status, budget, targeting (via `/v2/adgroup/update/`), and creative   (via `/v2/ad/update/` patch-style: `headline` is ignored, `body` becomes `ad_text`). - **Google**: status, budget, KEYWORD edits via `targeting.keywords` /   `targeting.negativeKeywords`, DEVICE bid adjustments via `targeting.devices`,   LOCATION edits via `targeting.locations` (or the equivalent top-level   `targeting.countries` / `regions` / `cities` / `zips` / `metros`), and LANGUAGE   edits via `targeting.languages`.   Each list you send becomes the FULL new set of its kind (criteria not in the   list are removed, except devices, which Google cannot remove and which are   switched off with a bid modifier of 0 instead); a kind left out is untouched.   Any other `targeting` field   returns 400: Google cannot mutate it post-create without recreating   the campaign. Creative edits are dispatched on the ad's `advertisingChannelType`,   and every supported field replaces a whole set; a field you omit is preserved.   - **Search**: top-level `headlines`, `descriptions` and `finalUrls`. Use 3-15 headlines     (1-30 characters) and 2-4 descriptions (1-90 characters). Omit an asset to remove it;     omit pinnedField on an included asset to unpin it. Updates do not pad or truncate text.     The legacy creative fields remain unsupported.   - **Display**: top-level `headlines` (1-5, no pinnedField, display ads have no pinned     positions), `descriptions` (1-5) and `finalUrls`, plus `creative.longHeadline`,     `creative.businessName`, `creative.imageUrl` (the landscape marketing image) and     `creative.squareImageUrl`. Each image URL is uploaded as a new Google asset and the ad     is pointed at it; Google assets are immutable, so the previous asset stays in the     account's asset library.   - **Performance Max**: top-level `assetGroup`, which swaps asset roles on the ad's asset     group. The other creative fields return 422 for this channel, and `assetGroup` returns     422 on any other channel. - **LinkedIn**: status, budget, targeting (countries or regions, excludedLocations (countries),   the B2B facets, and audience segments; applied to the LinkedIn Campaign via   PARTIAL_UPDATE, and REPLACES the campaign's entire targetingCriteria, not a merge),   and creative (uploads new media, creates a replacement inline creative on the same   campaign, pauses the old one). - **Pinterest / X / OpenAI Ads**: status + budget only. Sending   `targeting` or `creative` returns 501 with code `unsupported_platform_operation`.   OpenAI Ads budget is lifetime-only (see `budget.type` below).  **Google location and language replacement:** locations, languages and devices are campaign-level criteria on Google, so these edits apply to every ad group and ad in the ad's campaign. Send the complete list you want to keep. Zernio diffs it against the campaign's live criteria and sends the removes and the creates in ONE `googleAds:mutate`, so the campaign is never left with a half-applied set; criteria already in the list keep their criterion ID and history. Excluded (negative) locations are left untouched. Two cases are refused rather than applied: an empty location list returns 400 (a Google campaign with no location criteria targets every country, which is never what \"remove my locations\" means, so omit the field instead), and radius targeting (`customLocations`) returns 422 because it is a separate Google criterion type that this replacement neither creates nor removes. Send either `targeting.locations` or the top-level geo fields, not both: mixing them returns 400.  **Google keyword replacement:** These edits affect the ad's entire ad group, including sibling ads. Positive (`targeting.keywords`) and negative (`targeting.negativeKeywords`) sets are independent: omit a field to leave that set unchanged, or send `[]` to remove every keyword of that kind.  Zernio compares each supplied set with Google's live criteria by case-insensitive keyword text and match type. A matching criterion is left untouched, retaining its criterion ID, enabled/paused status, keyword-level bid overrides, labels, and criterion-associated history/statistics. Zernio does not reset its quality score; Google continues to calculate scores and statistics normally. Text comparison does not trim whitespace.  A bare string or an object without `matchType` means `broad`, not the existing criterion's match type. For example, resending an existing `{ \"text\": \"plumber\", \"matchType\": \"exact\" }` preserves it; sending `\"plumber\"` instead removes that EXACT criterion and requests a BROAD one. Changing text or match type removes criteria no longer requested and creates any missing criteria. New criteria get new IDs and do not inherit removed criteria's bid overrides, labels, or history. Historical reporting for a removed criterion is not transferred to its replacement.  To add keywords without replacing a set, use [POST /v1/ads/keywords](https://docs.zernio.com/ad-campaigns/add-ad-keywords). Use `PATCH /v1/ads/keywords/{keywordId}` to pause/enable one keyword, or `DELETE /v1/ads/keywords/{keywordId}` to remove it. 
+  # Patch one or more fields on an ad. Status, budget, targeting, and creative changes are propagated to the platform.  Per-platform support: - **Meta** (Facebook + Instagram): all fields supported. - **TikTok**: status, budget, targeting (via `/v2/adgroup/update/`), and creative   (via `/v2/ad/update/` patch-style: `headline` is ignored, `body` becomes `ad_text`). - **Google**: status, budget, KEYWORD edits via `targeting.keywords` /   `targeting.negativeKeywords`, DEVICE bid adjustments via `targeting.devices`,   LOCATION edits via `targeting.locations` (or the equivalent top-level   `targeting.countries` / `regions` / `cities` / `zips` / `metros`), and LANGUAGE   edits via `targeting.languages`.   Each list you send becomes the FULL new set of its kind (criteria not in the   list are removed, except devices, which Google cannot remove and which are   switched off with a bid modifier of 0 instead); a kind left out is untouched.   Any other `targeting` field   returns 400: Google cannot mutate it post-create without recreating   the campaign. Creative edits are dispatched on the ad's `advertisingChannelType`,   and every supported field replaces a whole set; a field you omit is preserved.   - **Search**: top-level `headlines`, `descriptions` and `finalUrls`. Use 3-15 headlines     (1-30 characters) and 2-4 descriptions (1-90 characters). Omit an asset to remove it;     omit pinnedField on an included asset to unpin it. Updates do not pad or truncate text.     The legacy creative fields remain unsupported.   - **Display**: top-level `headlines` (1-5, no pinnedField, display ads have no pinned     positions), `descriptions` (1-5) and `finalUrls`, plus `creative.longHeadline`,     `creative.businessName`, `creative.imageUrl` (the landscape marketing image) and     `creative.squareImageUrl`. Each image URL is uploaded as a new Google asset and the ad     is pointed at it; Google assets are immutable, so the previous asset stays in the     account's asset library.   - **Performance Max**: top-level `assetGroup`, which swaps asset roles on the ad's asset     group. The other creative fields return 422 for this channel, and `assetGroup` returns     422 on any other channel. - **LinkedIn**: status, budget, targeting (countries or regions, excludedLocations (countries),   the B2B facets, and audience segments; applied to the LinkedIn Campaign via   PARTIAL_UPDATE, and REPLACES the campaign's entire targetingCriteria, not a merge),   and creative (uploads new media, creates a replacement inline creative on the same   campaign, pauses the old one). - **Pinterest / X / OpenAI Ads**: status + budget only. Sending   `targeting` or `creative` returns 501 with code `unsupported_platform_operation`.   OpenAI Ads budget is lifetime-only (see `budget.type` below).  **Google location and language replacement:** locations, languages and devices are campaign-level criteria on Google, so these edits apply to every ad group and ad in the ad's campaign. Send the complete list you want to keep. Zernio diffs it against the campaign's live criteria and sends the removes and the creates in ONE `googleAds:mutate`, so the campaign is never left with a half-applied set; criteria already in the list keep their criterion ID and history. Excluded (negative) locations are left untouched. An empty location list returns 400 (a Google campaign with no location criteria targets every country, which is never what \"remove my locations\" means, so omit the field instead). Send either `targeting.locations` or the top-level geo fields, not both: mixing them returns 400.  **Google radius targeting:** `customLocations` is editable and is replaced the same way, but as its OWN set. Google models a place (LOCATION) and a point plus radius (PROXIMITY) as different criterion types, so the two are independent: sending `customLocations` replaces every radius and leaves the cities and countries alone, and sending places replaces those and leaves the radius alone. Send `customLocations: []` to drop radius targeting entirely. A circle you re-send unchanged keeps its criterion ID rather than being removed and recreated.  **Google keyword replacement:** These edits affect the ad's entire ad group, including sibling ads. Positive (`targeting.keywords`) and negative (`targeting.negativeKeywords`) sets are independent: omit a field to leave that set unchanged, or send `[]` to remove every keyword of that kind.  Zernio compares each supplied set with Google's live criteria by case-insensitive keyword text and match type. A matching criterion is left untouched, retaining its criterion ID, enabled/paused status, keyword-level bid overrides, labels, and criterion-associated history/statistics. Zernio does not reset its quality score; Google continues to calculate scores and statistics normally. Text comparison does not trim whitespace.  A bare string or an object without `matchType` means `broad`, not the existing criterion's match type. For example, resending an existing `{ \"text\": \"plumber\", \"matchType\": \"exact\" }` preserves it; sending `\"plumber\"` instead removes that EXACT criterion and requests a BROAD one. Changing text or match type removes criteria no longer requested and creates any missing criteria. New criteria get new IDs and do not inherit removed criteria's bid overrides, labels, or history. Historical reporting for a removed criterion is not transferred to its replacement.  To add keywords without replacing a set, use [POST /v1/ads/keywords](https://docs.zernio.com/ad-campaigns/add-ad-keywords). Use `PATCH /v1/ads/keywords/{keywordId}` to pause/enable one keyword, or `DELETE /v1/ads/keywords/{keywordId}` to remove it. 
   # @param ad_id 
   # @param update_ad_request 
   # @param [Hash] opts the optional parameters
@@ -687,6 +704,19 @@ describe 'AdCampaignsApi' do
     end
   end
 
+  # unit tests for update_campaign_ad_schedule
+  # Replace a campaign's ad schedule (dayparting)
+  # Replaces the campaign's whole ad schedule with the windows you send. This is a REPLACE, not a merge: windows you leave out stop serving.  Send `schedule: []` to clear dayparting, which returns the campaign to serving around the clock.  Google rules enforced here, so you get a named field instead of a criterion error: at most 6 windows per day, a window must end after it starts, windows on the same day may not overlap, `endHour` 24 is midnight and cannot carry minutes, and minutes are quarter-hours only (0, 15, 30, 45). `bidModifier` is 0.1-10.0; Google's 0 means \"off\" for devices only, so a window is switched off by leaving it out.  Windows are half-open (Google is exclusive of the end minute), so 09:00-12:00 and 12:00-17:00 on the same day are adjacent and both valid.  Google cannot edit an ad schedule in place (every AdScheduleInfo field is prohibited on update), so this removes the live criteria and creates the new ones in a single atomic mutate. The response is read back from Google and carries the new criterion ids. 
+  # @param campaign_id Numeric Google platform campaign id.
+  # @param update_campaign_ad_schedule_request 
+  # @param [Hash] opts the optional parameters
+  # @return [UpdateCampaignAdSchedule200Response]
+  describe 'update_campaign_ad_schedule test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   # unit tests for update_campaign_assets
   # Update campaign assets
   # Edits existing Google assets in place. Send updates with assetResourceName and the fields to change. An asset is shared: changes affect every attachment using it. Omitted fields stay unchanged. The operation consumes the Google operations budget and invalidates affected cached lists.

data/spec/models/ad_keyword_quality_spec.rb

@@ -0,0 +1,66 @@
+=begin
+#Zernio API
+
+#API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema). 
+
+The version of the OpenAPI document: 1.0.4
+Contact: support@zernio.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.19.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Zernio::AdKeywordQuality
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Zernio::AdKeywordQuality do
+  #let(:instance) { Zernio::AdKeywordQuality.new }
+
+  describe 'test an instance of AdKeywordQuality' do
+    it 'should create an instance of AdKeywordQuality' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Zernio::AdKeywordQuality)
+    end
+  end
+
+  describe 'test attribute "score"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "expected_ctr"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["BELOW_AVERAGE", "AVERAGE", "ABOVE_AVERAGE"])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.expected_ctr = value }.not_to raise_error
+      # end
+    end
+  end
+
+  describe 'test attribute "ad_relevance"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["BELOW_AVERAGE", "AVERAGE", "ABOVE_AVERAGE"])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.ad_relevance = value }.not_to raise_error
+      # end
+    end
+  end
+
+  describe 'test attribute "landing_page_experience"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["BELOW_AVERAGE", "AVERAGE", "ABOVE_AVERAGE"])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.landing_page_experience = value }.not_to raise_error
+      # end
+    end
+  end
+
+end

data/spec/models/ad_keyword_spec.rb

@@ -135,6 +135,12 @@ describe Zernio::AdKeyword do
     end
   end
 
+  describe 'test attribute "quality"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "synced_at"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/

data/spec/models/ad_schedule_window_spec.rb

@@ -0,0 +1,90 @@
+=begin
+#Zernio API
+
+#API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema). 
+
+The version of the OpenAPI document: 1.0.4
+Contact: support@zernio.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.19.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Zernio::AdScheduleWindow
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Zernio::AdScheduleWindow do
+  #let(:instance) { Zernio::AdScheduleWindow.new }
+
+  describe 'test an instance of AdScheduleWindow' do
+    it 'should create an instance of AdScheduleWindow' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Zernio::AdScheduleWindow)
+    end
+  end
+
+  describe 'test attribute "criterion_id"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "resource_name"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "day_of_week"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["MONDAY", "TUESDAY", "WEDNESDAY", "THURSDAY", "FRIDAY", "SATURDAY", "SUNDAY"])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.day_of_week = value }.not_to raise_error
+      # end
+    end
+  end
+
+  describe 'test attribute "start_hour"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "start_minute"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('Integer', [0, 15, 30, 45])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.start_minute = value }.not_to raise_error
+      # end
+    end
+  end
+
+  describe 'test attribute "end_hour"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "end_minute"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('Integer', [0, 15, 30, 45])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.end_minute = value }.not_to raise_error
+      # end
+    end
+  end
+
+  describe 'test attribute "bid_modifier"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/models/boost_post_request_promoted_object_spec.rb

@@ -0,0 +1,42 @@
+=begin
+#Zernio API
+
+#API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema). 
+
+The version of the OpenAPI document: 1.0.4
+Contact: support@zernio.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.19.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Zernio::BoostPostRequestPromotedObject
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Zernio::BoostPostRequestPromotedObject do
+  #let(:instance) { Zernio::BoostPostRequestPromotedObject.new }
+
+  describe 'test an instance of BoostPostRequestPromotedObject' do
+    it 'should create an instance of BoostPostRequestPromotedObject' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Zernio::BoostPostRequestPromotedObject)
+    end
+  end
+
+  describe 'test attribute "pixel_id"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "custom_event_type"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/models/boost_post_request_spec.rb

@@ -211,6 +211,12 @@ describe Zernio::BoostPostRequest do
     end
   end
 
+  describe 'test attribute "promoted_object"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "dsa_beneficiary"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/

data/spec/models/get_campaign_ad_schedule200_response_performance_by_day_of_week_inner_spec.rb

@@ -0,0 +1,64 @@
+=begin
+#Zernio API
+
+#API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema). 
+
+The version of the OpenAPI document: 1.0.4
+Contact: support@zernio.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.19.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Zernio::GetCampaignAdSchedule200ResponsePerformanceByDayOfWeekInner
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Zernio::GetCampaignAdSchedule200ResponsePerformanceByDayOfWeekInner do
+  #let(:instance) { Zernio::GetCampaignAdSchedule200ResponsePerformanceByDayOfWeekInner.new }
+
+  describe 'test an instance of GetCampaignAdSchedule200ResponsePerformanceByDayOfWeekInner' do
+    it 'should create an instance of GetCampaignAdSchedule200ResponsePerformanceByDayOfWeekInner' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Zernio::GetCampaignAdSchedule200ResponsePerformanceByDayOfWeekInner)
+    end
+  end
+
+  describe 'test attribute "day_of_week"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["MONDAY", "TUESDAY", "WEDNESDAY", "THURSDAY", "FRIDAY", "SATURDAY", "SUNDAY"])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.day_of_week = value }.not_to raise_error
+      # end
+    end
+  end
+
+  describe 'test attribute "impressions"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "clicks"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "cost"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "conversions"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end