Smartlook GDPR compliance and consent risk
Smartlook records user sessions and generates heatmaps. This page combines ConsentLens detection rules with live public scan data so you can see how often Smartlook appears, whether it fires before consent, and which compliance issues it tends to create.
1%
Of scanned sites
5 of 384 public sites include Smartlook.
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.
HIGH
Consent risk
Session replay tracker classified from ConsentLens tracker database.
How ConsentLens detects Smartlook
Domains
- smartlook.com
- rec.smartlook.com
Globals
- window.smartlook
Script patterns
- smartlook.js
ConsentLens combines these signals with request timing. If Smartlook 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 Smartlook, this section will show the most frequent findings.
Example public scans detecting Smartlook
| Domain | Score | Consent timing |
|---|---|---|
| feecreative.com | 20/100 | No early fire |
| hestabit.com | 20/100 | No early fire |
| anadea.info | 48/100 | No early fire |
| relevant.software | 20/100 | No early fire |
| lovedayandco.com | 78/100 | No early fire |