Fire the render beacon, that is, call the attachToView API, when the user can see the ad unit is made viewable on the screen. Make ad request during app initialization or when the app returns to foreground.
Note: Do not call attachToView more than once for the same response. If you do, no impression beacon will be fired in case of SDK. Also, do not make ad requests when the app goes to the background as users will not return to the app, leading to low render rates.
Send the click beacon only for valid click actions. Actions like swipe, scroll, and so on are not valid actions.
Note: Do not send the click beacon if the render beacon has not been fired. If done, no click beacon will be fired. In other words, only call handleClick when attachToView succeeds.
Make an ad request again only when the reason for a No Ad Response (IMErrorCode) is either NETWORK_ERROR or NO_FILL or INTERNAL_ERROR. Implement retry counter/logic to ensure that the ad call does not go into an infinite loop. For example, you can implement a 30-60 seconds time delay or try requesting an ad from your other demand partners.
Place the native ad unit on pages frequently visited by your users. Ensure the ad unit is placed above the page fold so that it does not require too many scrolls/swipes to be discovered.
Note: Do not use small icons or text that is not clearly visible to the user. Also, avoid placing the ad unit far down on a scrollable page where users don’t often reach. Arrive at a recommended number of pages and do not place the ad beyond that page number. For example, if your users do not scroll beyond 6-8 pages, the eighth page must be the last page at which you place your ad.
De-duplication is implemented for native by InMobi.
Note: Do not implement de-duplication.
If, for whatever reason, you still want to implement de-duplication, then request your InMobi Partner Manager to help you with the right JSON response.
It is best to request for an ad while loading the app. If the ad is ready at the same time that the content is, it creates a uniform experience. If, however, the ad is inserted after the user sees their feed, it does not create for a good user experience.
By installing this SDK update, you agree that your Children Privacy Compliance setting remains accurate or that you will update that setting, whenever there is a change in your app's audience. You may update the app's Children Privacy Compliance settings at https://publisher.inmobi.com/my-inventory/app-and-placements.
Support Center
