Untuk mendiskusikan dan memberikan masukan tentang produk kami, bergabunglah ke channel Discord Ad Manager resmi di server Komunitas Iklan dan Pengukuran Google.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Privacy Sandbox di
Android
memperkenalkan teknologi baru untuk meningkatkan privasi pengguna dan memungkinkan pengalaman iklan yang dipersonalisasi yang efektif untuk aplikasi seluler. Privacy Sandbox
mencakup API Perlindungan Privasi,
yang masing-masing memerlukan izin Layanan Iklan normal untuk mendukung
kasus penggunaan periklanan inti tanpa bergantung pada ID lintas aplikasi.
Topics
API
adalah bagian dari Privacy Sandbox yang dirancang untuk menyimpulkan sinyal minat secara terperinci
di perangkat berdasarkan penggunaan aplikasi pengguna. Sinyal atau "topik" ini adalah kategori yang dapat dikenali yang disimpulkan berdasarkan aplikasi yang digunakan.
Aplikasi dan platform iklan dapat menggunakan topik untuk memutuskan iklan mana yang relevan.
Topics mendukung kasus penggunaan iklan berbasis minat (IBA) tanpa memerlukan
pelacakan setiap pengguna di berbagai aplikasi seluler.
Google Mobile Ads SDK
22.4.0 mengakses Topics API dan mendeklarasikan
izin berikut secara default:
Jika Anda memilih tidak ikut pengujian Ad Manager untuk Topics API Android, lihat cara mencegah penggabungan izin di petunjuk Android.
Attribution Reporting API (dengan laporan debug)
Attribution Reporting
API
adalah bagian dari Privacy Sandbox dan dirancang untuk meningkatkan privasi pengguna
dengan menghapus ketergantungan pada ID pengguna lintas pihak dan untuk mendukung kasus penggunaan utama untuk atribusi dan pengukuran konversi di seluruh aplikasi seluler.
Google Mobile Ads SDK 22.4.0 mengakses Attribution Reporting API dengan
laporan debug dan menyatakan izin
berikut secara default:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-06 UTC."],[[["\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,["The [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\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\nGoogle Mobile Ads SDK\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\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\nGoogle Mobile Ads SDK 22.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)."]]
