Adjust stop sending events for users recognized as Authorized ATT users (US only)

[kientux]

Unity version: 2022.3.62f2
Adjust SDK version: v5.5.0

We're facing issue about logging play events from all of our games. We have several play events like PLAY_LEVEL_1, 2, ... Adjust tracked installs correctly, but somehow, for "Authorized ATT" users, Adjust stop sending further events for them.

• At first, we show ATT popup when the game starts. For users shown as "Authorized ATT", play events do not get logged.
• Then we changed to show ATT popup when user reached level 5. Still, for Authorized ATT users, play events do not get logged (even from level 1). However, we also use our custom tracking method, that pushes play event to our backend, and all these users are playing just fine.

Weird thing is this issue only happens with US users. All other countries are not affected.

From our custom tracking, these "Authorized ATT" users, some of them do not accept ATT request, but Adjust still group them into "Authorized". This might be some internal logic from Adjust side?

We tried several ways to fix this, from the begining we think it might be the issue from our code. But it does not explain why only US users are affected. We only recognize this issue from the start of November, because the number of Authorized ATT users is growing very fast since then (almost 0% in Sep, Oct; but 50% installs now).

Does Adjust team have any insight for this?

[uerceg]

Key @kientux,

Thank you for very detailed explanation. In this repo we are focused on potential SDK issues and when it comes to the SDK - it has no internal logic when it comes to events tracking to behave one way or another depending on status of your ATT consent. ATT consent is just a parameter whose value we send to our backend which then behaves in accordance to that value. Also our SDK is accessing no geolocation data, so the issue being US specific also doesn't sound like something that the SDK would cause on its own. It indeed sounds kinda odd that it's happening only in the US.

What I can advise you to check before forwarding this to the support team (or dedicated account manager in case you have one) is to set SDK to sandbox mode and log level to verbose and run the two tests that you described above - in one accepting ATT dialog and in another one declining it and check the SDK verbose logs when it comes to tracking of those specific events you're talking about. Are the events tracked fine in both scenarios or is it that you see difference in behavior as you described?