Usecase

Providing a consistent user experience in handling "user's ad opt-out preference" across different serving(FLEDGE and non-FLEDGE)

(See more details in this attached slides.)

Context(slide 2-5)

We run an ad business in Japan and deliver both direct ads(non-FLEDGE) and remarketing ads(considering implementing in FLEDGE) to our website (yahoo.co.jp). We provide a consistent user experience between them for users who want to opt out from specific ads.

When you click the "i" icon on the top right corner, it will navigate to our feedback page, then you can opt-out the ad you saw. The opt-out setting will be applied to both direct ads and remarketing ads.

Although we are considering implementing in FLEDGE, it is not feasible with FLEDGE since we cannot use the data from users’ feedback in future FLEDGE bidding.

Currently, we have a leaveAdInterestGroup() for removing an interest group from a browser. However, we think leaveAdInterestGroup() has the following problems regarding an opt-out control.

• Users can still rejoin the interest group they already have left by revisiting the same advertiser's website. leaveAdInterestGroup() is a solution for temporary removal from an interest group and not permanent.
• leaveAdInterestGroup() can only opt out from an interest group. When you want to opt-out all ads from a specific advertiser, you have to execute leaveAdInterestGroup() API one by one.
  • For example, let's say we have 2 interest groups, "Brand A - red shoes" or "Brand A - blue shoes". When you want to opt-out from all Brand A ads, but after opting out from "Brand A - red shoes", you will still see the ads with "Brand A - blue shoes"

Proposal(slide 6-13)

• New browser storage that stores users’ ad opt-out preferences data, which can only be readable through browser worklet
• New APIs for writing into the opt-out browser storage
  • addOptoutAdInterestGroup: Add an opt-out data to the browser storage.
  • deleteOptoutAdInterestGroup: Delete an opt-out data from the browser storage.

We believe that providing consistent user experience across different serving channels is critical, because users have no idea whether the ad they see is from FLEDGE or non-FLEDGE.

Any thoughts on this proposal?