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

Increasing K-Anon window size #491

Closed
radhika-mani opened this issue Mar 23, 2023 · 4 comments
Closed

Increasing K-Anon window size #491

radhika-mani opened this issue Mar 23, 2023 · 4 comments
Labels
Non-breaking Feature Request Feature request for functionality unlikely to break backwards compatibility

Comments

@radhika-mani
Copy link

Request: We would like to propose increasing the K-Anon window size from 7 to 14 days.

Background & Rationale

Chrome recently announced that K-Anon for rendering creatives will be 50 users over 7 days. Google Ads ran simulations using this threshold to measure the impact on advertiser reach and performance and saw that it would have a severe, negative impact especially on creatives used for dynamic remarketing. This impact is also likely to be more acute with small-to-medium sized businesses that may have more difficulty reaching the k-anon threshold.

For these reasons, we would like to propose increasing the K-Anon window size from 7 to 14 days. We believe this change will improve performance for advertisers while also striking the right balance between privacy and utility.

@tylerdev0
Copy link

I agree that increasing the window size would reduce the negative impact on specific creatives, especially in the context of #311 where specific creative sizes would be subject to K-Anon.

@JensenPaul JensenPaul added the Non-breaking Feature Request Feature request for functionality unlikely to break backwards compatibility label Jun 22, 2023
@leobierent12
Copy link

leobierent12 commented Sep 15, 2023

Comment from CRITEO recommendation team

Rationale :

In our continuous quest to enhance the performance of our platform while safeguarding user privacy, we have undertaken a comprehensive analysis of our current K-anonymity implementation. Our findings indicate that increasing the time window for K-anonymity can offer substantial benefits. This proposal outlines the advantages of extending the time window for K-anonymity, focusing on improving product displays and ensuring user privacy.

Current Challenges:

Currently, our platform operates with a 7-day time window for K-anonymity, which has successfully upheld user privacy. However, it presents certain challenges, particularly for products from partners with limited budgets. As per our analysis:

  1. Better Chance for Product Display: Extending the time window for K-anonymity would increase the likelihood of a single product being displayed over an extended period.

  2. Enhanced Partner Performance: Products from partners with low budgets are struggling to meet the K-anonymity filter within the existing 7-day timeframe.

Proposed Solution: Extending the Time Window for K-Anonymity:

We propose extending the time window for K-anonymity from 7 days to a more accommodating duration of 14 days. This change will address the following issues:

  1. Improved Partner Performance: Extending the time window provides products from partners with limited budgets a better chance to pass the K-anonymity filter. This will significantly enhance partner performance and their overall experience on our platform.

  2. Reduced Risk of Click Fallback: Our analysis reveals that by extending the time window, we could potentially save up to 5% of clicks currently at risk with our current implementation. This translates to a more accurate product display, leading to a superior user experience.

  1. Preservation of User Privacy: Crucially, this proposal does not involve changing the K-anonymity constraint itself. Therefore, user privacy remains uncompromised. We can ensure that the privacy of our users is guaranteed while enhancing the platform's performance.

Extending the time window for K-anonymity from 7 days to a more flexible duration is a strategic decision that addresses the challenges faced by our partner products and users. This change will improve product visibility, partner performance, and the overall user experience while maintaining our commitment to user privacy. We believe that this adjustment will create a better balance between performance and privacy, ultimately enhancing our platform's effectiveness.

@itaysharfi
Copy link

itaysharfi commented Nov 3, 2023

We appreciate your feedback and plan to increase the final K value to 50 over a window of 30 days. We are currently updating our explainers to reflect this change.

@JensenPaul
Copy link
Collaborator

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

5 participants