Is the gs:requestConsent (UMP) call working for anyone? No consent popup on device

DigiChainDigiChain Member, PRO Posts: 1,295

Hi all,

I’m back in GameSalad after a couple of years to update some Android games for the new Google Play requirements (using latest the RC), and I’ve found that the Google UMP consent popup isn’t appearing.

  • My games were last published about two years ago, using the “gs:requestConsent” Tweet Sheet behaviour at the start of the game, as per the RC 2023-12-20 notes.
  • AdMob shows almost all EEA/UK impressions from those live builds as Limited ads. For one game’s latest version, that was 1,014 Limited ads vs 8 unrestricted in the UK over 30 days. That fits no consent popup ever being shown to users.
  • A GDPR message is published in AdMob and assigned to the app.
  • I’ve now tested on a device (UK, clean install): neither a fresh build nor the old games I reinstalled show a popup.
  • In Creator (1.25.103) preview, the “Social Sharing is not supported in the creator...” message appears, so the action seems to fire.

So it looks like the consent call may never have worked in these builds, not that something has recently broken. Is the consent popup working for anyone else, on any build? Is this a known bug, or is there something extra I should be doing? @adent42 , any idea whether this needs looking at?

Thanks!

Comments

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,386

    I'll need to look into it, but I remember when testing that it was hard to get the consent call to reset for the same package id so that it shows again. I had to test by using a different package id.

  • DigiChainDigiChain Member, PRO Posts: 1,295

    Thanks for looking into it.

    The reset issue might explain my test devices, but not the live data: across the UK and EEA, over 95% of my live impressions are Limited ads (e.g. UK 1,014 vs 8 unrestricted, Spain 1,589 vs 78, Germany 893 vs 51, over 30 days), so first-time users don’t seem to see the popup either. I’ll retest with a different package ID and report back.

  • DigiChainDigiChain Member, PRO Posts: 1,295

    @adent42  Quick update: I tested the live versions on two phones that have never had the game installed (different Google accounts, UK), and neither shows a consent popup. Along with the AdMob data, that suggests the consent call isn’t working for first-time users either.

    Could you look at whether gs:requestConsent actually triggers UMP in the Android build?

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,386

    Can you DM a publish link? It looks like the issue is that it won't show unless you have ad networks enabled, but I assume you do.

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,386

    Also try a re-publish. I need to test it to, but we fixed a bunch of issues so that one might have been fixed inadvertantly (I don't think so, based on tracing the code, but it might be something I missed or me pushing something I thought was already out there)

  • DigiChainDigiChain Member, PRO Posts: 1,295
    edited November 3

    @adent42  - I've just republished and consent is now showing, so whatever you did seems to have fixed it. Thanks!

    However I now have a new issue when publishing to Google Play:

    Foreground service permissions

    Your app uses the FOREGROUND_SERVICE_DATA_SYNC permission. You can only use this permission if your app performs tasks noticeable to the user when they're not directly interacting with your app.


    I can't see anyway in which I can disable this permission - is this something you need to remove?

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,386

    I'll need to make some adjustments to fully fix for this but basically we include the gameproj as an asset pack and we turned of asset delivery. The engine doesn't use it for anything else. Ask for an exception like:

    "The build was configured to use asset delivery which is why this permission is pulled in. Can you allow this one through while our partner works on an updated build that doesn't require it."

  • DigiChainDigiChain Member, PRO Posts: 1,295

    Google are requesting a video showing how the foreground service permissions are used within the app as part of the submission process. Unfortunately I don't think I'll be granted an exception for its use.

    For now I'll hold off until you're able to remove it. Any ETA on when that might be? Thanks!

  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,386

    Try republishing, it should be removed now.

  • DigiChainDigiChain Member, PRO Posts: 1,295

    Thanks @adent42 - Seems to have done the trick!

  • blenser4blenser4 Member Posts: 7

    Glad to see this got sorted. The republish fixing the consent popup and the permission removal are both useful to know, since I have a couple of older Android games to update too. Thanks for sharing the follow up.

  • DigiChainDigiChain Member, PRO Posts: 1,295

    @adent42 - Thanks, the consent popup now appears, but there still seems to be an issue with the new build.

    AdMob is now showing around 80% of ad requests as Restricted Data Processing (RDP), including in countries where US state privacy laws don't apply. Before republishing, RDP accounted for just 0.08% of requests.

    Over the past few days, the republished app has generated around 5,100 requests, broken down as follows:

    • Restricted Data Processing: 4,085 (80%)
    • No Restrictions: 732 (14%)
    • Personalisation disabled: 218 (4%)
    • Limited ads: 74 (1.4%)

    By country (RDP vs No Restrictions):

    • Brazil: 898 vs 122
    • Mexico: 618 vs 99
    • Argentina: 316 vs 36
    • Russia: 105 vs 62
    • US: 242 vs 19 (the US accounts for only around 6% of my traffic)

    It's also happening in the UK and EEA, where almost all requests are restricted:

    • UK: 29 RDP, 12 Limited ads, 1 No Restrictions
    • Italy: 41 RDP, 4 Limited ads, 3 No Restrictions
    • Spain: 35 RDP, 12 Limited ads, 2 No Restrictions

    For comparison, a GameMaker app on the same AdMob account, with the same published privacy messages and receiving hundreds of daily downloads, shows no RDP at all over the past 30 days.

    The GDPR and US state privacy messages are both published and assigned to this app. 'Child directed' and 'AdMob Test Mode' are both switched off.

    This makes me suspect something specific to the GameSalad build or its UMP/ad request integration.

    Could you check the following?

    1. Does the build enable RDP (or set a US privacy string) by default, rather than only when UMP receives a relevant US state privacy signal?
    2. Is any debug geography or test-device configuration inadvertently being applied to release builds?
    3. After a user responds to the UMP form, is their consent status correctly applied to subsequent ad requests? For example, should consenting UK/EEA users generate requests classified as No Restrictions?


  • adent42adent42 Key Master, Head Chef, Executive Chef, Member, PRO Posts: 3,386

    Sorry, just saw, this, will look into it!

Sign In or Register to comment.