Foreign trackers on a Russian site
Every foreign counter or pixel ships visitor identifiers to servers outside Russia — a cross-border transfer of personal data that requires notifying Roskomnadzor before it starts and reflecting it in the policy. The practical choice: replace with a Russian analogue (Metrika, Top.Mail.Ru), or keep it — with the RKN notification, a policy entry, and loading strictly after consent.
Free online tool — compliance checker: instant results, no signup.
What exactly the problem is
GA, Meta Pixel, Hotjar and TikTok Analytics write a cookie identifier and send events to their servers (US/EU). Since 2023-03-01 cross-border transfer follows a notification regime: the operator files with RKN before the transfer begins. Meta is designated extremist in Russia — its pixel carries extra legal and reputational risk.
Three workable scenarios
- Replace: Metrika covers 90% of web analytics; for product analytics — self-hosted options in Russia
- Keep, properly papered: RKN cross-border notification, recipient and country in the policy, loading only from the banner's accept callback
- Hybrid: Metrika for everyone, GA only for the explicitly-consenting segment
Checking
The scanner identifies every third-party service, its vendor and jurisdiction against a catalogue of ~150 trackers, and flags foreign ones on a RU site with a dedicated rule — including those loading before consent.
Related
Why teams trust us
How it works
Enter your site URL
The scanner opens pages in a browser
Get a grade and a fix list
Why check your site for privacy compliance?
Regulators fine sites for processing personal data without consent — and a site starts processing earlier than it seems: analytics, pixels and widgets write cookies the moment the page loads. The scanner shows the auditor's view: what leaves for third parties before consent, whether the banner works, and whether forms collect data correctly.
Real Browser
Three sessions per page: no action, banner accepted, banner rejected.
Trackers and Jurisdiction
Service catalogue: who receives visitor data and in which country.
Policy at Collection Point
The policy link and consent element are checked next to the form, not in the footer.
Signed PDF
Report with an HMAC integrity stamp — hand it to your lawyer or contractor.
Who uses this
Business
preparing for an audit
Lawyers
technical facts for an opinion
Web Studios
client site handover
DevOps
consent regression monitoring
Common Mistakes
Best Practices
Monitor compliance automatically
Scheduled re-checks with an alert when pre-consent trackers appear on your site.
Sign up freeLearn more
Frequently Asked Questions
Does GA4 with "IP anonymisation" solve it?
No: the cookie identifier and events still travel to foreign servers — the transfer happens.
Is notification needed if the tracker loads after consent?
Consent and the cross-border notification are independent requirements: consent settles processing, the notification settles the transfer abroad.
Does loading a widget from a foreign CDN count as transfer?
The script download alone — not yet; a widget sending visitor identifiers to a foreign backend — yes.
Try the live tool that powered this guide
Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.