Integration Checklist

This comprehensive checklist is designed to help you systematically verify the integration of your application, ensuring a seamless and efficient ad SDK experience.

---

1. API Usage Verification

• When initializing your application, ensure the correct App Key and App ID are used, and verify that the aggregation unit IDs for each ad format match the dashboard configuration.
• After the SDK is initialized, all placements for each ad format should load and show as expected.

---

2. Ad Format Specific Checks

Rewarded Ads

• Properly initialize the MCRewardedAd instance and set the mediation unit id.
• Set all required ad-listener (MCRewardedAdListener).
• Properly call the ad loading function (loadAd).
• Check if the ad is ready before showing (isReady).
• Properly call the ad show function (showAd).
• It is recommended to invoke the loadAd funtion within all the following callbacks: onAdLoadFailed, onAdDisplayFailed, onAdHidden, onAdDisplayed.
• ❗Warning: Direct ad reload retries are prohibited in onAdLoadFailed; delayed operations must be implemented. Refer to the sample code for details.
• [Optional] Set ad revenue listener (setRevenueListener).
• Properly call the ad release function (destroy).

Interstitial Ads

• Properly initialize the MCInterstitialAd instance and set the mediation unit id.
• Set all required ad-listener (MCAdListener).
• Properly call the ad loading function (loadAd).
• Check if the ad is ready before showing (isReady).
• Properly call the ad show function (showAd).
• It is recommended to invoke the loadAd funtion within all the following callbacks: onAdLoadFailed, onAdDisplayFailed, onAdHidden, onAdDisplayed.
• ❗Warning: Direct ad reload retries are prohibited in onAdLoadFailed; delayed operations must be implemented. Refer to the sample code for details.
• [Optional] Set ad revenue listener (setRevenueListener).
• Properly call the ad release function (destroy).

App Open Ads

• Properly initialize the MCAppOpenAd instance and set the mediation unit id and SplashAdContainer.
• Set all required ad-listener (MCAppOpenAdListener).
• Properly call the ad loading function (loadAd).
• Check if the ad is ready before showing (isReady).
• Properly call the ad show function (showAd).
• Preload in the ad close callback(onAdDisplayFailed, onAdHidden).
• It is recommended to invoke the loadAd funtion within all the following callbacks: onAdDisplayFailed, onAdHidden.
• [Optional] Set ad revenue listener (setRevenueListener).
• Properly call the ad release function (destroy).

Banner Ads

• Properly initialize and configure the MCAdView instance and set the mediation unit id and BannerViewContainer.
• Set all required ad-listener (MCAdViewAdListener).
• Set the correct banner size (setLoadExtraParameter).
• Properly call the ad loading function (loadAd).
• Maintain container visibility for proper ad rendering.
• [Optional] Set ad revenue listener (setRevenueListener).
• Properly call the ad release function (destroy).
• Auto-refresh feature configuration: HyperBid Tools Dashboard > Application > Edit Mediation Unit > Advanced Settings

Native Ads

• Properly initialize the MCNativeAdLoader instance and set the mediation unit id and NativeAdViewContainer.
• Set all required ad-listener (MCNativeAdListener).
• Properly call the ad loading function (loadAd).
• For self-rendering, set MCNativeAdView correctly via createNativeAdView.
• For template rendering, handle the show logic properly (NativeAdViewContainer.addView(MCNativeAdView)).
• It is recommended to invoke the loadAd funtion within all the following callbacks: onAdDisplayFailed, onAdHidden.
• ❗Warning: Direct ad reload retries are prohibited in onAdLoadFailed; delayed operations must be implemented. Refer to the sample code for details.
• [Optional] Set ad revenue listener (setRevenueListener).
• Properly call the ad release function (destroy).

---

3. General Checks

• Using mediation debuggers to check ad integration (showMediationDebugger).
• Enable MCSDK log debug mode (MCSDK.setLogDebug(true)).

---

4. Compliance Verification

• The app-ads.txt file has been correctly uploaded.

---

5. Revenue Tracking

• For more details, please refer to Sample Code.

---