Android 版 Privacy Sandbox
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
Android 版 Privacy Sandbox 導入新技術，除了可強化使用者隱私，還能更有效率地在行動應用程式中提供個人化廣告體驗。Privacy Sandbox 包含隱私權保護 API，每個 API 都需有廣告服務 normal 權限，才能支援核心廣告用途，且不需仰賴跨應用程式 ID。
進一步瞭解 Android 版 Privacy Sandbox 計畫和 AdMob。
Topics API
Topics API 是 Privacy Sandbox 的一部分，會根據使用者的應用程式使用情形，在裝置上推斷出概略的興趣信號。這些信號或「主題」是根據使用者所使用的應用程式，推斷出的可辨識類別。
應用程式和廣告平台可以根據主題，判斷哪些廣告符合使用者需求。主題不必跨行動應用程式追蹤個別使用者，就能按照使用者興趣顯示相關廣告。
Google Mobile Ads SDK 22.4.0 會存取 Topics API，且預設會宣告下列權限：
<!-- Topics API permission. -->
<uses-permission android:name="android.permission.ACCESS_ADSERVICES_TOPICS" />
如果不希望參與 AdMob 的 Android 版 Topics API 測試，請參閱 Android 版操作說明，瞭解如何避免權限合併。
Attribution Reporting API (含偵錯報表)
Attribution Reporting API 是 Privacy Sandbox 的一部分，由於不需仰賴多方使用者 ID，因此能進一步保障使用者隱私，並支援跨行動應用程式的歸因與轉換評估等重要用途。
Google Mobile Ads 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" />
如果不希望參與 AdMob 的 Android 版 Attribution Reporting API 測試，請參閱 Android 版操作說明，瞭解如何避免權限合併。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-31 (世界標準時間)。
[null,null,["上次更新時間：2025-08-31 (世界標準時間)。"],[[["\u003cp\u003eThe Privacy Sandbox on Android enhances user privacy while enabling personalized advertising in mobile apps, using new technologies like the Topics and Attribution Reporting APIs.\u003c/p\u003e\n"],["\u003cp\u003eThe Topics API infers user interests based on app usage to deliver relevant ads without cross-app tracking, requiring the \u003ccode\u003eACCESS_ADSERVICES_TOPICS\u003c/code\u003e permission.\u003c/p\u003e\n"],["\u003cp\u003eThe Attribution Reporting API provides improved privacy for attribution and conversion measurement, utilizing the \u003ccode\u003eACCESS_ADSERVICES_ATTRIBUTION\u003c/code\u003e and \u003ccode\u003eACCESS_ADSERVICES_AD_ID\u003c/code\u003e permissions for debugging reports.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can opt out of AdMob's testing of these APIs by managing permissions as outlined in Android's instructions.\u003c/p\u003e\n"]]],["The Privacy Sandbox on Android introduces new technologies to enhance user privacy and enable personalized advertising. It includes Privacy-Preserving APIs, such as the Topics API, which infers user interests from app usage, and the Attribution Reporting API for conversion measurement. Both APIs require Ad Services permissions. The Google Mobile Ads SDK 22.4.0 utilizes these APIs and declares default permissions. Users can opt out of AdMob's testing of these APIs by preventing the merging of permissions, per Android's instructions.\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\nAdMob](//support.google.com/admob/answer/13635519).\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 AdMob 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 AdMob 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)."]]
