You just started working with a few rewarded ad networks that have strong demand in some of your Android apps’ key user geographies of Japan and South Korea. You want to use these ad networks in rewarded ad units across a few of your apps.

Let’s create a yield group that includes these higher-paying ad networks to monetize ad requests from Japan and South Korea on your rewarded ad units.

Part 1:

Let’s take a look at the first few fields you’ll need to populate for this new yield group.

Since this yield group will target rewarded inventory, you should select Rewarded as the ad format. You should also select Mobile app as the inventory type this yield group will target.

Which name is best for the yield group?

(A) Android Rewarded Japan/South Korea

(B) Yield Group Premium Demand

Explanation for Part 1

A descriptive name for your yield group can help with reporting. “Android Rewarded Japan/South Korea” identifies the platform, ad format, and additional geographic targeting associated with this yield group for mediation.

Part 2:

Next, you’ll need to select the targeting.

Given what you know about where this yield group should be eligible, which four targeting types should you modify?

(A) Inventory

(B) Device category

(C) Device manufacturer

(D) Operating system

(E) Geography

(F) Mobile application

(G) Custom targeting

Explanation for Part 2

As this yield group is meant to apply to rewarded ad units across multiple Android apps for users in Japan and South Korea, the following targeting options allow you to limit this yield group’s eligibility to that inventory:

Inventory: Select the relevant rewarded ad units

Operating system: Select “Android” to target requests from Android devices

Geography: Select “Japan” and “South Korea” to limit this yield group’s eligibility to requests from the two countries

Mobile application: Target the specific Android mobile apps

Part 3:

Next, you’ll need to add the first yield partner. The first few fields for this task have already been completed for you:

  • Name of new yield partner
  • Mobile SDK mediation as the integration type
  • Android as the platform 
  • Inactive for the status for the time being 
  • 2.00 as the default CPM

As this network supports automatic data collection, we’ve already enabled this feature in the Ad Manager company settings for this yield partner.

True or false? You should leave the option to override dynamic CPM unselected.

(A) True

(B) False

Explanation for Part 3

If you’ve enabled automatic data collection in the Ad Manager company settings, the default CPM value isn’t used, so you should leave the override dynamic CPM option unselected.

Conclusion

This question is a part of the Check your Knowledge section of the “Set Up Ad Manager Mediation” lesson from the “Configure Mobile In-App Ads Using Ad Manager” unit which is part of the Drive Advertising Revenue with Google Ad Manager course.

Leave a Comment

Share via
Copy link
Powered by Social Snap