Privacy Sandbox on Android
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
Privacy Sandbox on Android 引入了多项新技术，旨在更好地保护用户隐私，并为移动应用打造高效的个性化广告体验。Privacy Sandbox 包含可保护隐私的 API，每个 API 都需要 AdServices normal 权限，以便在不依赖跨应用标识符的情况下支持核心广告用例。
详细了解 Android 的 Privacy Sandbox 计划和 Ad Manager。
Topics API
Topics API 是 Privacy Sandbox 的一部分，旨在根据用户的应用使用情况来粗略推断设备上的兴趣信号。这些信号或“主题”是易于识别的类别，根据用户使用的应用推断得出。
应用和广告平台可以根据主题判断哪些广告与用户相关。
利用 Topics API，可针对用户兴趣投放广告 (IBA)，而无需跨移动应用跟踪各个用户。
Google 移动广告 SDK 22.4.0 会访问 Topics API，并默认声明以下权限：
<!-- Topics API permission. -->
<uses-permission android:name="android.permission.ACCESS_ADSERVICES_TOPICS" />
如果您想停止参与 Ad Manager 对 Android 的 Topics API 的测试，请参阅 Android 说明，了解如何阻止权限合并。
Attribution Reporting API（包含调试报告）
Attribution Reporting API 是 Privacy Sandbox 的一部分，旨在消除对跨多方用户标识符的依赖，更好地保护用户隐私，同时满足跨移动应用进行归因和转化衡量的各种关键应用场景。
Google 移动广告 SDK 22.4.0 会通过调试报告访问 Attribution Reporting API，并默认声明以下权限：
<!-- Attribution Reporting API (with debug reports) permissions. -->
<uses-permission android:name="android.permission.ACCESS_ADSERVICES_ATTRIBUTION" />
<uses-permission android:name="android.permission.ACCESS_ADSERVICES_AD_ID" />
如果您想在 Ad Manager 中退出面向 Android 的 Attribution Reporting API 测试，请参阅 Android 说明，了解如何阻止权限合并。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-08-31。
[null,null,["最后更新时间 (UTC)：2025-08-31。"],[[["\u003cp\u003eThe Privacy Sandbox on Android enhances user privacy while enabling personalized advertising in mobile apps, using Privacy-Preserving APIs requiring an Ad Services permission.\u003c/p\u003e\n"],["\u003cp\u003eThe Topics API infers user interests based on app usage, enabling interest-based advertising without cross-app user tracking.\u003c/p\u003e\n"],["\u003cp\u003eThe Attribution Reporting API provides improved privacy for attribution and conversion measurement by removing reliance on cross-party identifiers.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Mobile Ads SDK 22.4.0 integrates the Topics and Attribution Reporting APIs and declares necessary permissions by default, offering opt-out options for Ad Manager testing.\u003c/p\u003e\n"]]],[],null,["# Privacy Sandbox on Android\n\nThe [Privacy Sandbox on\nAndroid](//developer.android.com/design-for-safety/privacy-sandbox/introduction)\nintroduces new technologies to improve user privacy and enable effective,\npersonalized advertising experiences for mobile apps. The Privacy Sandbox\nincludes [Privacy-Preserving\nAPIs](//developer.android.com/design-for-safety/privacy-sandbox/introduction#privacy-preserving-apis),\neach of which requires an Ad Services `normal` permission in order to support\ncore advertising use cases without reliance on cross-app identifiers.\n\nLearn more about [Android's Privacy Sandbox initiative and\nAd Manager](https://support.google.com/admanager/answer/12270545).\n\nTopics API\n----------\n\nThe [Topics\nAPI](//developer.android.com/design-for-safety/privacy-sandbox/topics)\nis part of the Privacy Sandbox designed to infer coarse-grained interest signals\non-device based on a user's app usage. These signals or \"topics\" are\nrecognizable categories that are inferred based on the apps they used.\n\nApps and advertising platforms can use topics to decide what ads are relevant.\nTopics support interest-based advertising (IBA) use cases without requiring\ntracking of individual users across mobile apps.\n\n\nGoogle Mobile Ads SDK\n\n\n22.4.0 accesses the Topics API and declares\nthe following permission by default: \n\n \u003c!-- Topics API permission. --\u003e\n \u003cuses-permission android:name=\"android.permission.ACCESS_ADSERVICES_TOPICS\" /\u003e\n\nIf you want to opt out of Ad Manager testing of Android's Topics API,\nsee how to prevent the merging of permissions in\n[Android's instructions](//developer.android.com/design-for-safety/privacy-sandbox/setup-api-access#declare-adservices).\n\nAttribution Reporting API (with debug reports)\n----------------------------------------------\n\nThe [Attribution Reporting\nAPI](//developer.android.com/design-for-safety/privacy-sandbox/attribution)\nis part of the Privacy Sandbox and is designed to provide improved user privacy\nby removing reliance on cross-party user identifiers and to support key use\ncases for attribution and conversion measurement across mobile apps.\n\n\nGoogle Mobile Ads SDK\n\n22.4.0 accesses the Attribution Reporting API with\n[debugging reports](//developer.android.com/design-for-safety/privacy-sandbox/attribution#extended-debugging-reports) and declares the\nfollowing permissions by default: \n\n \u003c!-- Attribution Reporting API (with debug reports) permissions. --\u003e\n \u003cuses-permission android:name=\"android.permission.ACCESS_ADSERVICES_ATTRIBUTION\" /\u003e\n \u003cuses-permission android:name=\"android.permission.ACCESS_ADSERVICES_AD_ID\" /\u003e\n\nIf you want to opt out of Ad Manager testing of Android's Attribution\nReporting API, see how to prevent the merging of permissions in\n[Android's instructions](//developer.android.com/design-for-safety/privacy-sandbox/setup-api-access#declare-adservices)."]]
