Browse the help center

Other admin tools

The seven small admin CRUD pages — custom ad units & sizes, system banner templates, VPAID frameworks, video requirement presets, upstream macro presets, auto placements and additional entity fields — the routine they share, where each one takes effect elsewhere in the platform, and what each one does not do.

How-to admin Admin → Creatives & tags

Seven small admin CRUD pages don’t warrant a page each, but they are easy to miss because each one is really a lever on a feature that lives somewhere else: custom ad units & sizes decides which sizes a network manager and an advertiser can pick, system banner templates stocks the catalogue a Template creative renders from, VPAID frameworks feeds the video-creative flow, video requirement presets are the publisher specs a site’s video creative requirements are filled from, upstream macro presets are the stitchers a video placement’s tags are built for, auto placements feeds new-site setup, and additional entity fields adds columns to account edit forms. This page covers the routine they share and the four smallest in full; the three bigger tools have a guide each.

On this topic: Custom ad units and sizes · Video requirement presets · Upstream macro presets

Example. A publisher signs up and its site is approved. Nothing on the site page was typed by hand, yet it already has a zone “Sports Daily Placements” with a 728×90 and a 300×250 placement in it: the two Auto placements rows did that, sized from two custom ad units, because the approver’s role grants Automatic placements creation for approved sites. The advertiser who later builds a Template creative for the 300×250 picks a system banner template marked (global), and the extra Cost centre box on every campaign’s Basic info card is an additional entity field.

Typical scenarios

You wantToolWhat to set
A 970×250 billboard in the size dropdownsCustom ad units & sizesTitle Billboard (970x250), Site Placement, both sides on
One HTML template every advertiser can fill inSystem banner templatesAdd it here — created here it is (global), read-only for accounts
An interactive video creative from a vendor’s VPAID adapterVPAID frameworksUpload the .js, add its parameters; include one named duration
Roku’s spec on every Roku-facing siteVideo requirement presetsEdit the Roku spec → Apply to N sites
Tags a new stitcher can fillUpstream macro presetsFill with AI with the stitcher’s tag URL
Every approved new site to get a 300×250 placementAuto placementsOne row: Site, Medium Rectangle (300x250), Active — plus the account-side permission on the approver
A Cost centre box on every campaignAdditional entity fieldsName cost_center, Title Cost centre, Entity Campaign

Step by step

All seven pages share the same shape, so the routine is the same each time.

  1. Open Admin. Five of the seven sit in the sidebar group Creatives & tags (Custom ad units & sizes, System banner templates, VPAID frameworks, Video requirement presets, Upstream macro presets); Auto placements and Additional entity fields configuration sit under Ad serving.

    Custom ad units and sizes grid with the Creatives and tags sidebar group open

  2. Pick the page. Each opens on a grid with Add, Edit and Delete above it (Video requirement presets adds Duplicate and Apply to N sites for the ticked row; Upstream macro presets has no Delete — a preset is retired by switching it off).

  3. Add, or select a row and Edit, to reach the form. Field-by-field detail is under Reference below, or on the tool’s own guide.

  4. Save. On VPAID frameworks and System banner templates the first save is load-bearing: their sub-grids (framework parameters; template files, properties and target-related bodies) only appear once the row has an id, and the page navigates itself to the new edit URL to reveal them. A successful save raises a Done toast (saving a VPAID framework parameter raises Record successfully processed. instead).

  5. Delete removes the row. Only custom ad sizes refuse a delete that would break something, and video requirement presets warn first — see the caveats.

Caveats and exceptions

  • One permission per page. Each of these pages is its own Admin UI permission on your role, so you may well see one and not the others — see Users, roles & permissions. Opening the URL of a page your role does not grant shows Record not found. instead of the page. Network managers, publishers and advertisers never see these pages; they meet the results in their size, template and framework dropdowns, generated placements and extra form fields. Switch into a user’s account to check.
  • Auto placements need two grants. The admin permission edits the templates; for them to generate anything, whoever creates or approves the site also needs the account-side Automatic placements creation for approved sites permission. That is a separate grant on a separate role — without it no placements appear.

System banner templates

  • The grid is not restricted to system templates. Templates an account user created appear in it too, tagged (local) after the title. Editing one from here leaves it local — only a template created here (or imported here) is global — but deleting one from here deletes that user’s template. The same in-use warning applies as on the account side — here it also names the banners and placements — and confirming detaches the template from them; see Create and manage banner templates.
  • A template serves exactly one placement type, and the admin form offers seven of them — including Video, Email and Click-through, where the Template creative type is not offered at all. A template authored for those types is saved and then unreachable.

VPAID frameworks

  • An uploaded adapter is not published the moment you save it. Saving writes the JavaScript into the database; a scheduled worker copies it to the file store and purges the CDN copy once a minute. Expect up to a minute between saving a new adapter and players receiving it.
  • Renaming changes the adapter’s URL. Because the served filename is built from the framework’s Name, the next sync writes the file under the new name; the old file is not removed. Deleting a framework likewise leaves its .js behind in the file store.
  • Active frameworks only, gated by a permission. The framework dropdown on a creative is gated by the account role’s VPAID Framework permission and loads active frameworks only. Deactivating a framework hides it from new creatives but does not touch creatives that already reference it.
  • A network-wide default. Default VPAID framework on Inventory & campaigns settings picks one for every new video creative, and it lists active frameworks only.
  • The duration parameter is special. A parameter named duration supplies the VAST <Duration> in seconds. Without a usable value there, Epom emits the placeholder 00:00:00 — schema-valid, but not what a player expects.

Auto placements

  • A row with no size is skipped entirely during generation. The size is optional in the edit form but mandatory for the row to do anything, and nothing warns you. Always set one.
  • The size list is filtered differently from every other size picker: custom units are dropped, but the deprecated Any Size unit is not — the reverse of the creative-side lists. A template sized Any Size is legal, and on the publisher-signup path it is special-cased so the generated placement is named after the site alone rather than “<site> Any Size”.
  • De-duplication is by the template’s name. It compares placements already in the auto-placements zone against the template’s name. In the three paths that name a generated placement after its template that works as expected, and re-approving a site creates no duplicates. In the publisher-signup path the placement is named “<site> <size>” instead, so it never matches the template name and the guard does not fire.
  • Renaming a template later does not rename the placements it already produced — and, because de-duplication keys on the name, a renamed template will generate a second placement next to the first on a site it has already run against.
  • Approval decides when it runs. On the paths that create a site, a new site is Approved when the acting user holds the Sites approval permission (a switched-into session also counts in the account Publishers UI). Otherwise the publisher signup and the Publishers UI give it the network default site status — and if that is not Approved, the new site generates nothing until someone approves it on the Sites page, which then runs generation.

Additional entity fields

  • Storage only. These fields are shown on the edit form and saved per entity, but they never reach the ad server — they are not targeting keys, macros or report dimensions. Use them for internal notes and external reference IDs, not for ad-serving logic.

The caveats of the three bigger tools are on their own pages: sizes, video requirement presets, upstream macro presets.

Not working?

SymptomLikely causeCheck
A page is missing from the admin sidebar, or its URL shows Record not found.Your admin role lacks that page’s permissionUsers and roles → Admin UI permissions
A new site got no auto placementsThe site was not Approved at creation; the approver lacks Automatic placements creation for approved sites; every active row has no size; or no row is ActiveSites page → approve; the approver’s account role; Auto placements rows
A site got a second copy of a placementThe template was renamed, or the site came through publisher signup (named site size, so the guard does not fire)Delete the duplicate; keep template names stable
A new template is editable by accountsIt was created on the account side, so it is (local)Create or Import it here to make it (global)
An advertiser cannot find the templateIt was authored for Video, Email or Click-through, where the Template creative type is not offeredRe-create it for a Site / Mobile / Non-standard type
Players do not receive a new VPAID adapterThe once-a-minute sync has not run yetWait a minute
A VPAID framework is missing from the creative’s dropdownIt is inactive, or the account role lacks VPAID FrameworkFramework → Active; the account role
The VAST shows <Duration>00:00:00</Duration>No parameter named duration with a usable valueAdd a duration parameter to the framework
The additional field does not appear on the formWrong Entity, or the user is on a different entity typeEdit the field
A new size is not offered where expectedPlacement types / sides on the unitCustom ad units and sizes
A spec or a stitcher preset misbehaves—Video requirement presets, Upstream macro presets

Reference

Essentials; every field of the four smallest pages, the neighbouring Targeting presets pages and the permission behind each page are on Other admin tools reference.

SectionRead it for
System banner templatesWhat differs from the account-side template editor; template types and the content macro each body needs
VPAID frameworksName, Active, File; framework parameters; what the VAST carries at serve time
Auto placementsThe four fields; when generation runs and what it creates
Additional entity fields configurationName, Title, Entity; where the field appears and what it takes
Also in these sidebar groupsThe Targeting presets pages, documented elsewhere
PermissionsThe Admin UI permission behind each of the seven pages

Custom ad units and sizes

Admin → Creatives & tags → Custom ad units & sizes. An ad unit is a named creative size. The catalogue here is what every size dropdown in the product is drawn from — the placement’s Size combo, the creative’s Ad unit combo, the header-bidding slot editor, the auto-placement template. Placement types plus the Inventory side / Campaigns side flags decide where a size shows up; a unit with no placement type ticked appears nowhere. Full guide → Custom ad units and sizes.

Video requirement presets

Admin → Creatives & tags → Video requirement presets. The publisher video specs a network manager picks from with Use a publisher spec on a site’s Video creative requirements card. The network starts with the major streaming publishers’ published specs and they are yours to correct, duplicate, retire or delete; Fill with AI reads a spec from a PDF, a link or pasted text, and Apply to N sites pushes a corrected spec to every site filled from it. Full guide → Video requirement presets.

Upstream macro presets

Admin → Creatives & tags → Upstream macro presets. The server-side ad insertion stitchers a video placement can name under Server-side ad insertion (SSAI), and for each one the macro it fills into each of the ad server’s tag parameters, so the publisher pastes a tag the stitcher can fill as it is. Seven stitchers are built in; Fill with AI reads a new one’s macros from its documentation or a tag URL. Full guide → Upstream macro presets.

Over the API

The values an entity carries in additional fields are read and set with GET / POST /rest-api/additional-fields/{entityType}/{entityId}.do (entityType is ADVERTISER, CAMPAIGN, BANNER, SITE, ZONE or PLACEMENT). The POST body is a JSON object mapping a field id or name to its value, e.g. {"cost_center": "EU-42"}; only the fields sent change, and an empty string clears one. A field that does not exist or belongs to another entity type refuses the whole request, and a value is at most 255 characters. Reading needs view rights on the entity and writing needs update rights, as in the Basic Info card.

The single-entity reads — GET /rest-api/advertisers/{id}.do, /rest-api/campaign/{id}.do, /rest-api/banner/{id}.do, /rest-api/sites/{id}.do, /rest-api/zones/{id}.do and /rest-api/placements/{id}.do — carry the same values as additionalFieldValues, keyed by field id: {"7": {"name": "cost_center", "value": "EU-42"}}, with value null for a field the entity has no value for. The list endpoints leave them out; read them per entity.

Video requirement presets have their own operations under /rest-api/video-requirements/presets.do (list, read, add, change, copy, delete, apply to sites) and …/preset-from-document.do (read a spec document); every change needs the Video Requirement Presets admin permission and whoami reports may.videoRequirementPresets — see Video requirement presets → Over the API.

Upstream macro presets are under /rest-api/upstream-macro-presets (list with usedBy and parameters, read by id or code, add, change, retire with {"active": false}) and …/from-document; reading needs only a signed-in user, every change and every document reading needs the Upstream Macro Presets admin permission, and whoami reports it as may.upstreamMacroPresets. A placement names its preset by code: ssaiStitcher on POST /rest-api/placements/update/video and on the MCP placement_create tool — see Upstream macro presets → Over the API.

Ad units are listed by GET /rest-api/ad-units.do, per placement type — see Custom ad units and sizes.

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.