AppSpike vs Manual Mediation

Replace your static waterfall with an on-device optimization layer that handles routing, pre-loading, and maintenance automatically.

Feature Comparison

The Core Problem with Manual Mediation

Manual mediation was the only option before modern mediation platforms existed. You integrate each ad network SDK individually, order them in a waterfall by expected eCPM, and hope that your static configuration captures the best price.

The problems are structural:

• Static ordering can't keep up. eCPMs shift constantly by geo, time of day, ad format, and user segment. Your waterfall is always out of date.
• You only call the next network if the previous one fails. Higher-paying demand sources lower in the waterfall never get a chance to bid.
• Every new network means more engineering work. Integrating, testing, and maintaining each SDK individually scales poorly.

AppSpike eliminates all of this. One integration gives you access to 29 demand sources competing in real time. The on-device optimization engine handles routing, floor prices, and timing automatically.

What Doesn't Change When You Switch

You keep every ad network you currently use.

• Your existing ad network accounts stay active
• Every network you've already integrated continues to serve
• You remove individual SDK integrations and replace with AppSpike + adapters
• Each network now competes in a real-time auction instead of a static waterfall

Where Manual Mediation Falls Short

1. Static Waterfalls Lose Money

A manually configured waterfall calls networks in a fixed order. If Network A is first but Network B would pay 3x more for this particular impression, you'll never know. AppSpike runs a real-time auction across all 29 demand sources for every impression — the highest bidder always wins.

2. No On-Device Intelligence

Manual mediation has no concept of when to show an ad, how often, or which format performs best for a given user. You configure placements statically and hope for the best. AppSpike's optimization engine analyzes real signals — session depth, engagement patterns, connection quality — to find the optimal ad timing, frequency, and format per session.

3. Engineering Time Sink

Each ad network requires its own SDK integration, configuration, and maintenance. When an SDK releases a breaking update, you fix it. When you want to add a new network, you integrate it from scratch. AppSpike is a single integration with adapters — adding a new demand source takes minutes, not days.

4. Fragmented Analytics

With manual mediation, each network has its own dashboard. Comparing performance across networks means exporting CSVs and building your own reports. AppSpike provides a single unified dashboard with cross-network revenue data, LTV analysis, and IAP & subscription revenue tracking.

5. No Pre-Loading

Manual integrations typically load ads when they're needed, adding latency and missing impressions when ads aren't ready in time. AppSpike's on-device model evaluates connection quality, session depth, and placement history to pre-fetch ads before they're needed — delivering fast load times without letting high-value bid tokens expire.

Revenue Impact

Publishers that switch from manual mediation to AppSpike typically see:

The lift comes from three places: real-time auction competition replacing static ordering, on-device optimization of ad timing and format, and pre-loading that eliminates missed impressions.

Migration Path

Switching from manual mediation to AppSpike simplifies your stack:

1. Add the AppSpike SDK and one adapter per ad network you currently use
2. Initialize with your App ID
3. Replace individual network load calls with AppSpike.loadInterstitialAd(), AppSpike.loadRewardedVideoAd(), etc.
4. Remove individual ad network SDK integrations (AppSpike adapters handle them)

The result: fewer SDKs, less maintenance, better revenue. See the full Android integration guide for step-by-step instructions.

When Manual Mediation Makes Sense

If you're only using a single ad network and your revenue needs are minimal, manual mediation (which is really just direct integration) is fine. There's no waterfall to manage and no optimization to miss.

For anyone using 2+ networks — which is most publishers — manual mediation is an unnecessary tax on engineering time and revenue. AppSpike automates everything manual mediation does, and adds on-device optimization that manual configuration simply can't replicate.

Bottom Line

Manual mediation is the hard way to do something AppSpike handles automatically. Replace your static waterfall with an on-device optimization layer that routes every impression to the highest bidder, pre-loads ads before they're needed, and requires zero ongoing maintenance.