Amplitude GDPR compliance and consent risk
Amplitude provides product analytics. This page combines ConsentLens detection rules with live public scan data so you can see how often Amplitude appears, whether it fires before consent, and which compliance issues it tends to create.
1%
Of scanned sites
4 of 384 public sites include Amplitude.
0%
Fire before consent
0 detected sites fired it before a user could consent.
0%
Seen after rejection
No post-rejection evidence found in public scan data.
MEDIUM
Consent risk
Analytics tracker classified from ConsentLens tracker database.
How ConsentLens detects Amplitude
Domains
- cdn.amplitude.com
- api.amplitude.com
Globals
- window.amplitude
Script patterns
- amplitude.js
ConsentLens combines these signals with request timing. If Amplitude sends a data request during the first 500ms of page load, it is treated as a pre-consent tracking risk and connected to the relevant scan evidence.
Common compliance issues
No tracker-specific issue titles are available yet. When public scans produce issues naming Amplitude, this section will show the most frequent findings.
Example public scans detecting Amplitude
| Domain | Score | Consent timing |
|---|---|---|
| linkupst.com | 20/100 | No early fire |
| relevant.software | 20/100 | No early fire |
| hostinger.com | 73/100 | No early fire |
| lemonde.fr | 63/100 | No early fire |