search

android / privacy-sandbox-samples

Apache License 2.0
130 stars 52 forks source link

How can I check source & trigger registration works well? #91

Open jen6 opened 9 months ago

jen6 commented 9 months ago

Hi, Android Privacy sandbox team.

In Chrome privacy sandbox, I can check source & trigger registration and reports in chrome://attribution-internals/. It seems to have tab OS Registrations but when I tested it using the sample app there was no data in attribution-internals. Is this behavior expected? If not how can I check source and registration like chrome internal tools?

Virtual Device Image : UpsideDownCakePrivacySandbox

erintwalsh commented 8 months ago

Hi @jen6,

Unfortunately, there is not an exact equivalent to chrome://attribution-internals/ for Attribution Reporting on Android. However, you can set up Verbose Debug Reports to get information on whether source and trigger were registered successfully, and if not, information on the error. You can set these up by adding the field "debug_reporting": true to your Attribution-Reporting-Register-Source and Attribution-Reporting-Register-Trigger response headers.

I also recommend turning on verbose logging with the command adb shell setprop log.tag.adservices VERBOSE and then filtering for adservices messages in Logcat, which will also provide information on source and trigger registration.

I hope this helps!