Delivery Settings
Delivery settings shape how, when, and how often a campaign's ads are shown. Dayparting picks the days and hours when ads run, and frequency capping limits how many times the same person sees an ad in a given window. Device, inventory, and optimization controls are platform-managed today.
API operations
Relationships
Key concepts
Constraints
Rules to follow
- Dayparting and frequency capping are available for internet, native, TV, and audio campaigns. Billboard campaigns do not support either.
- Device, inventory, optimization, and CPM bidding are currently platform-managed. Direct API configuration will be available in a future version.
Platform-managed controls
Device targeting (PC, phone, tablet), inventory selection (web vs app), optimization type (quality impressions, traffic, clicks), and CPM bidding currently use platform defaults. Direct API configuration will be added in a future version.
URL patterns
Settings sub-resource endpoints follow the advertiser-scoped form /v1/advertisers/{advertiserId}/campaigns/{campaignId}/settings. Use this form for all GET and PUT calls against the settings sub-resource.
When building apps
Dayparting And Cap Starters
Dayparting works well starting with 8-12 hour windows and narrowing once performance data comes in. Restaurants typically weight lunch and dinner hours; B2B campaigns focus on weekday business hours; entertainment campaigns lean into evenings and weekends. Too-narrow dayparting reduces delivery volume and can cause under-spend. For frequency caps, brand awareness campaigns often run 3-5 daily impressions, retargeting campaigns use 1-2 per day to avoid fatigue, and direct response campaigns may use 5-7 per day. Omit
frequencyCap entirely to allow unlimited impressions.