How does the SDK integration process work, and how long does it take?
Integration is a lightweight, 3-step process: (1) add the SDK with a single line of code, (2) paste the Google Ad Manager identifier and ad placement (tag) ID provided by our Sales Team, (3) add the app-ads.txt entries provided by your business representative. A 4th step covers TCF consent collection. WPartner describes this as requiring minimal developer time.
Is the SDK compatible with existing advertising solutions, and can it run alongside other tools?
Yes. Everything runs on a Real-Time Bidding (RTB) model, and the SDK operates as a mediation/waterfall layer managing multiple demand sources, including Google — so it's built to sit alongside your existing ad stack rather than replace it.
How frequent are SDK updates, and do they require developer action?
Most of what powers the SDK lives on the backend — so the SDK itself doesn't require frequent updates on the developer's side.
Is the SDK GDPR compliant, and how does it handle user consent?
Yes — WPartner for Apps (SDK) is GDPR-compliant, with a consent flow that follows the IAB TCF standard. The SDK displays a CMP screen, collects user consent and sends the consent string with user permissions. If your app doesn't already have a CMP, you can use a market solution (e.g. OneTrust, ConsentManager) or the CMP built into WPartner's Google Ad Manager setup.
What user data does the SDK collect, and is it shared with third parties?
The exact data points are agreed and confirmed with each client individually. Some data — such as the IFA (Identifier for Advertisers) — is required for accurate ad targeting. As part of the Real-Time Bidding process, that data is shared with demand partners bidding on the impression; the exact scope shared is likewise agreed with each client.
What are the payment, settlement and payout terms?
Settlement runs on a monthly cycle through a dedicated programmatic panel where all statistics and turnover are visible, and payouts follow that same monthly cycle. The revenue-share model is standard across clients, though the exact split can vary by app.
What ad formats are available besides banner and interstitial?
Rewarded Video, Native and Sticky Banner formats are also supported, alongside standard Banner and Interstitial units. Rich Media placements are available too.
Can you control the frequency and placement of ads?
Yes — you retain full control over placements, frequency and visibility, and you can also block specific publishers and specific competitors from showing ads in your app.
What does technical support look like?
Dedicated support is included. Our team actively manages your account to keep monetisation as efficient and effective as possible, from onboarding through ongoing optimisation.
What are the main advantages over AdMob and other networks?
In head-to-head A/B tests on production traffic (minimum 14 days, ≥1 million impressions), WPartner for Apps delivered up to 2x higher eCPM than the leading market solution. Beyond raw performance: you get access to Wirtualna Polska's own unique demand plus 100+ integrated DSPs, AI-driven auction management, and a dedicated partnership team — not just a self-serve dashboard.
How does the SDK perform on fill rate and eCPM compared to other networks?
Fill rate and eCPM benefit from tapping multiple inventory sources at once — WPartner queries Google's own ad space, its own network, and external networks together, which is designed to lift both fill rate and eCPM versus a single-source setup. Exact comparative figures vary by app.
What reporting, real-time management and testing tools are available?
All statistics and turnover are visible in a dedicated programmatic panel, updated on the monthly settlement cycle. Everything operates on a Real-Time Bidding (RTB) model, so every impression is auctioned and priced in real time, and A/B testing of different ad settings is available too.
