中文Start a Test

Product

Dynamic floors. Decisions informed by context.

Orivia adjusts ad price floors using request context. When the mediation platform limits direct floor control, Orivia selects an ad unit instead. Both methods serve the same goal: improving monetization within your existing mediation setup.

Start a Test See How It Works

Two delivery methods

Floors first. Ad unit selection when needed.

  • Primary method

    Dynamic floor optimization

    Orivia adjusts the ad price floor using request context before the mediation call.

  • Alternative delivery method

    Ad unit selection

    When the mediation platform limits direct floor control, Orivia selects an ad unit instead.

How it works

From request context to the mediation call.

How Orivia worksRequest signals, impressions, revenue and optional publisher-provided context flow into the Orivia ML engine, which sets a dynamic floor or, where floor control is limited, selects an ad unit before the mediation call.CONTEXTRequest signalsImpressionsRevenueOptional contextpublisher-providedOriviaML engineDynamicfloorAd unitselectionMediationHow Orivia worksRequest signals, impressions, revenue and optional publisher-provided context flow into the Orivia ML engine, which sets a dynamic floor or, where floor control is limited, selects an ad unit before the mediation call.CONTEXTRequestsignalsImpressionsRevenueOptionalcontextOriviaML engineDynamic floorAd unit selectionMediation
Conceptual workflow
Core inputs
Ad requests, impressions and revenue data. Click data is not currently required.
Optional context
Publishers may supply additional behavioral context.
A model for each title
Model selection reflects each title, genre and player journey.

Measurement

Your current setup provides the baseline.

Compare a control group using your current monetization configuration with a test group using Orivia. You control traffic allocation through dynamic configuration.

Control group

Your current monetization configuration

Test group

Your current setup with Orivia

You set the split through dynamic configuration.

Incremental ARPDAU is assessed across comparable segments:

  • Country
  • Format
  • Placement
  • Traffic quality
  • Time window

Key metrics

  • Incremental ARPDAU

    Average revenue per daily active user, test group against control.

  • Fill rate

    Monitored throughout the test.

  • Stability

    Monitored throughout the test.

Reliability

Built for production traffic.

  • Asynchronous optimization

    Optimization runs asynchronously, so ad requests keep moving.

  • Automatic fallback

    If Orivia times out, the SDK returns your configured default ad unit.

  • Publisher-controlled rollout

    Adjust the test allocation or disable Orivia through dynamic configuration.

How fallback works

Find the revenue already inside your traffic.

Start with one app and controlled traffic. Measure the results before expanding.

Start a Test