Without TapMind
Every new partner starts as an engineering project.
Your app
Your mediation
New demand partnerNeeds its own SDK
- 1Integrate SDK
- 2QA and release
- 3Test performance
Engineering work first. Evidence later.
TapMind OpenMediation Your Mediation, Your Demand, Your Control.
Keep the mediation platform you already run. Add TapMind OpenMediation as a separate demand path to test, measure and manage new partners—without adding a new SDK or integration to your stack for each one.
Your app
Your current mediationAppLovin MAX · AdMob · Unity · GAMUnchanged
Existing direct demandStays connected to your mediation
PartnerPartner
TapMind OpenMediationAdded alongside, not in front
TapMind Marketplace demandYour own demand partners
Your app runs through your current mediation platform, which is unchanged. Existing demand keeps running. TapMind OpenMediation is added alongside it as a second path, reaching additional demand partners and demand the publisher brings themselves.
- <40 KB Adapter size
- <100 MS Response Time
- Transparent Bidding
- Low-end Device optimized
- Privacy Compliant
What is TapMind OpenMediation?
TapMind OpenMediation extends your existing mediation setup so you can test additional demand without rebuilding your stack for every new partner. Access TapMind Marketplace demand and bring your own demand partners into the same testing layer.
You choose the partners to test, review their performance, and decide where they continue.
Your app
Your existing mediationStays exactly as it is
Existing direct demandUnchanged
Connected straight to your mediation.
TapMind OpenMediationAdded testing layer
TapMind Marketplace demandReached through the same connection
Your own demand partnersBrought in over these routes
OpenRTBHeader BiddingGAM
- Your mediation staysNo migration, no replacement, no change to existing demand.
- One integration, many partnersConnect TapMind once instead of building an adapter per partner.
- Your partners, your routesBring demand you already know over OpenRTB, Header Bidding or GAM.
Life without TapMind. Life with TapMind.
See what changes when your next demand partner arrives.
A new demand partner arrives. Here is what happens next.
With TapMind OpenMediation
The same partner runs through a layer you connected once.
Your app
Your mediation
TapMind OpenMediationConnected once
New demand partnerRouted through TapMind
Marketplace demandTapMind Marketplace demand through the same connectionYour demand partnersOpenRTB · Header bidding · GAM
You decide what happens next.
Keep through TapMindPause or removeMove to your mediation
Evidence first. Commitment after.
Your app and your existing mediation are unchanged in both cases. TapMind sits beside them, it does not replace them.
Publisher outcomes with TapMind OpenMediation
Evaluate more demand partners, reduce repeated integration work, and use performance evidence to decide which relationships to grow.
Less repeated integration work
Test additional demand through your connected TapMind layer before committing to a separate direct integration.
More demand partners to evaluate
Bring your own partners alongside TapMind Marketplace demand and compare their contribution.
Potential eCPM improvement
Identify demand partners that improve the value of your available impressions.
Potential ARPDAU improvement
Evaluate how additional demand contributes to ad revenue per daily active user.
More scope to negotiate integration bonuses
Discuss integration bonuses directly with demand partners as part of your commercial agreement.
How TapMind OpenMediation is built
Your inventory and existing mediation, the TapMind layer added to it, the demand it reaches, and where reporting and control sit.
- Additive, not replacingThe layer attaches to your existing mediation rather than sitting in front of it.
- One connection, many partnersDemand is added behind the layer instead of in your app.
- Built to stay lightUnder 40KB, under 100ms, and running on low-end devices.
- Control returns to the publisherPriority, traffic and partner status are yours to set.
Request path
01
Your app or siteInventory you already monetize
02
Your existing mediationExisting direct demand stays where it is
03
TapMind OpenMediationCustom Adapter · Orchestration SDK · GAM
04
Demand connections and routingMarketplace demand and the partners you add yourself
BiddingPartners compete on price per request
WaterfallPartners called in the order you set
Both setups are supported, and they can run alongside each other.
TapMind Marketplace demandYour own demand partners
05
Reporting and publisher controlPerformance, partner status, priority and traffic
Custom Adapter
TapMind is registered as a demand path inside supported mediation environments, so the layer activates without a permanent integration per partner.
Orchestration SDK
A deeper orchestration path where TapMind participates in mediation logic and request routing, including refreshed and no-fill handling and round-robin logic.
Bidding and waterfall
Demand is supported across bidding and waterfall-style partner setups where the selected integration path allows it.
Publisher-added demand
Third-party partners you already have relationships with can be brought into the same layer.
Payment model
No setup fee, no monthly commitment, and no separate ad-serving fee. TapMind's revenue share applies to revenue generated through its platform.
Illustrative revenue split
$100
Revenue generated through TapMind OpenMediation platform
$90Publisher share
$10TapMind share
No revenue generated means no revenue share payable to TapMind. The example covers revenue generated through three types of buyers.
| Buyer type | Revenue share |
|---|---|
| TapMind Marketplace Demand | X% |
| TapMind Contracted Platform Buyers | 90/10 Revshare |
| Publisher Contracted Platform Buyers | 90/10 Revshare |
What you pay
10% revenue share
TapMind receives 10% of revenue generated through the platform. The publisher keeps 90%.
What you do not pay
- Setup feeNone
- Fixed monthly platform feeNone
- Separate ad-serving feeNone
No lock-inA commercial condition, not a fee.
Additional demand creates an opportunity for incremental revenue. The split above explains how revenue generated through TapMind is shared.
Integration paths
Two ways to connect OpenMediation. The right one depends on your existing stack and how deeply TapMind needs to participate in mediation.
Your app
Your existing mediationPartners already configured there
TapMind Custom AdapterRegistered as one more demand path
Marketplace demand
Your own partners
The adapter is configured inside the mediation platform you already run.
Custom Adapter
TapMind registered as a demand path inside your existing mediation platform.
- Where it fits
- Inside your current mediation setup, alongside the partners already configured there.
- When to use it
- You want to start testing additional demand with the least change to your stack.
Your app
TapMind Orchestration SDKRequest routing, refreshed and no-fill handling, round robin
Your existing mediation
Demand through TapMind
The SDK sits between your app and demand, taking part in mediation decisions.
Orchestration SDK
An Orchestration SDK where TapMind takes a more active role in mediation logic and request routing.
- Where it fits
- Between your app and demand, handling refreshed and no-fill requests and round-robin logic.
- When to use it
- You need TapMind to participate in mediation decisions, not sit as one more demand line.
Frequently asked questions
OpenMediation adds another demand path alongside the mediation setup you already run, letting you connect, test, and manage additional demand without replacing your existing mediation or the partners already connected to it.
Request received
Thanks. We have your stack.
The TapMind team can now review your current setup, goal and the right place to start.
What happens next?We’ll follow up using the work email you provided.