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

Digital Services Act compatability #1050

Open
patmmccann opened this issue Feb 22, 2024 · 0 comments
Open

Digital Services Act compatability #1050

patmmccann opened this issue Feb 22, 2024 · 0 comments

Comments

@patmmccann
Copy link
Contributor

patmmccann commented Feb 22, 2024

So there is a legal requirement that some publishers tell a user, perhaps from their cmp, or perhaps using their own tech, or perhaps from say the adchoices icon, the reason an ad was selected for them. See https://iabtechlab.com/iab-tech-lab-releases-for-public-comment-specification-for-dsa-transparency/ .

It seems a publisher can basically pick one of two options: (a) let (and trust under threat of govt penalty) that the fenced ads will render the DSA information or (b) not allow fenced frames

A is undesirable to many pubs bc the amount of trust to extend to the advertising community in general without a validation mechanism is quite large. B seems undesirable as well for obvious reasons.

How can a publisher used fenced frames but also prevent responses without dsa information from rendering? Assuming that is possible, how can a publisher used fenced frames but also prevent responses with insufficiently detailed dsa information from rendering?

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

1 participant