- Why is my app not marked as live yet?
- Why can't I see live ads?
- Do you comply with Google and Apple developer policies?
- What type of ad units are available?
- What ad sizes do you support?
- What permissions will my app need in order to integrate Glispa Connect?
- What’s your SDK size?
- What’s the network usage for an ad?
- Are the video ads on auto play?
- Can I switch the video ads on and off?
- What platforms do you support?
- What are the minimum requirements of configuring a native ad for the different ad networks?
- What if I’m not happy?
Why is my app not marked as live yet?
Our algorithm is constantly running and monitors the apps that are live in Google Play and in the Apple Store. In order for your app to be marked as “live” in the dashboard, you need to reach the threshold of 100 ad requests per day.
In the meantime, if your app is working fine in the Google Play/ Apple Store, then you have nothing to worry about. Ad requests are served, impressions are counted respectively and you are still making revenue.
Why can't I see live ads?
Our advertising partners require for new publishers to reach a minimum threshold of ad requests per day before they start bidding on their traffic. If you are testing from one device (yours) and you are making a low number of requests, our advertising partners will not be able to spot your app and start running their campaigns.
If you can receive ads while in Sandbox we advise you to disable Sandbox and then upload your app on the app store so that your users can start making requests to our servers and advertisers start evaluating your traffic. Finally, keep in mind that the vast majority of the advertisers are only sending ads on apps that are uploaded in Google Play and Apple Store. We strongly recommend that you upload your app in the respective app stores.
Do you comply with Google and Apple developer policies?
We are in full compliance with the latest developer policies both on Google Play and Apple Store. We consider this a serious matter and re-evaluate our ad unit’s compliance on every policy update.
What type of ad units are available?
With the Glispa Connect exchange SDK, you can create any type of ad since Native Ads are fully customizable. The most common implementations that are out-of-the-box ready are Stream and Interstitial ads.
We also support video ads on all the above implementations and on your customized ads.
What ad sizes do you support?
The Glispa Connect exchange supports the following ad formats:
- Banner (320×50, 728x90)
- Native (Custom size)
What permissions will my app need in order to integrate Glispa Connect?
Only INTERNET and ACCESS_NETWORK_PERMISSIONS are required.
What’s your SDK size?
Android Change Log can be found here
|Glispa Connect Light||~0.768 MB|
|Glispa Connect Exchange||~1.01 MB|
|Glispa Connect Full||~1.08 MB|
iOS Change Log can be found here
|Packages||Swift Size||Obj-C Size|
|Glispa Connect Light||~4.1 MB||~1.17 MB|
|Glispa Connect Exchange||~5.5 MB||~2.57 MB|
|Glispa Connect Full||~6.6 MB||~3.77MB|
*The SDK size can be changed depending on which third-party ad networks and which ad format you choose to integrate.
What’s the network usage for an ad?
~60KB for Native interstitial ads (Natural Pause). ~20KB for in-Stream ads. For video ads the network usage can vary, depending on the restrictions you want to set.
Are the video ads on auto play?
Yes, by default the video ads are on auto-play and muted. An impression is counted once the first frame of the video has been shown to the user.
Can I switch the video ads on and off?
Yes. You can turn the video ad capability on or off, whenever you want, from your dashboard settings.
What platforms do you support?
We offer Android and iOS SDKs.
What are the minimum requirements of configuring a native ad for the different ad networks?
Various ad networks have their own minimum requirements for a native ad unit. Note that if you include the following basic elements, you will be able to leverage the native ad unit and are safe from being disabled out of any ad network.
- ‘Call to Action’ button
- AdChoices logo OR anything that hints that this is an advert and not a part of the content. EX: ‘sponsored post’, ‘promoted post’, etc.
For your reference, here are the guidelines for individual networks:
- Facebook: https://developers.facebook.com/docs/audience-network/guidelines/native-ads
- Mopub: http://mopubcom.c.presscdn.com/wp-content/uploads/2014/04/MoPub_Native_Ads_Addendum.pdf, http://www.mopub.com/resources/docs/ad-formats-best-practices/native-ads-best-practices
- Applovin: https://support.applovin.com/support/solutions/articles/11000015457-ad-specs
- Admob: https://support.google.com/admob/answer/6329638?hl=en&ref_topic=6372357
- Glispa Connect Exchange: http://www.avocarrot.com/blog/mobile-native-ads-design-guidelines/
What if I’m not happy?
You can switch off any app from the dashboard at any time. We hope this will never happen but if for any reason your expectations have not been met, no code update will be needed to stop the service and the performance of your app will not be affected.