How to Integrate the User Messaging Platform (UMP) SDK Into Your Android Apps to Gather User Consent

[Music] welcome back to another Google admob developer tutorial my name is Justin mandulo and today I'm going to show you how to integrate the user messaging platform SDK or ump SDK into your app on Android the UMP SDK provides a collection of apis that you can use to gather consent from your users which helps you comply with privacy laws and regulations let's take a look at the ab mob user interface and see the Privacy message I have configured which the UMP SDK presents giving your users the ability to consent to how their data is used a complete integration of the UMP SDK includes the following key steps I'll walk you through each step with the demo Android Studio project first we'll import the SDK then request for consent information load and present a privacy message request ads I'll show you how to test your integration then we'll Implement a privacy options button and lastly I'll talk about how to optimize your integration so let's jump into a [Music] demo here I have a simple Android app and I'm in my build dog Gradle file in the app the first thing I'm going to do is jump across to the developer documentation under the install with Gradle section in the get started guide I'm going to copy this dependency and it's important when you're integrating choose the latest version which we include here and sync Gradle next step is to request for the most recent consent information navigate to your initial activity and create a consent information object that you're going to initialize in oncreate set consent consent information equal to user messaging platform. getc consent information and we can pass in a context now that it is initialized call request consent info update which requires inactivity and consent parameters so we will initialize one right here the method has a success listener and a failure listener for any air handling that's all you need to do to fetch the most up-to-date consent information next step is to load and show a consent form inside the success listener type user messaging platform. load and show consent form if required this method will do one of two things if consent is required for this user the SDK loads and shows a consent form The Listener is invoked when the form is dismissed or if consent is not required it's invoked immediately at this point you now have enough information to initialize the Google mobile ads SDK and start loading ads query consent information. can request ads as a layer of verification before making your request if it returns true you're good to go I'm recording this in New York so I won't see a gdpr consent form but what if I want to see how my app behaves for users in privacy regulated regions such as Europe This is possible with just a few lines of code create a debug settings object and configure the settings to include a geography add set debug geography and set the value to EA include the debug settings as part of your consent request parameter note that debug settings only work on enable test devices to enable a test device run the app and check the logs for consent debug settings all one word the log will include an ID that you can extract and include in your dbug settings by using ADD test device hashed ID like so now let's run our [Music] app and there we have a consent form now that we know how to show a consent form on app launch we now have to let users modify their consent choices in your app at any time this is commonly done by adding a button in your apps settings page if using an options menu regenerate the menu once load and show if required complete your button's visibility can then be determined by checking consent information. privacy options requirement status if the status is required the button should be visible when a user Taps on your menu item show the form using user messaging platform.sh show privacy options form there's a listener that is invoked upon user dismissal of the form or if there is an error now let's run our app again and our privacy settings button is now wired up lastly let's talk about optimization for loading ads your app will have already gathered consent from returning users SO waiting for request consent info updates listener can delay your ad impression you can optimize this by attempting to synchronously request ads just after calling request consent info update checking the can request ads API in two places ensures an optimal ad experience for new users and returning users because we're calling the same code in two places I am creating a helper function for readability as part of this optimization create an atomic Boolean to ensure you are only initializing the SDK and loading ads once during the consent Gathering process and there you have it to learn more check out the resources in the description below we have developer samples that go through a proper integration and the developer Forum where you can go and ask technical questions today we walk through how to gather consent in your mobile application by fetching consent information and loading a privacy message we then use that information to help us load ads and enable a privacy settings button we hope the video was helpful for you feel free to give it a thumbs up and leave a comment and remember to subscribe to admob for more technical content

Channel: Google AdMob

Views: 8,131

Keywords: admob, google admob, ump, Android, AdMob, GMA, Google, Mobile, Ads, UMP, User, Messaging, Platform, Privacy, Consent, Framework, Ad Manager, GDPR, EU, IAB, Tutorial, Integration, SDK, Developer, User Messaging Platform, Google Mobile Ads

Id: SysASyh9XKo

Length: 7min 9sec (429 seconds)

Published: Wed Dec 06 2023