Closed guybashan closed 9 months ago
This was done by choice as a way to limit getting information about audiences created by other parties or potentially leaking other data. I'll bring this up as feedback to our engineering teams to see if anything can be done for a debug build, but right now the best way to see which audiences are registered on the device is to run an auction and see if your bidding logic or other endpoints are being hit
It seems like the class: CustomAudienceManager allows only to register custom audiences, but no means for fetching them. It might be useful, especially when working with the API and debugging it, to be able to list the existing custom audiences.