No cookies. No banner. No lawyer.
PulseTrack never sets a cookie and never stores personal data, so there is nothing to ask consent for — and 16× less weight on every page load.
Cookie-free by architecture
Not a setting you enable — there is no code path in PulseTrack that writes a cookie or reads local storage.
No consent banner needed
Because nothing personal is stored and nothing is read from the device, the ePrivacy consent requirement does not apply.
16× lighter
2.8 KB against roughly 45 KB for GA4. That is a measurable Core Web Vitals difference on mobile.
How it works
Remove your old tag
Delete the GA4 snippet and, in most cases, the consent banner that existed to serve it.
Add PulseTrack
One script tag, no configuration and no data-processing agreement to negotiate.
Keep your data in the EU
Events are stored on EU infrastructure and never leave it.
Frequently asked
Am I really allowed to skip the cookie banner?+
Consent under ePrivacy is triggered by storing or reading information on a user's device. PulseTrack does neither. This reflects how cookie-free analytics is commonly treated, but it is not legal advice — check with your counsel for your jurisdiction.
What data is actually stored per visit?+
Page path, referrer, coarse country, device type, an anonymous daily session key and a timestamp. No IP address, no cookie, no cross-site identifier.
Where is the data hosted?+
On EU infrastructure. Events do not leave the European Union.
Do ad blockers block PulseTrack?+
Far less often than Google Analytics, because PulseTrack is not an advertising network and is not on the major tracker blocklists. You will typically see noticeably more traffic than GA4 reported.