Google releases the Pixel Privacy Sandbox Developer Preview, built on Android 13.

Google introduced the Privacy Sandbox for Android in February to make mobile advertising more privacy-conscious while work on the Chrome version continues. On top of Android 13, a Developer Preview for the Privacy Sandbox is now accessible.

The Privacy Sandbox on Android wants ensures user privacy by default while bringing safer alternatives, tools, and approaches to the current ways in order to maintain the viability of the mobile advertising sector. This strategy, which is probably influenced by the company’s position as a major player in the advertising industry, is known as “ differs from Apple ,” and according to Google today, it restricts existing technologies that are utilized by developers and advertisers.

Learn more.

The Topics API and SDK Runtime are given an early preview in this Privacy Sandbox Developer Preview. The former was initially created for Chrome in order for apps and websites to offer relevant adverts based on recent interests. The latter isolates advertising SDKs (and their processes) included by apps.

Additional platform APIs and services are offered by Privacy Sandbox DP1 in addition to the Android 13 Developer Beta version, which was just made available to beta testers on Tuesday. It is intended for early testing of these novel technologies and assessing how you might include them into your remedies.

Google expressly states that it is only accessible through manual download and is not intended for daily or consumer use.

The Pixel 4, 4a, 5, 5a, 6, and 6 Pro may all be used to install it, as well as an Android emulator. The Pixel 4 XL build doesn’t exist. The following resources and activities, such as running sample apps , are provided by Google:

Topics API: Call the API and retrieve test values that illustrate the coarse-grained interests of the user. To learn more, see the documentation . Build and install an SDK that is runtime-enabled on a test device or emulator. Make a test app with the SDK loaded in the runtime and ask it to remotely render an ad using the app’s WebView. For details, see the documentation . Sample code for the Topics API and implementation of runtime-enabled SDKs is available on the GitHub Privacy Sandbox. API reference The Attribution Reporting and FLEDGE APIs will be previews in next DPs.

FTC: We employ automatically earning affiliate connections. wants 0

wants 1


Related Posts