Native Ad Format
Native ads provide individual ad components that you implement directly in your app’s layout, unlike other formats where the SDK provides the complete ad view. Advantages: Customize the layout to match your UI/UX and minimize visual disruption. Requirements: Include an ad indicator and maintain visual differentiation to prevent users from confusing ads with content.
Four Required Elements for Native AdsNative ads can be designed to complement the content and look of your app. However, the following four required elements must be included. These elements are necessary to clearly mark native ads as advertisements so that users don’t mistake them for content, and to ensure the minimum advertising effectiveness expected by advertisers.
- Ad attribution: You must clearly display ad attribution text such as “Ad”, “Advertisement”, or “Sponsored” (localized appropriately) in the ad area so users can clearly identify the content as advertising.
- AdChoices icon: The AdChoices overlay icon enables users to identify and control ads, typically displayed as an ’ⓘ’ icon. This icon is automatically added by the DARO SDK, so no separate implementation is required. It is placed in one of the four corners of the ad view (top-left, top-right, bottom-right, bottom-left), with bottom-right as the default. For Non-Reward apps using Manual Implementation(XML), you can pick the corner via
DaroNativeAdBinder.Builder.setAdChoicePlacement()(see the AdChoices placement section below). Please lay out your ad view so the selected corner is not overlapped or obscured by other UI elements. The icon’s appearance and behavior may vary depending on the ad source (demand). - Title: The ad title must be displayed.
- CTA (Call to action): A CTA button with text such as “Install”, “Open”, or “Download” must be included. The size and format of the button can be freely configured, and it can be replaced with a text field depending on the situation. Since the ad source (demand) provides the CTA text, there is no need to specify fixed wording.
Integrating Ads
- Xml
- Compose
1
Create adBinder
- Create an adBinder needed to render native ads.
- Manual implementation(xml)
- Use Template
2
Create adUnit
3
Create adView and add to view
4
Set adBinder on adView
5
Set listener
6
Load ad
AdChoices placement
- Use
DaroNativeAdBinder.Builder.setAdChoicePlacement()to control where the AdChoices icon is rendered. - If unset, it defaults to the bottom-right corner (
BOTTOM_RIGHT). - Supported values:
TOP_LEFT,TOP_RIGHT,BOTTOM_LEFT,BOTTOM_RIGHT.
For Reward apps, calling
setAdChoicePlacement() does not actually change the AdChoices icon position.Template
- The Daro SDK provides the following templates.





