Analytics and tracking scripts

The analytics and advertising scripts the pages load. Which ones they are is a fact about the site, not a fault in it; whether they run before consent is the question on the next row.

• Help center

Analytics counters, ad tags and session-recording tools all arrive the same way: as a script on the page that phones home to a third party. Knowing which ones a site loads is the starting point for everything else in this section — what the privacy policy has to mention, what the consent layer has to hold back, and how much third-party code each visit pulls in.

How SiteScan finds them

The scan reads every <script> on the crawled pages — its address, its inline code and its data- attributes — and matches them against known vendors: Google Analytics, Google Tag Manager, Google Ads, Meta Pixel, Hotjar, Microsoft Clarity, Yandex Metrica, Matomo, TikTok Pixel, LinkedIn Insight, Intercom and Segment. A container id such as GTM-… or G-… counts even when a consent tool is still holding the tag back. The names are listed in the Trackers row of the Privacy & consent group — with a grey dash, because it is a fact rather than a verdict — and on the Analytics line of the Technology group.

A tracker is not a fault. The report flags only what goes wrong around it: tags that load as plain scripts despite a banner, tracking cookies set by the very first response, or two containers of the same kind that count every visit twice.

Remove the tags nobody reads any more, and see Consent layer and third-party scripts for the rest.