I am developing an application in react native one of the requirements of the application in showing an interstitial ad when starting the application before it loads any component, this due to the policies of admob google, otherwise it brings penalties in the ads.
I've been trying in several ways first to put a in componentDidMount and in the constructor the react-native-admob code for interstitial, however the ad likewise takes time to load causing the component (screen) to load completely , which should not be allowed until the ad loads and closes.
Should the ad be added natively (native code for android) or is there any other way to place that ad
It's not possible, because there are politics of Google Admob
you can read all the documentation
https://support.google.com/admob/answer/6066980?hl=es&ref_topic=2936214
https://support.google.com/admob/answer/6201362
Related
Is there a way to display the same banner ad throughout my Android application using different activities?
It's almost impossible, bro!
Your banner is controller by Ads Providers. Unless they provide customizing to configure ads like you said. As all providers I knew, there's none support that.
What is the difference between Admob Native Express and Native Advanced Ads?
Are there separate Ad ids for Native express or native advanced ads, i have seen that native advanced use 2 ids , one of Ad id and other is App id but express needs one
Native Express ads are similar to banners in that they're rectangular ads that you can drop into a layout and size how you like. The key difference is that you, the publisher, can control the ad's presentation details (things like image sizes, fonts, colors, and so on) by uploading a CSS template for your ad unit. AdMob will combine that template with advertiser assets like icons, images, and text, and display the result in a NativeExpressAdView. This approach minimizes the amount of Java code needed for Native Ads Express, while helping publishers display ads that look natural in their app.
Native Ads Advanced is a format in which ad assets are presented to users via UI components that are native to the platform. They're shown using the same types of views with which you're already building your layouts, and can be formatted to match the visual design of the user experience in which they live. In coding terms, this means that when a native ad loads, your app will receive a NativeAd object that contains its assets, and the app (rather than the SDK) is then responsible for displaying them.
There are two system-defined formats for native ads: app install and content. App install ads are represented by NativeAppInstallAd, and content ads are represented by NativeContentAd. These objects contain the assets for the native ad. You also have the option of defining your own custom native formats, in which case the ads are represented by NativeCustomTemplateAd.
Native Ads Advanced is a format in which ad assets are presented to users via UI components that are native to the platform. They're shown using the same types of views with which you're already building your layouts, and can be formatted to match the visual design of the user experience in which they live. In coding terms, this means that when a native ad loads, your app will receive a NativeAd object that contains its assets, and the app (rather than the SDK) is then responsible for displaying them. There are two system-defined formats for native ads: app install and content. App install ads are represented by NativeAppInstallAd, and content ads are represented by NativeContentAd. These objects contain the assets for the native ad.
Let's say I have integrated Mopub with Facebook Audience Network (FAN), Flurry, Inmobi. Now, I want to find out which network is actually serving the ads because maybe I want to serve Flurry's ads with a slightly different layout compared to FAN). How do I determine on my users side which ads he is seeing?
From the mopub docs : https://github.com/mopub/mopub-android-sdk/wiki/Native-Ads-Integration, it seems pretty linear in that we can only create one sort of layout for our native ads and we have to stick to that type of layout. What happens if for example, we want to serve videos ads from FAN and static image ads from Flurry?
They are two separate integrations effectively - Native and banner ads. Each has a different custom events (adapter) implementation and you will need to use that appropriately.
Since the Mopub sdk and the custom event implementations are both open source, you can modify them to put in appropriate checks (or logs) to determine the ad network source. It is likely that the ad response from Mopub will contain the serving network's name (I don't recall fully as it's been a time since I mucked around in their ad response0
I am using google native ad GoogleNativeAdsAddon-1.0.0.jar , native ad showing properly but click event on image and text not working. means it is not redirecting on any webpage . i also debug the code and find contentAd.performClick(NativeContentAd.ASSET_HEADLINE);
for headline not redirecting on any page . for testing i am using test id of native ad
The add-on jar for Google's native ad architecture is no longer necessary, and no longer works. Just use the latest version of the SDK (8.4.0 at the moment). It has all the resources necessary to show native ads from AdMob and DFP.
I have developed simple webview app for my website. App simply load url of my website with in webview. Is it ok to insert adview for admob ads in this type of app? Thanks in advance.
You can either embed the ad in your webpage or add an adview to your app layout. It's really up to your personal preference.
I suppose the big difference is that if you wanted to change the adview after you've published the app, you would have to release an update while if your ad was on the webpage you could just change it there.
You should also consider that if you have ads on the webpage for people viewing it through a browser, you probably don't want to have additional ads within the app itself (or maybe you do, I don't know), it all depends on how your users access this website.