Monitoring the trackers on your site
A tracker is rarely added by decision: it arrives with an extension, a supplier, a new integration. Spotting it means looking, regularly.
In short
Pulsar regularly opens your site in a real browser and records the trackers and cookies set before any interaction. You are notified by email as soon as a new one appears.
What the scan measures
The scan loads your page as a visitor would, without clicking anything, and notes everything that is set. That is the moment that matters legally: what leaves before any interaction is what should have waited for consent.
The report separates cookies, trackers identified by their domain, and outgoing requests to third parties. Each finding carries a code and an explanation.
Reading the score
The score summarises, it does not judge. A site at eighty out of a hundred is not eighty per cent compliant: it carries less serious findings than a site at forty. It is the list of findings that must be read, not the number.
The heaviest finding is data leaving before any interaction. It means a visitor was measured by a third party without having accepted anything.
When you get an alert
You are only notified about something new: a tracker or cookie that was not there last time. An alert therefore means something changed on your site, not that an old problem persists.
The right reaction is to identify what changed recently: an updated extension, a tag added by a supplier, a new integration.
Read next
- Why Pulsar does not ask for consent Pulsar sets no cookie and keeps no identifier that could recognise a person from one day to the next. The ePrivacy Directive therefore does not require prior consent, and no banner is needed.
Missing an answer? Write to us. We reply ourselves, and we complete this guide.
Ask a question