What you get with Publink
An ad server that sits between your audience and the buyers you choose, decides each impression on your rules, and shows you the whole path. Here is what that means in practice.
You decide the impression, not the buyer
Floors, priorities, caps and targeting are yours. They run before any partner is called, so demand only ever sees the inventory you meant to sell.
- Floors and priorities per placement and per partner, with a guardrail under every test.
- Country, device, OS and environment rules; app and domain lists you maintain once and reuse.
- Creative blocks for advertisers, categories and specific creatives.
- Request and serve caps so a partner gets the volume you agreed on.
Rules first
A request that does not match never leaves your side.
Lists, once
Update a list and every placement using it follows.
Blocks that hold
Blocked creatives never render, whoever bid.
Pause anything
Placement, partner or campaign. History stays.
OpenRTB
Any endpoint that speaks 2.x, with a per-buyer template when needed.
VAST
Third-party tags, wrappers followed, served as-is.
Direct
Line items with a price and a flight, competing on equal footing.
Header bidding
Prebid-compatible, alongside everything else.
The buyers you choose, on the terms you set
Programmatic, tag-based and direct demand live on the same placement and compete for the same impression. Add a partner in minutes, pause it in a click, keep the history.
- Every inbound signal forwarded as received. Nothing stripped, nothing invented.
- Supply-chain objects built from your own sellers.json entries.
- Observed price next to declared price for every partner.
- A diagnostic that replays what a partner was sent and what came back.
See the whole path, request to render
Reports count from the same events that drive billing, so the number on the screen is the number on the invoice. When something is estimated, it says so.
- A live dashboard that shows the full day, hour by hour.
- Breakdowns by placement, partner, country, app, device and OS.
- A capture of any single request: signals in, rules applied, partners called, bids back, winner served.
- A no-fill reason for every miss: below floor, blocked, no bid, timeout, failed to render.
request ctv · us · 1920x1080 · vast
rules floor 2.40 · country ok · app list ok
demand 3 partners called · 2 bids · 1 above floor
decision partner-b · 3.10 · vast 4.2
render impression · quartiles · completeIllustrative. Values are examples, not live data.
One ruleset across web, in-app, CTV and audio
A rule you write once applies everywhere it makes sense. Environment-specific signals are added only where that environment uses them.
CTV
Content and app signals, bundle-level rules, identifiers passed through untouched.
In-app
iOS, Android and Fire OS with app lists and device targeting.
Web
Display and video on desktop and mobile web with domain lists.
Audio
Same targeting, reporting and demand controls as video.
Seats, roles and a playbook in the product
- Owner, manager and viewer roles with per-user permissions for reports, finance and campaigns.
- Publishers, advertisers and partners in one directory, each with its own pricing model.
- Step-by-step guides inside the product for the tasks you do most.
Set up with you, not handed to you
- A first serve on your own inventory during the demo, not a slide.
- Onboarding done together: company, placements, partners, floors.
- Answers in writing from the people who built it.
- Standards only: OpenRTB, VAST, sellers.json, schain. No lock-in.
See it on your own inventory
Bring a tag, a demand endpoint and fifteen minutes. We will walk you through a first serve end to end.
No forms to fill twice. One email, a real reply.