Shipped and verified live. GET and PUT /v1/ads/campaigns/{campaignId}/ad-schedule.
A window is { dayOfWeek, startHour, startMinute, endHour, endMinute, bidModifier }. Minutes are the number rather than Google's enum, so you send 30, not THIRTY. endHour: 24 is midnight at the end of the day. bidModifier is 0.1 to 10.0, or null to run at the campaign bid.
PUT replaces the whole schedule, and schedule: [] clears it, which returns the campaign to serving around the clock. An empty schedule is not "no data": Google has no all-day criterion, so the response says servesAroundTheClock outright.
For the performance half of your request: GET ?includePerformance=true returns delivery split byDayOfWeek and byHour, from one query segmented on both dimensions so the two views always agree. Add fromDate/toDate, or windowDays for a trailing window.
Google's own rules are enforced before the write, so you get a named field instead of a criterion error: at most 6 windows per day, a window must end after it starts, no overlaps on a day, hour 24 carries no minutes, quarter-hour minutes only. All of those were confirmed against Google rather than assumed, including that adjacent windows like 09:00-12:00 and 12:00-17:00 are legal, so we do not reject them.
One thing worth knowing: Google cannot edit an ad schedule in place, so a PUT removes the live criteria and creates the new ones in a single atomic operation. The criterion ids in the response change on every write; that is Google's constraint, not ours.
Verified end to end on a real campaign: wrote two windows, read them back identically, then cleared it.
Log in to comment and vote
Comments1
Miquel Palet López
Sep 15
Shipped and verified live.
GETandPUT /v1/ads/campaigns/{campaignId}/ad-schedule.A window is
{ dayOfWeek, startHour, startMinute, endHour, endMinute, bidModifier }. Minutes are the number rather than Google's enum, so you send30, notTHIRTY.endHour: 24is midnight at the end of the day.bidModifieris 0.1 to 10.0, or null to run at the campaign bid.PUT replaces the whole schedule, and
schedule: []clears it, which returns the campaign to serving around the clock. An empty schedule is not "no data": Google has no all-day criterion, so the response saysservesAroundTheClockoutright.For the performance half of your request:
GET ?includePerformance=truereturns delivery splitbyDayOfWeekandbyHour, from one query segmented on both dimensions so the two views always agree. AddfromDate/toDate, orwindowDaysfor a trailing window.Google's own rules are enforced before the write, so you get a named field instead of a criterion error: at most 6 windows per day, a window must end after it starts, no overlaps on a day, hour 24 carries no minutes, quarter-hour minutes only. All of those were confirmed against Google rather than assumed, including that adjacent windows like 09:00-12:00 and 12:00-17:00 are legal, so we do not reject them.
One thing worth knowing: Google cannot edit an ad schedule in place, so a PUT removes the live criteria and creates the new ones in a single atomic operation. The criterion ids in the response change on every write; that is Google's constraint, not ours.
Verified end to end on a real campaign: wrote two windows, read them back identically, then cleared it.