Privacy-First Analytics for Modern Web Apps (Part 3)
Why analytics, advertising, and consent are tightly connected — and where the risks actually are
Analytics and advertising are often discussed separately.
In reality, they are deeply connected.
The moment you introduce ads — or even just conversion tracking — your analytics setup becomes part of a much larger system involving:
- user tracking
- profiling
- legal compliance
To understand the trade-offs, it helps to break things down.
The three types of advertising
Not all ads are the same. From a privacy and legal perspective, there are three fundamentally different models.
1. Contextual advertising (privacy-first)
Contextual ads are selected based on what the user is currently viewing, not who they are.
Example:
Page about CSS tools
↓
Ad for web hosting
Advantages
- no user tracking
- no personal profiles
- simple compliance
- works without consent banners in many cases
Typical networks
- Carbon Ads
- EthicalAds
This is the most privacy-friendly model and aligns well with developer-focused platforms.
2. Personalized advertising (tracking-heavy)
Personalized ads rely on tracking users across multiple websites.
Example:
User visits hosting websites
↓
Ad network builds profile
↓
Hosting ads shown elsewhere
Advantages
- higher ad revenue
- better targeting
Disadvantages
- requires extensive tracking
- strict consent requirements
- legally more complex
Typical platform
- Google AdSense
This is where most privacy concerns — and regulations — apply.
3. Conversion tracking (the hidden layer)
Even if you are not running ads, you may still care about:
Which action led to a signup?
This is called conversion tracking.
It is often used for:
- marketing campaigns
- onboarding optimisation
- product growth
This is also where Google Consent Mode becomes relevant.
Where Advanced Consent Mode fits in
Advanced Consent Mode tries to solve a key problem:
How can you measure behaviour if users decline cookies?
It does this by sending cookieless signals such as:
- page views
- timestamps
- device/browser info
- approximate location
Google then uses modelling to estimate user behaviour.
The legal reality in the EU and UK
Privacy regulation in Europe mainly comes from:
- GDPR
- ePrivacy / PECR
The core rule is simple:
Users must give consent before non-essential technologies access or store information on their device.
Traditional analytics cookies clearly require consent.
Why Advanced Consent Mode is debated
Even without cookies, Advanced Consent Mode still sends:
- device information
- page URLs
- IP-based location
Some privacy experts argue that this still counts as:
👉 accessing information from a user’s device
Because of this, Advanced Consent Mode sits in a legal grey area.
What can actually happen in practice
In reality, enforcement tends to focus on:
- large platforms
- large-scale tracking
- clear violations
Examples of companies involved in major enforcement actions include:
- Meta
- TikTok
For smaller websites, the most likely scenario is much simpler:
Regulator review
↓
Request to disable tracking before consent
In most cases:
- no fines
- no legal escalation
- just a requirement to adjust implementation
What this means for developers
When choosing an analytics and advertising setup, you are balancing:
- data quality
- legal clarity
- implementation complexity
A simple way to think about it:
Contextual ads → lowest risk
Hybrid analytics → balanced
Advanced consent mode → more data, more uncertainty
Personalized ads → highest risk
Key takeaway
The moment you introduce:
- ads
- tracking
- or conversion measurement
you are no longer just dealing with analytics.
You are designing a data collection system under legal constraints.
Understanding the differences between advertising models and consent strategies is essential to making the right trade-offs.
Series: Privacy-First Analytics for Modern Web Apps
- Why Cookie Consent Breaks Your Analytics
- Google Consent Mode Explained (React + TypeScript)
- Ads, Tracking, and the Legal Reality in the EU and UK
- The Hybrid Analytics Architecture
About this series
This series is based on real-world work building CSSEXY, a visual UI platform where understanding user behaviour is essential for improving the product.
All articles are also available on CSSEXY and there in the Gallery.
Top comments (0)