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

How does browser identification work under dovekey for frequency-capping purposes? #37

Open
PedroAlvarado opened this issue Mar 9, 2021 · 1 comment

Comments

@PedroAlvarado
Copy link

That is, how is a Dovekey server able to count that a particular browser instance has seen an ad too many times? It seems that browsers will be required to provide a strong signal, albeit an encrypted one, that distinguishes one browser from another.

@gangwang-google
Copy link
Contributor

Thank you for your question.

The details need to be worked out with browser vendors. The high level idea is that, whenever an ad is rendered, the ad tells the browser its associated FCAP ID and FCAP rules. For each FCAP ID, The browser looks back the most recent N minutes/hours/days defined by the FCAP rule, and counts the number of times that ads were rendered with the FCAP ID.

For details please see Section Frequency capping (FCAP).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants