Standard in-content
Sits in the article flow where attention already is.
Rikaavi
Smarter demand, placements, and fill — one platform for display and video today, built to expand.
Display & video monetization for publishers — mediation, fill, and Core Web Vitals in one stack.
Built for news, media, blogs, and high-traffic publisher sites ready to grow revenue.
Manage ad demand, optimize placements, improve fill rates, and grow revenue from the traffic you already have — starting with display and video.
A built-in waterfall backfills unsold inventory — including video no-fill handing off to display.
Configuration-driven renderers you can place, size, and tune per domain — no redeploy to change a unit.
Instream, outstream, and bumper modes with IMA / VAST, OMID, and autoplay that respects the browser.
On-demand SDKs, lazy slots, and edge-delivered config so monetization stays off the critical path.
Consent and regional rules resolve first; killswitch, bot guards, and friendly iframes keep you safe.
Consent-aware analytics, request tracking, first-party pixels, and Core Web Vitals alongside fill.
We help mid-size and growing publishers improve fill, placements, and demand — so advertising revenue goes up without a traffic project.
When primary demand doesn't fill, Rikaavi steps through your configured fallback sources — house and direct campaigns, additional networks, and custom demand — using round-robin or size-based selection.
Configuration-driven renderers you can place, size, and tune per domain — no code changes to move a unit or turn one off.
Sits in the article flow where attention already is.
Pins to the viewport edge as readers scroll.
Rides the rail beside long-form content.
Expands in-flow for high-impact moments.
Layers on media without breaking the layout.
Full-page pause between navigation beats.
High-visibility takeover with a lighter footprint.
Value exchange — view to unlock.
Multiple creatives in one placement.
Instream, outstream, and bumper modes, multiple playback engines, and native HLS — with autoplay that adapts to what the browser will actually allow.
Revenue shouldn't cost you page experience. Rikaavi is built to stay light on the critical path — with instrumentation wired in from the start.
Player engines, the IMA SDK, and other heavy libraries load only when a page actually needs them — not on every pageview.
Slots initialize as they approach the viewport, and the player starts when it's actually in view.
Per-domain configuration resolves at the edge, so the right setup is applied instantly and cached.
Consent-aware event reporting out of the box.
Primary and fallback attempts tracked per slot.
Slot-view tracking you own.
Page-experience reporting alongside monetization.
Consent handled as a first-class concern, and the operational controls to keep you safe in production.
Regional rules (EEA/UK and beyond) and CMP/TCF signals are resolved before ads or analytics run — and the whole stack honors the result.
Environment guards, bot-traffic detection, and a global killswitch protect your revenue and your reputation. Display units can run in isolated friendly iframes to limit blast radius.
Set your formats, demand sources, and rules once, per domain.
A single lightweight tag resolves the right config instantly and loads only what each page needs.
Mediation keeps slots full while built-in analytics report fill, latency, and page-experience impact.
From first setup to scale, we’re here to help you get measurable revenue uplift from Rikaavi.
A single point of contact to tune your setup, demand waterfall, and rollout.
Consent and regional rules resolve before ads or analytics run — and the stack honors the result.
Edge config, A/B variants, and an emergency killswitch so you stay in control in production.
Environment guards, bot-traffic detection, and isolated friendly iframes limit blast radius.
No. Rikaavi focuses on demand, placements, and fill so you can earn more from the visitors you already have.
No — both run from one Rikaavi stack with shared configuration and mediation.
Rikaavi loads heavy dependencies only when needed and lazy-loads slots. Performance is a design constraint, not an afterthought.
Consent and regional rules are resolved before ads or analytics run, and the whole stack honors the result.
Yes. Configuration is delivered from the edge and applied at runtime, including A/B variants and an emergency killswitch.
The mediation waterfall backfills across your demand sources, and video no-fill can fall back to display — so the impression still monetizes.
See how Rikaavi improves fill, placements, and demand — without asking you to buy more visitors.