Product · 4 Aug 2026
When a JS tag is enough — and when it is not
Start simple. Move to OpenRTB or Prebid when you need competing demand, cleaner logs, and less work on the device.
A JS tag is the right first step for a new site, a proof of demand, or a placement that will never justify a wrapper. You get a live unit, basic reporting, and a short path to revenue. Most publishers should not start with a full header-bidding stack on day one.
Where a tag is enough
Use a tag when you have one or two sizes, modest volume, and a single demand partner. It is also enough for a landing page, a seasonal microsite, or a test placement you may remove in a month. Ops can paste the snippet, QA the creative, and stop.
Where it stops scaling
A tag is the wrong long-term path when you run many sizes, need header-bidding competition, or must reconcile impression logs with a warehouse. Tags put more logic in the browser, which is harder to debug at scale and easier to break with a consent or CMP change.
You also lose a clean bid stream. OpenRTB gives you request and response logs, timeout visibility, and a schain you can show to buyers. A tag often gives you a filled or unfilled pixel and a weekly CSV.
A sequence that does not force a rewrite
A common path: JS tag to confirm the placement, OpenRTB S2S for the app or high-volume web, Prebid on web where other demand already lives in the wrapper. You should not have to rip out the first integration to add the second.
Amli Media supports tag, OpenRTB, and Prebid so the same seat can start on a snippet and move demand onto S2S without changing how finance sees the account.