Browse the help center

Block demand and inventory (pre-targeting blocks)

Block a named advertiser, campaign or banner on a placement, a site or all your sites from the Banners probability card — or a named site or placement from a banner or campaign in an analytics report — then find the Blocking and "is Blocked by" chips, remove them in the right place, and know why a block still applies with targeting switched off.

How-to network manager publisher Account → Publishers → site → zone → placement → Banners probability

Besides dimension rules (browser, operating system, day of week…), the two sides of the platform can refuse each other by name: a placement or site refuses a named banner, campaign or advertiser, and a banner or campaign refuses a named site or placement. Both are stored as ordinary targeting rules in five dedicated rule types — Blocked Banners, Blocked Campaigns, Blocked Advertisers, Blocked Placements and Blocked Sites — that never appear in the add-rule picker on the Targeting card: blocks come only from the two flows below, and they keep applying even when the entity’s targeting switch is off.

Example. dailynews.example.com has 6 placements. The publisher opens one of them, sees Stonebridge Media winning 18 % of its traffic on the Banners probability card, and blocks the advertiser on Site. One rule is written on the site; all 6 placements refuse every Stonebridge campaign — including the two Stonebridge creates next month — and Stonebridge sees the site under is Blocked by on its own Targeting card only if its role holds Blocked by.

Typical scenarios

You wantSetWhere
One creative off one slot, the rest of its campaign untouchedBlock as: Banner, On: PlacementPlacement → Banners probability → ⊘
An advertiser off a whole site, future campaigns includedBlock as: Advertiser, On: SitePlacement → Banners probability → ⊘
An advertiser off all 14 sites you can see todayBlock as: Advertiser, On: All sites — 14 rows, one per site; a 15th site created tomorrow is not coveredPlacement → Banners probability → ⊘
Stop a campaign spending on 3 low-performing sitesReport grouped by Site + Campaign, tick the 3 rows, Block siteAccount → Analytics
See who blocked your creativeis Blocked by group on the banner’s Targeting card (needs the Blocked by grant)Banner → Targeting

Step by step

Block an advertiser, campaign or banner on your inventory

  1. Go to Account → Publishers → site → zone → placement and scroll to Banners probability. The grid lists every eligible banner with its computed share of the placement’s traffic; the placement must be saved and the banners linked to it, since the grid is a live simulation and rows that cannot win right now show as NA.

  2. Optionally narrow it: the Search box matches advertiser, campaign and banner names, and Grouping (Banner / Campaign / Advertiser) collapses the grid to that level.

  3. On the row you want, click the Block button at the end of the row (a circle-with-slash icon). A popover opens headed Block <row name> with two choices:

    • Block as — Banner, Campaign or Advertiser. Only the current grouping level and the levels above it are offered, so grouping by Advertiser leaves Advertiser as the only choice.
    • On — Placement, Site or All sites. A control with a single option renders as plain text rather than a segmented button.

    Placement edit page with the block popover open on a Banners probability row

  4. Click Block. A confirmation dialog asks “Block advertiser on site?” (the wording follows your two choices). Click Confirm. On success a green toast reads “Successfully blocked advertiser on the specified scope” and the grid reloads.

  5. Open the Pre-targeting card of the entity you wrote the rule to — the placement for a Placement scope, the site for Site and All sites. The new rule sits under Excluded: Blocking, as a chip such as Advertiser: Northwind Media.

    Pre-targeting card showing a Blocking group and the always-applies warning

Block a site or placement from your demand (the mirror direction: the rule is written on a banner or campaign and names a site or placement)

  1. Go to Account → Analytics and build a report that groups by Site (or Placement) together with Banner or Campaign — the buttons only appear for those combinations. Click Run report and wait for the results grid.

  2. Tick the rows whose traffic you want to cut off. A highlighted selection bar appears above the grid reading “N selected”. Click Block site or Block placement.

    Analytics report with a row selected and the Block site button in the selection bar

  3. A toast reads “Records have been blocked”. The rule is written to each selected row’s banner if the report groups by Banner, otherwise to its campaign.

  4. To undo, select the same rows and click Unblock site / Unblock placement, or open the banner’s (or campaign’s) Targeting card and remove the chip from Excluded: Blocking.

What each choice actually writes. Block as decides which entity the rule names, and therefore how much demand it removes; On decides where the rule is stored, and therefore how much inventory it covers.

Block asRule typeWhat stops serving
BannerBlocked Bannersthat one creative; the campaign’s other banners keep serving
CampaignBlocked Campaignsevery banner in that campaign
AdvertiserBlocked Advertisersevery campaign the advertiser has — including campaigns created after you set the block, because the ad server resolves the advertiser’s campaign list at request time
OnRule is written onRows createdReach
Placementthe placement1this placement only
Sitethe site the placement belongs to1every placement under that site, including ones added later
All sitesevery site your account can currently seeone per sitethose sites only — a site created afterwards is not covered, because the fan-out is a snapshot taken when you click Block

Where a block appears, and where to remove it

A block is one row, shown from both ends. The side that owns it sees it under Blocking; the side it was aimed at sees it under is Blocked by — and that second group exists only for users who hold Blocked by.

RuleOwned byShown as Blocking onShown as is Blocked by onRemoved from
Blocked Banners / Campaigns / Advertisers, scope Placementthe placementthe placementthe entity it names, and everything under it — an advertiser block also surfaces on each of that advertiser’s campaigns and bannersthe placement’s Pre-targeting card
Blocked Banners / Campaigns / Advertisers, scope Site or All sitesthe site (one row per site)the site — and every placement under itsame as aboveeach site’s Pre-targeting card
Blocked Sitesthe banner or campaignthat banner or campaignthe named site, and its zones and placementsthe banner’s/campaign’s Targeting card, or Unblock site in analytics
Blocked Placementsthe banner or campaignthat banner or campaignthe named placement onlythe banner’s/campaign’s Targeting card, or Unblock placement in analytics

Unblocking is direction-specific. The analytics Unblock site / Unblock placement buttons only remove Blocked Sites and Blocked Placements rows from a banner or campaign. They cannot touch a publisher’s block on their inventory, and nothing in analytics can — those come off the placement’s or site’s own Pre-targeting card.

Caveats and exceptions

Before you start

  • Blocking by name is switched off for all three roles as shipped, on both sides. The Banners probability grid is there, and reports run as usual, but the Block buttons are not drawn until your network administrator turns the scope you need on for your role. Each scope — this placement, this site, all sites — is switched on separately, as is being able to see who blocked me. A publisher blocks from the Banners probability card; every scope also needs Show Blocked Banners, the permission that writes the block — without it no Block button is drawn, whichever scopes are on. An advertiser blocks from an analytics report; Block site and Block placement are switched on independently. A network manager has both entry points once they are switched on. On a Can View share, blocked chips have no ✕ or Clear all and no Block button appears; blocking needs Can Edit or Is Owner.

How blocks behave

  • Blocks keep working when targeting is switched off. The ad server loads blocked-entity rules regardless of an entity’s targeting switch, so turning Pre-targeting off does not release anything you blocked. The card stays collapsed while its switch is off and does not list any rules, so a placement with blocks and targeting off shows only the card header — and on a window wide enough for the Features rail not even that, only the switched-off rail entry — even though it is still refusing the blocked demand. To review or remove blocks, switch targeting on: the block groups and the “Blocked entities stay blocked even when targeting is off” note appear in the card body.
  • Creating a block silently switches targeting on for the entity that receives the rule, because the write path enables it. Any positive rules that entity already had — and that you had deliberately parked by switching the card off — start applying again at the same moment. The page does not repaint the switch, so it still reads off until you reload the page; reload after blocking to see the real state.
  • OR between rule types can skip the blocks. Rule types are evaluated in order with blocked types last, and OR stops at the first type that passes — so a placement with any passing dimension rule never reaches its blocked list. Leave entities that block on the default AND.
  • The Banners probability grid lags. The rule is saved immediately, but the grid reads the ad server’s in-memory cache, so the change shows only after the next cache refresh. A blocked advertiser or campaign then shows as NA; a blocked banner drops off the grid.
  • All sites is not a switch, it is a bulk write. For a banner-level block the fan-out covers the sites shared with you plus any site the banner is already linked to; for campaign and advertiser levels it covers the sites shared with you. Each resulting row is independent, so undoing it means removing the chip on every site one at a time — there is no “unblock everywhere” action.
  • Blocking from analytics writes one rule per selected row, in sequence, and stops at the first refusal. The rows before it stay blocked and the rest are not attempted; the error toast names the refusal, not the row. A block or unblock the server refuses — a missing permission, or a row it cannot write — shows the server’s reason as an error toast instead of the success one. An Unblock that finds no matching block has nothing to refuse, so it still reports success; after a bulk unblock, confirm on the banner’s or campaign’s Targeting card that the chips are what you expect.
  • A block that points at a deleted entity is kept but hidden from the card, so restoring a deleted banner or site also restores every block that named it.
  • Blocked rules are always exclude rules — the server rejects anything else with “Please use only Exclude rule.” — so both groups only ever render an Excluded: block, never an Included: one.

What the chips show

  • Inherited chips. A placement’s Pre-targeting card lists its site’s blocks inside its own Blocking group, marked (inherited from the site) and without an ✕ (a banner does the same with its campaign’s blocks, marked (inherited from the campaign)). The block is one rule on the site or campaign that applies to every placement or banner under it, so it is removed on that parent’s own card, not from a child.
  • The same entity blocked at both placement and site level produces two chips with identical text in the placement’s Blocking group. Removing one leaves the other in force.
  • The popover header and the confirmation dialog can both name the wrong thing. With Grouping on Banner and Block as on Advertiser, the header still reads “Block Northwind Leaderboard 728x90” and the dialog only says “Block advertiser on site?” — neither names the advertiser you are about to remove from the placement. Read the Block as control, not the header.
  • The ✕ on a blocked chip is drawn for anyone who can manage the card, even without the blocked-type permission. Without Show Blocked Banners the click comes back as “You do not have permission to delete target for this Zone” and the chip stays. The toast says “Zone” whichever entity the card is on — its wording is fixed in the card.
  • Masked names. A name in these chips is masked when you cannot view that advertiser or site, and — if your account has Mask Campaigns or Mask Inventory — also when you do not own it. The masking applies on every targeting card, supply and demand. The masked text is built from the id (ADVERTISER_9, SITE_4), except on a masked blocked-advertiser chip, which can show the bare type token BLOCKED_ADVERTISERS instead of any label.
  • A stray HTML tail. An is Blocked by chip for a banner-level block on a site, zone or placement card ends in a fragment of HTML — … > Banner: Northwind MPU 300x250 <a href="/account/advertisers/banner-preview.do?…"></a>. Ignore the tail; the part before it is the real value.

What the blocked advertiser sees

  • Nothing, by default. A blocked banner simply stops being selected; there is no notice, no status change, and no entry on the campaign — the traffic just stops. The ad server files the drop under the same generic targeting exclusion it uses for any rule that did not match, so even a troubleshooting trace does not separate “the publisher blocked this creative” from “it failed the country rule”.
  • The one place it does surface is the entity’s own Targeting card, under is Blocked by, with a chip like By Site: Harbour Gazette or By Site: Harbour Gazette > Zone: Homepage > Placement: Article MPU. That group is added only for users holding Blocked by — so two people can open the same banner and only one of them learns that a publisher has blocked it. It aggregates upwards too: a banner shows blocks aimed at its campaign and its advertiser, not only at itself.

Not working?

SymptomCheckWhere
No Block button on the Banners probability rowsThe scope permissions (Block … on Placement / Site / All sites) and Show Blocked Banners are off for your role; or the share is Can View.Your network administrator; the share level
No Block site / Block placement in the reportThe report must group by Site (or Placement) and Banner or Campaign; the Blocked Sites / Blocked Placements permission must be on.Analytics → Group by; your administrator
Blocked, but the grid still shows the rowThe grid reads the ad server’s cache; wait for the next refresh.Placement → Banners probability
The block does not take effect although it is listedThe entity’s rule-type operator is OR — a passing dimension rule stops evaluation before the blocked list. Set it back to AND.Entity → Targeting → Between rule types
Blocks are not listed on the cardThe switch is off and the card is collapsed; blocks still apply. Switch it on to see them.Placement → Pre-targeting switch
Positive rules started applying after a blockCreating a block switches targeting on; reload the page to see the real state.The entity’s Targeting switch
Removing a chip is refused: “You do not have permission to delete target for this Zone”Show Blocked Banners is missing (the toast says “Zone” on every entity).Your administrator
A chip has no ✕It is inherited from the site or campaign — remove it there — or your share is Can View.Parent’s Pre-targeting / Targeting card
You removed a chip but the block still appliesThe same entity is blocked at another level (placement and site; an All sites fan-out row per site). Check every level.Each site’s Pre-targeting card
Unblock site did nothingIt only removes Blocked Sites / Blocked Placements on a banner or campaign; a publisher’s block on inventory is removed on the placement’s or site’s card.Placement / site → Pre-targeting
Only some rows were blocked from analyticsThe write stops at the first refusal; the toast names the refusal. Re-select the remaining rows.The error toast
A site you created later still serves the blocked advertiserAll sites is a snapshot; block it on the new site too.New site → Banners probability
A blocked banner came back after a restoreBlocks naming a deleted entity are kept hidden and return with it — expected.—
The confirmation named a creative, not the advertiserThe header follows the grouping level; the Block as control is what counts.The popover

Reference

Block popover (Banners probability grid)

ControlOptionsWhat it does
Header—Reads Block <name>, where the name is the row’s name at the current grouping level — not necessarily the entity you are about to block
Block asBanner, Campaign, AdvertiserChooses the rule type. Only the grouping level and the levels above it are offered
OnPlacement, Site, All sitesChooses where the rule is written. One option per Block … on … permission you hold
Block—Opens the confirm dialog (Confirm / Cancel)

Analytics selection bar (appears once at least one result row is ticked)

ButtonAppears whenWhat it does
Block site / Unblock siteBlocked Sites enabled, report grouped by Site and by Campaign or BannerAdds/removes a Blocked Sites rule on the row’s banner (or campaign)
Block placement / Unblock placementBlocked Placements enabled, report grouped by Placement and by Campaign or BannerAdds/removes a Blocked Placements rule the same way
Block channelChannel targeting enabled, report grouped by Banner and ChannelAdds a Channel exclude rule — a dimension rule, not a named block
Set banners OFFBanner-status permissions, report grouped by BannerDeactivates the banner; unrelated to blocking
ClearalwaysClears the selection

Groups in the Targeting / Pre-targeting card

HeadingContainsChips
Excluded: Blocking (N)blocks this entity holds, plus blocks inherited from its site or campaignremovable, with Clear all for the group — except inherited chips, which are marked as such and removed on the site or campaign
Excluded: is Blocked by (N)blocks other entities hold against this oneremovable unless your Blocked by grant is read-only

Permissions

PermissionLets you
Block … on Placement / on Site / on All sitesSee that option under On in the popover (one per scope)
Show Blocked BannersWrite a block from the grid and remove a blocked chip
Blocked Sites / Blocked PlacementsSee Block site / Block placement in the analytics selection bar
Blocked by (full or Read-only)See the is Blocked by group; the full grant adds the ✕

Over the API

The REST API covers the blocks only in part. It can create Blocked Sites and Blocked Placements on an advertiser, a campaign or a banner (POST /rest-api/{advertiser|campaign|banner}/{id}/targeting/{site|placement}/create.do), and it can block advertisers on a placement (POST /rest-api/placement/{placementId}/targeting/advertiser/create.do?advertiserIds=…&rule=…, which needs Block Advertiser/Campaign/Banner on Placement). It cannot block a campaign or a banner on a placement, or anything on a site or a zone — those come only from the Banners probability grid. GET /rest-api/blocked/entities.do lists the blocked advertisers and placements visible to the caller. Like the console, the placement endpoint takes only rule=EXCLUDE and answers anything else with a 400 “Please use only Exclude rule.”

Related pages

Please disable Adblock
Are you using adblock? Disable it and reload the page to proceed to the destination page.

A registration has already been submitted from this page. Please try again in 10 minutes.