1. In case FalconMediation is not used.
Provide a method to display the consent popup according to Google standards
Last updated
Provide a method to display the consent popup according to Google standards
Last updated
use Google Mobile Ads version 9.2.0
After importing, select Assets > Google Mobile Ads > Settings... and verify in the Google Mobile Ads Settings file to ensure that all information has been filled in correctly:
To reduce errors in the iOS build process and potential crashes when running the app, it's recommended to use the following versions for IronSource and Google Mobile Ads:
After completing the import, select Assets > Google Mobile Ads > Settings... to check again the Google Mobile Ads Settings file to ensure all information has been filled in:
Combining with ATT popup on iOS:
Google encourages the display of the consent popup before the ATT popup. Therefore, when you receive the returned consent value, call the code to display the ATT popup. Refer to the usage guide for more details.
Note: UMP-specific settings: This section is used to set the content for the ATT popup. However, it only takes effect when you allow Google CMP to manage the display of the ATT popup automatically. If you want to use this feature, you must inform the MO side to activate it. If you use this feature, the content of this field must not be left empty.
After completing the installation and settings, to use it, call the function: FalconUMP.ShowConsentForm(Action onSetIronSourceConsent, Action onInitializeAdmob, Action onShowPopupATT) right after launching the app. Then implement the actions onSetIronSourceConsent, onInitializeAdmob, onShowPopupATT to initialize Mediation, Admob and to show the ATT popup (only for iOS).
Note:
If you allow Google CMP to automatically manage the display of the ATT popup, there is no need to implement the onShowPopupATT action.
If you wish to manually manage the display of the ATT popup, you must read the data returned by Google CMP to decide whether or not to show the ATT popup afterwards. Incorrect handling may lead to your app being rejected during the review process on the App Store.
For example:
Some consent forms require allowing users to edit their agreement at any time. Therefore, you should create a button that allows users to show the consent form again when necessary (it's recommended to place this button in the settings popup if available).
The display of this button will depend on the value returned by FalconUMP.RequirePrivacyOptionsForm:
True: show the button
False: hide the button.
When clicking on the button: call the FalconUMP.ShowPrivacyOptionsForm(); function to show the consent form again.
