How about the possibility of malicious compliance? Companies have obnoxious cookie banners to 1) make the path of least resistance accepting all the cookies and 2) as a bonus, serve as propaganda against the cookie directive.
And among the companies who aren’t doing it for malicious compliance, many of them may be copying ideas from companies who do without realizing why they do it.
I think #1 is definitely the case: if you have to put up a banner even to do normal things that few people object to, might as well also include profitable things that are less popular. On the other hand, there are also a bunch of things that are important for the proper functioning of websites in the long term but are pretty hard to convey clearly in a banner. This is things like, as a way to verify that changes haven’t broken your site you typically want to roll them out gradually as an A/B test, which requires collecting enough metrics that you can tell whether and how A and B are performing differently. This is good for users in aggregate in that the site gets improvements faster and is less likely to have broken functionality, but is just kind of complicated.
How about the possibility of malicious compliance? Companies have obnoxious cookie banners to 1) make the path of least resistance accepting all the cookies and 2) as a bonus, serve as propaganda against the cookie directive.
And among the companies who aren’t doing it for malicious compliance, many of them may be copying ideas from companies who do without realizing why they do it.
I think #1 is definitely the case: if you have to put up a banner even to do normal things that few people object to, might as well also include profitable things that are less popular. On the other hand, there are also a bunch of things that are important for the proper functioning of websites in the long term but are pretty hard to convey clearly in a banner. This is things like, as a way to verify that changes haven’t broken your site you typically want to roll them out gradually as an A/B test, which requires collecting enough metrics that you can tell whether and how A and B are performing differently. This is good for users in aggregate in that the site gets improvements faster and is less likely to have broken functionality, but is just kind of complicated.