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.
Path parameters
Numeric Google platform campaign id.
Query parameters
Disambiguates the campaign id when the connection spans platforms.
Also return delivery by day of week and by hour. Costs one extra Google call.
Trailing window for the performance split. Ignored when fromDate and toDate are both given.
Start of an explicit performance range (YYYY-MM-DD). Use together with toDate.
End of an explicit performance range (YYYY-MM-DD). Must be on or after fromDate.
Response
The campaign's ad schedule
Changes
Changed in 4 of the 56 revisions of this API.15
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
- ○
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
- ○
- ○
endpoint added
endpoint-added
- ○