You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: