APPLE REJECTION - Ask App Not to Track UNITY ADMOB
riken sonani
Specifically, we noticed the app accesses web content you own and collects cookies for tracking after the user asked you not to track them.
Next Steps
To resolve this issue, please revise the app so that you do not collect data for tracking purposes if the user does not give permission for tracking.
Alternatively, if you do not collect cookies for tracking purposes, revise the cookie prompts that appear in the app to clarify you do not track users.
Note that if the app behaves differently in different countries or regions, you should provide a way for App Review to review these variations in the app submission. Additionally, these differences should be documented in the Review Notes section of App Store Connect.
Resources
- Tracking is linking data collected from the app with third-party data for advertising purposes, or sharing the collected data with a data broker. Learn more about tracking.
- See Frequently Asked Questions about the requirements for apps that track users.
Mobile Ads SDK Forum Advisor
Hi,
Thank you for contacting the Mobile Ads SDK Support team.
It looks like you are utilizing ATT by using your own implementation. Please confirm.
If you are using Mobile Ads SDK, the ATT pop-up may appear through the SDK. The initial consent pop-up will be presented once agreed upon, subsequently followed by the appearance of the ATT pop-up. I would like to suggest the removal of custom ATT code and the utilization of the SDK-level ATT to mitigate any potential rejection by Apple.
If you have any questions or need assistance, kindly contact us.
Thanks,
 |
Mobile Ads SDK Team |
Carlos Marciano Gonzalez Benitez
Si necesito ayuda no funciona 😔
--
---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/nhjDQ000000000000000000000000000000000000000000000SGT7SS00BjqyxyW8Ra6DYBnHpjJgxg%40sfdc.net.
Mobile Ads SDK Forum Advisor
Hi Riken,
Thank you for getting back to us
I would suggest here to remove custom code of ATT and utilize SDK level ATT to avoid any rejection through Apple.
Make sure to update your Info.plist to add the NSUserTrackingUsageDescription key with a custom message describing your usage. For Ex:
<key>NSUserTrackingUsageDescription</key>
<string>This identifier will be used to deliver personalized ads to you.</string>
If you decide to include App Tracking Transparency(ATT) in your app, you can use the User Messaging Platform (UMP) SDK to trigger an IDFA explainer that gives users some context of why you're asking for this permission. Be aware that the usage of the UMP SDK affects all users of your app. If you aren't using the UMP SDK, the Request App Tracking Transparency authorization shows you how to implement the OS-level ATT authorization request manually. Also, refer to privacy strategies for iOS to decide whether Apple's ATT prompt is right for your app. You can also refer to unity.
Kindly get back to us in case you need any other help.
Mobile Ads SDK Forum Advisor
Hi Carlos,
Thank you for contacting the Mobile Ads SDK Support team.
We would like to inform you that this product officially supports only English. It would be best to reply in English if you can. If not, we will try to use Google Translate to support you as best as we can.
Please note that our support channel can only best assist you with regards to Google Mobile Ads SDK implementation and technical issues. Should you encounter any difficulties related to the Mobile Ads SDK, please provide a detailed description of your concern, and we will guide you accordingly.