Routers allow publishers to distribute traffic across multiple demand sources. This is managed at the channel level, where the channel acts as a router and routes incoming traffic to one or more sources based on assigned weights.
Channel Configuration
When creating or editing a channel, you must:
-
Set the Channel Type to Traffic Router
-
Provide a Router tag, which is the endpoint that the publisher uses
Each router tag is linked to one or more sources. When a request comes through the router, ad server determines which source to route it to, based purely on weight-based distribution.
Source Setup Under a Router
Each source linked to the router must be configured individually:
-
Source Name and Description help identify the integration
-
Type of Integration: can be Tag-based, OpenRTB, or DOOH
-
Supply Type: Video or Audio
-
Pricing Type: Share of Revenue, Floor Price, Fixed CPM, or Dynamic Floor
-
Weight: determines the % share of traffic this source will receive from the router
Example: If two sources under the same router have weights 70 and 30, 70% of traffic will be routed to the first source, and 30% to the second.
Traffic Routing Logic
Currently, ad server uses only weight-based routing. It does not yet support logic-based routing such as:
-
Geo-based distribution
-
Device type routing
-
Dayparting or time-based logic
This makes setup straightforward but also limits dynamic distribution based on performance or targeting.
Reporting View
Once a router is active and receiving traffic:
-
You can view performance per source under the router
-
Metrics such as Router Requests, Fill Rate, Unmatched Traffic, Paid Impressions, eCPM, and Total Revenue are displayed
-
This view helps optimize source weights over time
Best Practices
-
Begin with even weights (e.g. 50/50) when testing two new demand sources
-
Monitor metrics after a few days and adjust weights based on performance
-
Keep a fallback tag with a small weight to capture any unmatched traffic