Dokira
Dokira is an ad monetization platform that connects publishers to Google AdX and 17 bidding partners through one script, tuned by a named human contact.
Overview
Dokira is an advertising monetization platform for independent publishers, operated by ReVantage GmbH. The product pairs a single on-page script with a managed ad stack: Google AdX plus seventeen additional bidding partners, all routed through Prebid and OpenRTB demand connections. Instead of handing publishers a self-serve dashboard and leaving configuration to them, Dokira assigns a named contact who reads a site's traffic and adjusts the setup by hand. The company argues explicitly against the "here is a tag, good luck" model common in ad tech, contending that revenue movement comes from continuous human adjustment rather than the tag itself. The platform targets content sites that want both programmatic and direct demand without recruiting an internal ad operations team.
Key Features
One script, placed once. A publisher pastes a single tag into the page and the integration is finished. Every bidding partner sits behind that tag, and keeping all adapters and server connections healthy is Dokira's responsibility rather than the publisher's engineering team's.
Eighteen demand partners behind one integration. Google AdX anchors the stack, joined by Sovrn, Adagio, Improve Digital, E-Planning, NoBid, Adform, Criteo, AppNexus, InMobi, Omnidex, Receptiv, ProgrammaticX, RobustApps, Yandex, Onetag, Kueez and Perion. All of them compete for the same impression, which the company frames as more bidders per ad slot.
Human configuration instead of a template. Setup is not a dashboard the publisher operates, and not one template stretched across every site on the network. A person reviews traffic patterns and adjusts the configuration based on what those patterns show. Dokira treats this as its primary differentiator against tag-only vendors.
Direct sales alongside programmatic demand. Dokira maintains direct advertiser relationships in addition to the programmatic pool, so publisher inventory is not limited to whatever the real-time auction happens to clear. Premium demand and direct deals run through the same integration.
Dual demand routes through Prebid and OpenRTB. Browser-side Prebid adapters and server-side OpenRTB connections operate in parallel. A public interactive illustration walks through the four auction stages, request, demand, auction and ad served, and lets visitors filter the flow by demand route.
No exclusivity and no setup fee. Publishers keep existing direct-sold business and any other monetization partner already in place. Dokira takes a share of what it monetizes, with nothing charged before revenue exists.
Anonymised results shared on request. The company declines to publish benchmark charts, median lift percentages or logo case studies, arguing those are easy to print and impossible to verify. Instead it shares account figures described by sector and size, with no publisher named, matching the confidentiality extended to new clients.
How It Works
The onboarding path starts with a domain. A publisher submits a site address through a short form, creates an account with a name, email and password, and waits for human review. Nothing serves until the review is approved, and the company states that applicants hear back either way, including what it would change and what it would leave alone.
After approval, the publisher places the single Dokira tag on the site. From that point the operational burden shifts to the network. Configuration, adapter maintenance, partner troubleshooting and bid optimization are handled internally by the assigned contact.
At runtime a page load creates an ad opportunity. The Dokira tag starts an auction, the request reaches buyers across both Prebid and OpenRTB routes, eligible bids compete, and the winning creative renders in the slot. Dokira notes that specific demand routes and auction rules depend on how each individual site is configured, so the public flow illustration is presented as representative rather than universal. Payment follows a revenue-share arrangement, with no fixed fee preceding monetization.
Use Cases
An independent content site without ad ops staff. A publication generating steady traffic but lacking a dedicated ad operations hire can hand the revenue side to Dokira and keep editorial focus intact. The single tag removes the need to maintain a vendor list or babysit a header bidding stack.
A publisher already running header bidding but underperforming. Sites that deployed Prebid themselves and never tuned it often carry stale adapters or mismatched timeouts. Dokira's pitch is that a person reconfigures the existing setup based on observed traffic instead of applying a default template.
A site with existing direct-sold campaigns. Because Dokira imposes no exclusivity, a publisher with sponsor packages or direct advertiser relationships can layer programmatic demand underneath without renegotiating those deals.
A site that wants geographic demand diversity. The homepage demonstration shows one impression drawing different winning bids across five regions, which speaks to publishers whose audience is spread across markets rather than concentrated in a single country.
A publisher evaluating vendors skeptically. Teams that distrust published lift statistics can request anonymised account data from comparable sites and judge the numbers against their own analytics before committing.
Who It's For
Dokira suits small and mid-sized independent publishers, content sites and niche media brands that want managed programmatic revenue without building an ad operations function. It is a poor fit for publishers who insist on operating their own bidding configuration or who need granular self-serve controls and publicly listed revenue-share tiers before applying. Compared with large ad management networks, Dokira leans on the absence of exclusivity and the absence of a setup fee as its structural differences, while conceding that performance proof is only available through a direct conversation rather than a public case study library.
Pros & Cons
The Good
- A single tag consolidates Google AdX and 17 additional bidding partners, eliminating the need to maintain an in-house header bidding stack.
- A named human contact configures and tunes each site based on observed traffic patterns instead of applying one template across the network.
- No exclusivity clause allows publishers to keep direct-sold deals and existing monetization partners running alongside Dokira.
- No setup fee and revenue-share pricing mean costs only scale with revenue actually generated.
- The company declines to publish invented benchmarks and instead shares anonymised account data from sites it operates.
The Bad
- Revenue share percentages and earnings terms are not published, so publishers must complete an application before learning the economics.
- Configuration is deliberately handled internally, which limits self-serve control for publishers who want direct access to bidding settings.
- Performance evidence is available only on request as anonymised figures, making independent pre-signup comparison against rival networks difficult.