What Lies Beneath: What are they really tracking and how?
summary
Used webpagetest.org, GTmetrix, Chrome DevTools to load news.com.au once (no scrolling, no login) and observed ~40 marketing/analytics domains contacted, with up to 27 cookies per domain. Evidence shows third parties (Facebook, Google, AddThis, Taboola, Rubicon, Scorecard Research, ID5) receive hashed/encrypted identifiers, shopping and offline purchase data, and undergo server-side relays that forward first‑party‑collected data to ad networks. Incognito is ineffective; selective JS blocking or a curated privacy extension is the practical defense.
AI-written summary · about
chapters (15)
- 0:00Start
- 2:21Overview
- 2:40Why collect data?
- 11:02Facebook tracking (Ooops, they changed it!)
- 15:17Only enterprises collecting?
- 17:44AddThis Policies
- 19:21Case study
- 20:23Tools used
- 22:04Marketing/analytics platform root domains
- 22:41Data sent?
- 30:20Apps
- 30:53Risk Factors
- 33:43What can you do?
- 40:27What do I do?
- 41:38Questions?
related talks
49mWeb Side Story: A Privacy Odyssey through Tracking and Fingerprinting
49mBeyond Cookies: The Unseen Privacy Risks of Web Analytics
42m8 Unbelievable Things You Never Knew About Tracking
42mGoodbye Tracking, Hello Privacy
46mDeep dive into third-party performance
57mData Protection & Digital Marketing – An interactive networking session
27mTracing Information Flows Between Ad Exchanges Using Retargeted Ads
41m"Analytics and how it should be!"