Less repeated integration work
Test additional demand through your connected TapMind layer before committing to a separate direct integration.
Test more demand without rebuilding your monetization stack.
Keep the mediation platform you already run. Add TapMind MetaMediation 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 MetaMediationAdded alongside, not in front
TapMind Marketplace demandYour own demand partners
- <35 KBAdapter size
- <100 MSLatency
- TransparentBidding
- Low-endDevice optimized
- PrivacyCompliant
What is TapMind MetaMediation?
TapMind MetaMediation 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 MetaMediationAdded 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.
Life Without TapMind
Interactive demoIncoming
Your next demand partner arrives here
New demand partnerArriving
New demand partnerArriving
+ SDK module for this partner
Your setup, unchanged in both scenes
Your app
Your mediationExisting demandExisting demand
One connection point, ready for an added layer
TapMind MetaMediationConnected once
Marketplace demandYour demand partnersOpenRTB · Header bidding · GAM
Integration work
- 1Integrate SDK
- 2QA and release
- 3Test performance
Not the right fit
Your decision
Test and measure
Your app, your mediation, and the demand already connected to it.This group stays exactly where it is through both scenes.
A new demand partner arrives.Without TapMind, evaluating it starts with engineering work.
Another partner. Another integration project.Performance is discovered after integration work.
The partner is routed through the connected TapMind layer.Your app and your existing mediation are untouched.
Another partner. The same connected setup.Test additional demand, then choose where it continues.
This partner continues through TapMind.It keeps running inside the layer you already connected.
This partner is no longer active through TapMind.Nothing else in your setup changes.
Choose a direct integration after evaluating performance.This illustrates the publisher's decision, not an automatic migration.
You control every demand decision.
- Partners to test
- Partner priority
- Traffic allocation
- Pause or remove
- Continue through TapMind
- Move to your mediation
Publisher outcomes with TapMind MetaMediation
Evaluate more demand partners, reduce repeated integration work, and use performance evidence to decide which relationships to grow.
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 MetaMediation 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 35KB, 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 MetaMediationCustom Adapter · OrCh 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.
OrCh SDK
A deeper orchestration path where TapMind participates in mediation logic and request routing, including refreshed and no-fill handling and round-robin logic.
GAM path
Connectivity through an existing Google Ad Manager workflow, with ID management and reporting handled from the TapMind backend.
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.
Marketplace connection
Where the architecture connects to it, TapMind Marketplace supply is reachable through the same relationship.
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
$90Publisher share
$10TapMind share
No revenue generated means no revenue share payable to TapMind. The example covers revenue generated through TapMind, not your entire monetization revenue.
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
Three ways to connect MetaMediation. 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 OrCh 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.
OrCh 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.
Your app
Google Ad ManagerThe workflow your team already operates
TapMind managed IDsSet up and reported from the TapMind backend
Marketplace demand
Your own partners
Demand reaches your GAM setup through IDs TapMind manages for you.
GAM path
Connectivity through your existing Google Ad Manager workflow using managed IDs.
- Where it fits
- Inside the GAM setup your team already operates, with ID management on the TapMind side.
- When to use it
- GAM is where your monetization is configured and you would rather not add an SDK path.
Frequently asked questions
You can stop a partner or the TapMind path without committing your existing monetization setup to an underperforming relationship.
Thanks. We have your stack.
The TapMind team can now review your current setup, goal and the right place to start.