AD SON is a monetization wrapper that connects app developers to multiple ad networks through a single integration. It simplifies demand management by automatically routing requests to the highest paying sources.
Designed for both iOS and Android, AD SON helps publishers optimize fill rates, eCPM, and latency while maintaining control over ad formats and user experience. The following sections detail how it works, where it fits, and how teams can implement it effectively.
How AD SON Works Under The Hood
AD SON acts as an intermediary layer between your app and external ad networks. It handles request batching, format normalization, and latency optimization behind the scenes.
Core Responsibilities
- Unified SDK integration with multiple partners
- Real time bid routing and waterfall optimization
- Failover logic to prevent empty ad slots
- Reporting and analytics aggregation
| Component | Role | Impact on Revenue | Impact on Performance |
|---|---|---|---|
| Bid Router | Evaluates competing demand sources | Higher eCPM through auction style logic | Minimal latency added |
| Format Adapter | Converts network specific tags to standard sizes | Enables mixed ad types in same zone | Reduces integration time |
| Failover Manager | Switches to backup network on miss | Improves fill rate and stable revenue | Prevents layout jumps and blank screens |
| Dashboard Analytics | Shows line item performance in real time | Identifies top paying campaigns | Lightweight SDK reporting, low overhead |
Supported Ad Formats And Placement
AD SON supports a wide range of native, banner, interstitial, and rewarded formats. Flexible placement zones allow you to test different layouts without code changes.
Key Format Types
- Native ads with customizable templates
- Auto refreshing banner ads
- Full screen interstitial campaigns
- Rewarded video with user opted in flow
Implementation And SDK Setup
Integration typically involves adding a single SDK and initializing with your network credentials. From there, you define zones and let AD SON manage the underlying demand chain.
Typical Initialization Steps
- Download the latest AD SON SDK
- Add the dependency to your build configuration
- Initialize the client with your publisher key
- Define ad zones and map creative sizes
- Enable test mode and verify live metrics
Optimization Strategies For Publishers
To extract maximum value, you need to combine platform automation with manual rule based tweaks. Focus on format layout, floor pricing, and geographic segmentation.
Proven Optimization Levers
- Set per zone eCPM floors based on historical data
- Prioritize high fill networks for lower latency zones
- Run A tests on native templates and color schemes
- Exclude low quality demand during peak app usage
Best Practices And Next Steps
- Start with test mode and validate all formats before going live
- Monitor latency metrics and adjust waterfall timeouts accordingly
- Use A B testing to compare native versus interstitial performance
- Review weekly reports to refine floor prices and block low quality demand
- Keep SDK updated to benefit from new routing algorithms and security patches
FAQ
Reader questions
Does AD SON support mediation with my existing ad networks?
Yes, it is designed to work alongside your current partners and can coexist with server side or client side mediation stacks.
How frequently are eCPM reports updated in the dashboard?
Reports are refreshed in near real time, with detailed breakdowns available at hourly intervals for most campaigns.
Can I apply different floor prices for specific countries or user segments?
Absolutely, you can set geo specific and segment specific rules directly from the dashboard without releasing a new app version.
What happens if the primary ad network fails to respond?
The failover manager automatically switches to the next eligible network to keep impressions flowing and protect your revenue.