> Don’t look for a section on permissions or consent in that document, by the way. There isn’t one. And nothing about nerd lawyer stuff like “opt out of sale” or “objections to processing” in there, either. The Big Tech companies want a two-track system, where other companies’ ad features are required to do all the privacy regulation hassles, but the browser’s own built-in tracking feature is something that people have to find the right setting for and turn off.
This language to make consent popups sound good is suspicious. Not being interrupted while you're browsing is good. A browser setting that people can turn off once, for all participating websites, is good.
>Problem one: Over-rating search, social, and app store ads
Isn't this a problem with today's ad attribution system? The author doesn't try to argue how the new system makes it worse.
>Problem two: Incentives for extra tracking
Same as above. It sounds like he's against attribution in general, which is an okay position to have, but I'd rather he say this upfront and more directly rather than spending 1k+ words on what essentially can be boiled down to "I hate Attribution Level 1 because it's attribution, and attribution is bad in general", and implying the issues he has are issues with Attribution Level 1 specifically.
Agreed, this can't be worse than what it's replacing. Still, the author has some interesting points I hadn't considered before.
I guess from the advertiser's perspective this standard could be a concern, because the loss of cookie-based tracking might make it harder for them to develop alternative attribution tracking methods that don't have the same data quality problems.
> Agreed, this can't be worse than what it's replacing.
The mistake is assuming this replaces anything instead of becoming just one more piece of the tracking puzzle.
Even if it did "replace" cookies or whatever, it's strictly worse than "before" because it's giving advertising a front seat in the browser. My browser should be doing precisely nothing to help you attribute your ad impressions or whatever. But now Mozilla et al have to waste their time maintaining and augmenting this opaque piece of mathematical faff.
This is a debate I've seen many times now on HN. I sympathize with what you're saying, but the flip side is that many users seem to prefer a free ad-supported funding model over a paid, ad-free model. If a site is going to be serving me ads anyway, then all else being equal I'd rather them make as much money off each impression as possible to incentivize them to keep providing me with free services. The privacy and resource cost of a user's browser sending anonymized attribution statistics is very minimal.
Maybe? Depends on what the ads are for. Obviously I'm not going to buy something I don't actually want just to support the site I'm on, but I have no particular objection to buying something I discovered through an ad if it's something I would buy anyway if I discovered it organically.
This seems like this is written by an advertiser who wants their profits, but pretending to care about privacy so they get users' support.
Here is a more honest summary:
"This proposal hurts us, small advertisement networks and professional marketers. Reject it, or we will ramp up the tracking to compensate for the lost opportunities!"
So they “reinvented” HTTP cookies but with only advertisers?
> Technically, the way it works is that a script running on a site with ads asks the browser to record an ad impression. Then the browser keeps a record of ads seen from all the sites you visit. Later, when you buy something, the retail site can ask the browser to generate a “conversion report” that can be passed to a centralized aggregation service.
Sort of. Cookies track you as an individual with a unique identifier. The conversion report only tracks anonymized aggregate statistics that can't be used to identify you as an individual.
The next time anyone on HN says "GDPR should've been a setting in the browser", I'll just point them to this. This is what browser vendors are making as a default setting.
> Don’t look for a section on permissions or consent in that document, by the way. There isn’t one. And nothing about nerd lawyer stuff like “opt out of sale” or “objections to processing” in there, either. The Big Tech companies want a two-track system, where other companies’ ad features are required to do all the privacy regulation hassles, but the browser’s own built-in tracking feature is something that people have to find the right setting for and turn off.
This language to make consent popups sound good is suspicious. Not being interrupted while you're browsing is good. A browser setting that people can turn off once, for all participating websites, is good.
That’s what the Do Not Track signal was for, but tech bros still don’t get consent sooooooooo…
I'm not sure what this blog is complaining about.
>Problem one: Over-rating search, social, and app store ads
Isn't this a problem with today's ad attribution system? The author doesn't try to argue how the new system makes it worse.
>Problem two: Incentives for extra tracking
Same as above. It sounds like he's against attribution in general, which is an okay position to have, but I'd rather he say this upfront and more directly rather than spending 1k+ words on what essentially can be boiled down to "I hate Attribution Level 1 because it's attribution, and attribution is bad in general", and implying the issues he has are issues with Attribution Level 1 specifically.
Agreed, this can't be worse than what it's replacing. Still, the author has some interesting points I hadn't considered before.
I guess from the advertiser's perspective this standard could be a concern, because the loss of cookie-based tracking might make it harder for them to develop alternative attribution tracking methods that don't have the same data quality problems.
> Agreed, this can't be worse than what it's replacing.
The mistake is assuming this replaces anything instead of becoming just one more piece of the tracking puzzle.
Even if it did "replace" cookies or whatever, it's strictly worse than "before" because it's giving advertising a front seat in the browser. My browser should be doing precisely nothing to help you attribute your ad impressions or whatever. But now Mozilla et al have to waste their time maintaining and augmenting this opaque piece of mathematical faff.
This is a debate I've seen many times now on HN. I sympathize with what you're saying, but the flip side is that many users seem to prefer a free ad-supported funding model over a paid, ad-free model. If a site is going to be serving me ads anyway, then all else being equal I'd rather them make as much money off each impression as possible to incentivize them to keep providing me with free services. The privacy and resource cost of a user's browser sending anonymized attribution statistics is very minimal.
Do you want to click through and spend money on the ads?
If not you aren't really working towards them paying a lot for ads, right?
Maybe? Depends on what the ads are for. Obviously I'm not going to buy something I don't actually want just to support the site I'm on, but I have no particular objection to buying something I discovered through an ad if it's something I would buy anyway if I discovered it organically.
>Do you want to click through and spend money on the ads?
Nobody "wants" ads, but they do want the free content they get today, which are funded by ads.
> many users seem to prefer a free ad-supported funding model over a paid, ad-free model.
You don't need pervasive and invasive tracking and wholesale trading of your data to display advertising.
> Agreed, this can't be worse than what it's replacing.
Why can't it?
Because as GP alluded to, the thing it's replacing (cookies) already does exactly the same thing but isn't anonymized.
> the thing it's replacing (cookies) already does exactly the same thing but isn't anonymized.
No idea what it's replacing. Cookies is a red herring. Tracking involves more than just cookies.
This seems like this is written by an advertiser who wants their profits, but pretending to care about privacy so they get users' support.
Here is a more honest summary:
"This proposal hurts us, small advertisement networks and professional marketers. Reject it, or we will ramp up the tracking to compensate for the lost opportunities!"
> When Meta, Google and Apple [and Mozilla] agree on a “privacy” feature, watch out.
?
This feels like a good sign, to me. I get far more worried when I see the likes of Meta, Google, Spotify, Epic etc team up.
And you think that they team up for your benefit?
Most people (and orgs) do things that benefit themselves. The question as a user, who is likely to be more aligned with you?
- Mozilla, Meta, Google, Facebook
- VP of "monetization technology" company, "Marketing data expert"
Closed immediately due to the invasive "using this site means you agree to our terms of service!!" Popup
Did you read it?
You can tell who works in adtech
> called Attribution Level 1, as a standard feature of web browsers
We need to eliminate private companies from our browsers in general. Many years ago they called it "acceptable ads".
So they “reinvented” HTTP cookies but with only advertisers?
> Technically, the way it works is that a script running on a site with ads asks the browser to record an ad impression. Then the browser keeps a record of ads seen from all the sites you visit. Later, when you buy something, the retail site can ask the browser to generate a “conversion report” that can be passed to a centralized aggregation service.
Sort of. Cookies track you as an individual with a unique identifier. The conversion report only tracks anonymized aggregate statistics that can't be used to identify you as an individual.
> The conversion report only tracks anonymized aggregate statistics that can't be used to identify you as an individual.
Combined with the other 200+ tracking points from your machine... Yes, yes you can be identified.
More importantly it's privacy preserving because it doesn't allow for bidirectional communication, which third party cookies could do.
The next time anyone on HN says "GDPR should've been a setting in the browser", I'll just point them to this. This is what browser vendors are making as a default setting.