Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FLEDGE: User-based A/B testing #122

Open
alois-bissuel opened this issue Feb 23, 2021 · 0 comments
Open

FLEDGE: User-based A/B testing #122

alois-bissuel opened this issue Feb 23, 2021 · 0 comments
Labels
Non-breaking Feature Request Feature request for functionality unlikely to break backwards compatibility

Comments

@alois-bissuel
Copy link

Hello,

A/B testing is at the heart of the web and its constant improvement. It applies to ad tech in particular. In its current form, FLEDGE does not allow for owner-wide AB-testing.

Following the idea laid out in SPARROW, we would like to propose an identifier to be added to the browser signals (for bidding and reporting).
This identifier would be specific to the IG owner, resettable by the user at any time (and might be periodically reset by the browser), and be of very low cardinality (say less than 32).
This would enable buyers (and sellers too, if they set their identifier) to run a handful of A/B tests simultaneously (depending on the split) while presenting a very limited risk for privacy.

What are your thoughts on this?

@alois-bissuel alois-bissuel changed the title User-based A/B testing FLEDGE: User-based A/B testing Feb 23, 2021
@JensenPaul JensenPaul added the Non-breaking Feature Request Feature request for functionality unlikely to break backwards compatibility label Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Non-breaking Feature Request Feature request for functionality unlikely to break backwards compatibility
Projects
None yet
Development

No branches or pull requests

2 participants