Wrapper as a Service

Keep your demand relationships. Stop maintaining Prebid.

For media groups and partners with their own SSP relationships and yield team. You bring the seats, we run the wrapper, Prebid Server and every upgrade, and you can add Valuad's demand to the same auction whenever you want.

Illustration of a wrapper frame holding the publisher's own demand modules and optional added demand, with an API key for reporting

Trusted by 100+ premium publishers, including

  • ynet
  • mako
  • N12
  • Israel Hayom
  • 24
  • TheMarker
  • Maariv
  • ONE

Direct integrations with the largest demand partners

  • Magnite
  • Microsoft
  • OpenX
  • Outbrain
  • Taboola
  • Criteo
  • Teads
  • TripleLift
  • Equativ
  • RTB House
  • Sovrn
  • OneTag
  • 33Across
  • and more

Why run someone else's wrapper

Building a Prebid wrapper is a project. Keeping it current is a job: Prebid ships a new major version every year or so, bidder adapters change, consent rules move, and Prebid Server has to stay up under your peak traffic. Wrapper as a Service lets your team spend that time on yield instead.

  • Your seats, your revenue

    Your SSP accounts run as your bidders, under your agreements.

  • Optional Valuad demand

    Add our demand partners to the same auction, reported separately from your own.

  • Reporting API

    Your data goes into your own tools through an API with scoped keys.

The publisher's own bids and added Valuad bids flowing into one auction that fills an ad slot

Your demand and ours, in one auction

Your own seats compete alongside any Valuad demand you choose to add, in the same wrapper and the same Prebid Server. Revenue from Valuad demand is reported separately, so you always know which part of the auction earned what.

  • The same wrapper our managed publishers use, with its fail-safes, refresh logic and unfilled-slot recovery
  • Hosted Prebid Server for the partners you want to call server-side
  • Billed as a technology fee on served impressions, not a revenue share on your own demand
An API key connected through code brackets to a reporting chart

Numbers that flow into your own tools

Wrapper as a Service publishers get their own data set and an external reporting API authenticated with API keys. Each key can be limited in what it can query, so you can hand one to your BI team or an agency without opening everything.

  • A separate data set for your traffic
  • API keys scoped by the breakdowns, filters and date ranges they may use
  • Per-site reporting for groups running many sites

How it works

  1. 1

    Bring your seats

    Share the SSP accounts and parameters you want to run. We configure them as your bidders.

  2. 2

    Integrate once

    Standard Google Ad Manager pages use our snippet. Apps that manage their own slots use a small JavaScript API or data attributes.

  3. 3

    Run your yield

    Your team manages demand and reads the numbers through the dashboard or the API. We keep the technology current.

Talk to an expert

After having years of experience with all kinds and sizes of agencies, developers, marketers, analysts and campaigners - I can say loud and clear that the people behind Valuad are the most brightest, enthusiasts, clever and growth drivers I have ever encountered. It's all about the people. Always.
Yaron AherDeputy CEO at The Jerusalem Post

Questions publishers ask

Does it work with single-page apps?

Yes. Declare slots in markup with data attributes or call vadHB.display() and vadHB.refresh() from your code. Slots your app destroys are cleaned up, so route changes don't leave stale slots behind.

Do I have to use Valuad demand?

No. Valuad demand is optional. If you add it, its revenue is reported separately from your own seats.

How is it priced?

As a technology fee on the impressions the wrapper serves, not as a revenue share on your own demand. Talk to us for the numbers.

Talk to the team behind Israel's largest publishers

Tell us about your sites and your ad server setup, and we'll show you where the revenue is.