Work with zones
Create a zone to group a site's placements, what the five zone-level cards do for every placement in the group, how to move or copy zones and placements without breaking ad tags, and what deleting a zone takes with it.
A zone is the middle level of the supply tree: a named group of placements inside one site. It carries no ad tag of its own — it exists to organise placements, to give reports a grouping, and to hold the filters and rules that apply to every placement in the group, so you set them once instead of once per placement.
Example. dailynews.example.com has 4 article-page slots and 3 homepage slots. Two zones, Article Pages (4 placements) and Homepage (3 placements), let the publisher read revenue per page area in one report row each, and let the network manager ask DSP partners to keep the Gambling IAB category off all 4 article slots with one blocked category on the Article Pages zone instead of four.
Typical scenarios
| You want | Set | Where |
|---|---|---|
| Revenue per page area in reports | One zone per area: Homepage, Article Pages, Sports section | Site → Add new zone |
| Premium vs. remnant pricing on the same site | Zones Premium and Remnant; placements grouped by what they are sold as | Site → Add new zone, then drag placements between them |
| Ask DSPs to keep adult or gambling ads off a whole section | The blocked IAB categories once on the zone’s OpenRTB integration card (programmatic demand only — see Keep unwanted ad categories off your inventory) | Zone editor |
| Pair a section with the right advertisers automatically | Category or label Matching rules on the zone; check the result on Matched banners | Zone editor |
| Retire a page area without losing its tags | Move the placements to another zone first (keys are kept), then delete the empty zone | Publishers tree, drag and drop |
Step by step
-
Open the site (Account → Publishers → site) and click Add new zone in the header.
-
Enter the Name (up to 128 characters). It is the only required field — a zone has no category and no size. If your role can switch zones on and off, the Active switch, on by default, sits under it.

-
Optionally open Additional information for a Description, and fill any additional fields your network has configured.
-
Click Save. You get a Zone saved toast and land on the full zone editor. Until the zone has its first placement it shows the nudge “This zone has no placements yet — A placement is the actual ad slot — the zone serves nothing without one. Create the first placement and link banners to it.” with the same Add new placement… menu as the header.

-
Click Add new placement… and pick a type — see Create a placement.

-
Switch on the cards the zone needs from the Features rail and fill them in. They appear only after the first save, in this order:
Card What it does for every placement in the zone Pre-targeting Traffic filters. See Pre-targeting and blocking. OpenRTB integration IAB categories (sent as sectioncat) and blocked IAB categories (merged intobcat) in the bid requests for this zone. See how the levels combine.Matching rules Category/label rules that auto-pair this zone’s inventory with demand. See Rules and defaults. Matched banners Read-only cascade of the advertisers → campaigns → banners the rules currently match.
The editor’s header carries the placements counter — the title reads Article Pages (placements: 4) and the count links to the zone’s placement list — the site / zone switchers
in the breadcrumb and title for jumping to a sibling without going back to the tree, the
Add new placement… menu, and Delete this zone.
Move or copy a zone or placement
Drag a zone onto another site, or a placement onto another zone, in the Publishers tree; the dialog asks whether to Move or Copy (with the number of copies, 1 to 20) and whether to Keep banners linked. The grid clipboard does the same: put zones or placements in it, open the destination site or zone, and choose Move or Paste a copy.
- A moved placement keeps its placement key, and a zone moved to another site keeps the keys of every placement in it — so every ad tag already published for them keeps serving, unchanged.
- A copy is a new placement with a new key: its tags have to be taken from the copy.
- Keep banners linked on a move leaves the placement’s banner links as they are; cleared, it unlinks every banner and takes them out of the placement’s daisy chain. On a copy it decides whether the copy is linked to the same banners.
- Moving needs update rights on both sites — the one the entity leaves and the one it joins.
- Nothing is moved or copied into a deleted zone or site, or out of one: the move is refused with a message naming the deleted entity, and the placement or zone stays where it was. The same holds for campaigns and banners in the Advertisers tree.
Caveats and exceptions
- Who sees what. A publisher gets the zone itself (Basic info and Add new placement…); the
five cards belong to the network side. Which cards a network role sees depends on its grants —
see User roles. On a Can View share the form is read-only and
Add new placement… is hidden; ask the owner for Can Edit (deleting needs Is Owner).
On a masked share the name shows as
ZONE_<id>and is locked, Description is not rendered, Add new zone / Add new placement… are not rendered, and the placements under the zone are masked too. - Matched banners needs Matching rules. The Matched banners card renders only when the Matching rules card is visible too. A role that cannot see Matching rules never gets Matched banners, and nothing on screen says why.
- Deleting a zone deletes every placement under it. The confirmation says so literally —
“The zone will be deleted along with its placements. You can restore it within 90 days. Are you
sure?” — and it means it: the delete cascades to each placement, and those tags stop answering.
The cascade reaches the ad server almost immediately, not on the next cache reload: each deleted
entity publishes an update that patches the ad server’s in-memory inventory, so a tag deleted
“just to test” is dark within seconds. For 90 days Recently deleted (the box-with-arrow button
in the Publishers tree’s action rail, and the link on the delete toast), the Undo on the toast
of a delete made from the tree rail, or
POST /rest-api/deleted-entities/{type}/{id}/restorebrings the zone and those placements back — their tags answer again after the ad server’s next reload, see Restore something you deleted — but traffic is lost in between. Move the traffic first. - Zone pre-targeting is a filter, not a merge. A request must pass site and zone and placement pre-targeting, evaluated broadest-first and failing fast. A rule that allows traffic at placement level still loses if the zone blocks it.
- Name length is checked by the server. The 128-character cap on Name is enforced on save, not by the input, and the over-length failure has no friendly message registered — you get the validation framework’s generic “size must be between…” text rather than something naming the field.
- Some save errors arrive as a toast. A zone save can fail with an affiliate-related message shown as a toast rather than under a field. Nothing is highlighted on the form — read the toast.
Not working?
| Symptom | Check | Where |
|---|---|---|
| No Add new zone button on the site | Your share is masked or view-only; the button is not rendered. Ask the owner for Can Edit. | Site header; share settings on the owner’s side |
| A placement in the zone will not serve although its own pre-targeting allows the traffic | The zone or the site blocks it — all three levels must pass. | Site → Pre-targeting, zone → Pre-targeting, placement → Pre-targeting |
| Matched banners card is missing | Your role lacks the Matching rules card; Matched banners never shows without it. | User roles |
| Save fails with “size must be between…” | Name is over 128 characters. | Zone → Basic info → Name |
| Save fails but no field is highlighted | The error came as a toast (affiliate-related). | The toast in the corner of the screen |
| ”You do not have permission to edit this zone” / “Access denied” / “Permission denied” | Three different refusals: a zone edit, a zone delete, and a placement edit respectively. The exact wording tells you which action was refused. | Role grants or share level on that entity |
| A tag went dark right after a delete | Deletes patch the ad server within seconds. Restore from Recently deleted or the toast’s Undo; tags answer again after the next ad-server reload. | Publishers tree action rail → Recently deleted |
| Drag-and-drop move is refused | Either side is deleted (the message names it), or you lack update rights on the source or destination site. | Publishers tree; share level on both sites |
Reference
The whole zone form, in the order it renders.
| Field | What it does | Control | Default | Where | Notes |
|---|---|---|---|---|---|
| Name | Zone display name | Text, max 128 | — | Both | Required. Locked (and skipped on save) on a masked share. |
| Active | On/off for the zone and every placement under it | Toggle | On | Both | Shown only if your role can switch zones on and off. |
| Additional fields | Network-defined custom fields | Varies | — | Both | Only when your network has configured them. |
| Description | Free-text notes | Textarea | — | Both | Under Additional information. Not rendered at all on a masked share. |
| Created | Creation date | Read-only text | — | Edit | Last field in Additional information. |
| Role or share | Gets |
|---|---|
| Publisher | Basic info and placements; the five cards belong to the network side. |
| Network manager | Basic info plus all five cards (per its grants). |
| Can View share | Read-only form; Add new placement… hidden. |
| Can Edit share | Edit; deleting needs Is Owner. |
| Masked share | Name as ZONE_<id>, locked; Description hidden; placements masked. |
Exact grants: see User roles.
Over the API
- Matched Ads —
GET /rest-api/matched/ZONE/{zoneId}.do?returnType=ADVERTISER|CAMPAIGN|BANNER(BANNERwhen omitted), with the card’s filters andstart/limit; it needs the Matched advertisers permission. Sites and placements use the same endpoint. - Open RTB categories —
GET/POST /rest-api/zones/{zoneId}/openrtb.doreads and setsiabCategoriesandblockedIabCategories(ids or IAB codes such asIAB1_2); only the lists sent change, and an empty list clears one. It needs the Open RTB permission.GET /rest-api/iab-categories.dolists the catalogue. A placement’s card is/rest-api/placements/{placementId}/openrtb.do, which also takesblockedBannerAttributesandcustomOpenRtbTagId— see Set a placement’s OpenRTB settings, which also explains how the zone’s lists combine with the site’s and the placement’s. - Custom fields —
/rest-api/additional-fields/ZONE/{zoneId}.do. - Move —
POST /rest-api/zones/update.dowith the zone’sidand anothersiteIdmoves the zone; a placement moves the same way through itsupdateendpoint with anotherzoneId. Both keep the placement keys (see Entities via API). From an AI assistant,entity_updatewithparentIddoes it. - Restore —
POST /rest-api/deleted-entities/{type}/{id}/restorewithin 90 days of a delete.