Skip to content

FAQ

No. Keep your AdMob account and ad units; Qartvelo Ads uses them as the fallback for every request it cannot fill. AdMob revenue keeps going directly to you.

No network or disk work happens on your calling thread, loads are asynchronous, the Qartvelo Ads request has an 800 ms budget by default, and AdMob preloads in parallel. Start-up does not wait for the backend when a cached configuration exists.

Not yet. The React Native API is platform-neutral and rejects with unsupported_platform on iOS, so shared code keeps working. Use QartveloAds.isSupported() to hide ad UI on iOS.

No. It is public by design and is only accepted together with your registered package name. The SDK secret is the secret; never put it in an app.

Yes. Test mode works for pending apps and pending accounts.

Can I use one placement code for two banners?

Section titled “Can I use one placement code for two banners?”

Only one banner per placement code can be visible at a time. Create one placement per simultaneously visible banner.

Each Qartvelo Ads impression earns the campaign’s CPM bid / 1000 times your revenue share (70% by default), in GEL. See Reports and payouts.

No advertising ID, no device identifiers, no location, no personal data. See Privacy.

Section titled “Do I need a consent dialog for Qartvelo Ads?”

Qartvelo Ads ads are contextual and do not use personal data for personalization. Google’s AdMob, used as fallback, has its own consent requirements; collect consent with your CMP where required and pass the result with setPrivacy.

Can I use Qartvelo Ads with another network than AdMob?

Section titled “Can I use Qartvelo Ads with another network than AdMob?”

Yes, by implementing the fallback adapter interface.

Android 6.0 (API 23) and newer for native apps; React Native requires API 24.

github.com/Qartvelo-com/ads, MIT licensed. It includes a native sample app and a React Native example.