Check why a banner does not serve on a placement
Lists everything that stops the banner from serving on the placement: any of the six levels (banner, campaign, advertiser, placement, zone, site) deleted or switched off - and, when the ad server switched it off itself because a total impressions, clicks or conversions limit was reached or (banner,
https://YOUR-NETWORK-DOMAIN/rest-api/serving-check.do Lists everything that stops the banner from serving on the placement: any of the six levels (banner, campaign, advertiser, placement, zone, site) deleted or switched off - and, when the ad server switched it off itself because a total impressions, clicks or conversions limit was reached or (banner, campaign) its end date passed, which one, since raising the limit or moving the date does not switch it back on; a delivery limit that is full (daily, weekly, monthly, total budget) on any level but the zone; moderation that switched the banner off (pending or rejected); the link between them, or links switched off on either side; their kind and size (which of kind, size, app operating system or category, or native asset sizes differs); a device targeting no visitor can pass on all six levels together (device format rules, and an operating system include list read as the devices it runs on), with a warning when it leaves a mobile site placement only desktop or TV visitors; an uploaded video that misses the site's video creative requirements, with each failed requirement (named only with the SITE_VIDEO_CREATIVE_REQUIREMENTS permission, enabled or read-only); the banner's and the campaign's run dates; a location rule naming a place the geo database no longer knows (an exclude, or includes that are all such places, keep every visitor out); and, with country, a country targeting rule that keeps that visitor out. blockers is empty when nothing in that list is in the way. warnings names what matters but does not stop serving: a pending approval on a banner still switched on, a site the network has not approved, location includes the geo database no longer knows next to ones it does. targeting lists, per level (site, zone, placement, advertiser, campaign, banner) with targeting switched on, how its rule types combine and each rule as "TYPE RULE value"; the site, zone and placement rules are listed only with the MANAGE_SUPPLY_PRE_TARGETING permission and the advertiser, campaign and banner rules only with MANAGE_DEMAND_TARGETING (enabled or read-only), as the console shows them. Only country rules are evaluated, and only when a country is given; a hidden level that keeps the visitor out is still named as a blocker. Day-of-week, time and date rules depend on the moment of the request; to simulate a visitor read /rest-api/placements/{placementId}/banner-probability. Requires VIEW permission on the banner's advertiser and VIEW access to the placement's site.
Query Params
bannerId integer required
The banner (creative)
3001 placementId integer required
The placement it should serve on
4001 country string
The visitor's country, two-letter code (US, DE): its country targeting is then evaluated
US Responses
200
{success, bannerId, placementId, blockers:[..], warnings:[..], targeting:{level:{combine, rules:[..]}}}
400
Bad request — invalid or missing parameters
401
Authentication error
403
No VIEW permission on the banner's advertiser, or no VIEW access to the placement's site
404
Banner or placement not found; a deleted one is answered with a blocker