Wanted: Online Pubs Doing Real (and Therefore GDPR-Compliant) Advertising
blogs.harvard.edu
blogs.harvard.edu
1. Any kind of even vaguely targeted advertising is better than none. It's common sport on HN to jeer about how badly the ads that people see are targeted towards them but non-targeted is so much worse. It's ads for restaurants that won't be in my area for decades (if ever). Male and female specific medicines, and on and on.
2. The rampant abuse and fraud on the part of the publishers. Much of the js and tracking on sites is not about _you_ so much as making sure that the site that the ads are embedded on isn't just a VPS that someone is flogging with bot traffic.
I want some level of targetting in my ads. But too much and it becomes obnoxious and frustrating. I wish I could just check off the boxes I want:
- Canadian - Lives in Ontario - Male - 30-39
Hmm yeah I think that's all I want you to use.
Instead they ask for nothing and seek to take everything. That's the part I can't tolerate.
My experience with targeted ads is either way off base or suggesting something I don't need because I literally _just_ bought it. But mostly I don't experience them because they're so easy to block. Then they don't even get the potential benefits of word of mouth.
As far as fraud, the roll of an online advertising company should be to ensure both parties are holding up their end of the deal, ensuring links go where they are supposed to and sites are presenting ads as agreed. That can be done with code the ad companies write for the advertiser and content providers to run on their own servers during the agreement. Pawning that off on the user machine doesn't solve the fraud issue, but apparently advertisers are convinced it does, for now. It does get you tracking, but only as long as users put up with it. It's lazy and, hopefully, it won't be a profitable solution much longer.
But for a while I've had the worst of both: huge amounts of data slurping, combined with terribly targeted ads.
LANG=de_DE.UTF-8
LC_MESSAGES=C
There is substantial disagreement among the programs that I use [1] whether this constitutes a German locale or an English locale.[1] True, only those programs which are dumb enough to assume that locale is described by a single word like "German" or "English".
That seems to be in direct conflict with GDPR provisions that force web publishers to give people the option to reject personalized ads while still giving them the services they were trying to access. I'm sure that when regulators come calling, they'll claim "legitimate interest," but if this model is acceptable under GDPR, then almost nothing has actually changed under it.
The reason why nearly everyone is using consent currently is because the other straightforward one which is:
(f) Legitimate interests: the processing is necessary for your legitimate interests or the legitimate interests of a third party unless there is a good reason to protect the individual’s personal data which overrides those legitimate interests. (This cannot apply if you are a public authority processing data to perform your official tasks.)
Is so vaguely defined as far as benchmarks go and no one is up for taking the risk of being at the mercy of the judgment of 28 different regulators and court systems.
Which part of the GDPR requires a site to give access to someone who doesn't agree to their terms?
This describes us as we sell our own ads, self-host them, and only allow static jpg graphics.
After changing our MailChimp signup form and removing sharing button scripts I think the only 3rd party things we use are Google analytics (now with anonymous IP settings activated) and a google font and jquery cdn.
For me, the goal has been to create a site that attracts a specific audience and target the ads based on the content.