03 September 2017
(Updated 4 Sep 2017: add screenshot and how to see the warning.)
Advice from yan, on Twitter:
if your site embeds tweets, add <meta name="twitter:dnt" content="on"> so that Twitter doesn't track your visitors https://t.co/Hn6QjE0hHQ— yan (@bcrypt) September 1, 2017
I decided not to do that for this site.
Yes, user tracking is creepy, and yes, collecting user information without permission is wrong. But read on for what could be a better approach for sites that can make a bigger difference.
First of all, Twitter is so far behind in their attempts to do surveillance marketing that they're more funny and heartening than ominous. If getting targeted by one of the big players is like getting tracked down by a pack of hunting dogs, then Twitter targeting is like watching a puppy chew on your sock. Twitter has me in their database as...
Owner of eight luxury cars and a motorcycle.
Medical doctor advising patients about eating High Fructose Corn Syrup.
Owner of prime urban real estate looking for financing to build a hotel.
Decision-maker for a city water system, looking to read up on the pros and cons of cast iron and concrete pipes.
Active in-market car shopper, making all decisions based on superficial shit like whether the car has Beats® brand speakers in the doors. (Hey, where am I supposed to park car number 9?)
So if Twitter is the minor leagues of creepy, and they probably won't be something we have to worry about for long anyway, maybe we can think about whether there's anything that sites can do about riskier kinds of tracking. Getting a user protected from being tracked by one Tweet is a start. But helping users get started with client-side privacy tools that protect from Twitter tracking everywhere can help with not just Twitter tracking, but with the serious trackers that show up in other places.
Blocking Twitter tracking: like kicking a puppy?
Funny wrong Twitter ad targeting is one of my reliable Internet amusements for the day. But that's not why I'm not especially concerned with tagging quoted Tweets. Just doing that doesn't protect this site's visitors from retargeting schemes on other sites.
And every time someone clicks on a retargeted ad from a local business on a social site (probably Facebook, since more people spend more time there) then that's 65 cents or whatever of marketing money that could have gone to local news, bus benches, Little League, or some other sustainable, signal-carrying marketing project. (That's not even counting the medium to heavy treason angle that makes me really uncomfortable about seeing money move in Facebook's direction.)
So, instead of messing with quoted Tweet tagging, I set up this script:
This will load the Aloodo third-party tracking detector, and, if the browser shows up as easily trackable from site to site, switch out the page header to nag the user.
(If you are viewing this site from an unprotected browser and still not seeing the warning, it means that your browser has not yet visited enough domains with the Aloodo script to detect that you're trackable. Take a tracking protection test to expose your browser to more fake tracking, then try again.)
If the other side wants it hidden, then reveal it
Surveillance marketers want tracking to happen behind the scenes, so make it obvious. If you have a browser or privacy tool that you want to recommend, it's easy to put in the link. Every retargeted ad impression that's prevented from happening is more marketing money to pay for ad-sponsored resources that users really want. I know I can't get all the users of this site perfectly protected from all surveillance marketing everywhere, but hey, 65 cents is 65 cents.
Bob Hoffman's new book is out! Go click on this quoted Tweet, and do what it says.
Today's Newsletter (special clickbait edition) GUNFIGHT AT THE AD TECH SALOON https://t.co/OI9JXs1hbM— adcontrarian (@AdContrarian) September 3, 2017
Links to stuff
Good points here: you don't need to be Magickal Palo Alto Bros to get people to spend more time on your site. USA Today’s Facebook-like mobile site increased time spent per article by 75 percent