Difference between revisions of "Trust Tokens"
Jump to navigation
Jump to search
m |
m |
||
| Line 1: | Line 1: | ||
| − | Google's Trust Tokens are “issued” by one organization (a trust provider) and “redeemed” across different publishers.<ref>https://iabtechlab.com/blog/explaining-the-privacy-sandbox-explainers</ref> Redemption requires the consent of the issuer. The token state is stored local to a web client. | + | Google's Trust Tokens are “issued” by one organization (a trust provider) and “redeemed” across different publishers.<ref>https://iabtechlab.com/blog/explaining-the-privacy-sandbox-explainers</ref> Redemption requires the consent of the issuer. The token state is stored local to a web client.<ref>https://github.com/dvorak42/trust-token-api</ref> |
== Impact == | == Impact == | ||
Revision as of 15:22, 12 January 2021
Google's Trust Tokens are “issued” by one organization (a trust provider) and “redeemed” across different publishers.[1] Redemption requires the consent of the issuer. The token state is stored local to a web client.[2]
Impact
By removing the technographics that are often used to detect non-human traffic via Privacy Budget, marketers would not be able to rely on existing fraud detection and prevention services. Moreover, by not being able to detect which publishers' sites have relatively more non-human traffic more of marketers budgets will be spent on fraud.
Open Questions
- Can organizations other than Google create Trust Tokens? And if so, how can their quality of trust be compared?
- What validation service can redeeming organizations rely upon to ensure that a token is not copied from one web client to multiple others?