Tracking
What the tag collects
Page views, clicks, forms, scroll, errors and page speed, counted without code. What never leaves the page.
Updated
The tag counts what most sites need without any code from you. Here's what it counts, and what it never touches.
What does the tag count on its own?
| What | Details |
|---|---|
| Page views | Every page, also on single-page navigation, with its title and HTTP status. |
| Where visits came from | The referrer, UTM tags and ad click ids (Google, Microsoft, Meta, TikTok, LinkedIn, X, ChatGPT Ads). AI assistants such as ChatGPT, Claude and Perplexity are their own channel. |
| Time on page and scroll | How long the page was in front, and how far it was read. |
| Clicks | Outbound links, tel: and mailto: links (never the number or address), downloads and anything marked data-na-event. |
| Forms | Started, each field reached (its name or label, never what was typed), sent or abandoned. |
| JavaScript errors | Uncaught errors and failed promises, with the file and line. |
| Page speed | Web Vitals (LCP, INP, CLS, FCP, TTFB) on one page view in ten. |
| Device | Desktop, mobile or tablet; browser; operating system; country. |
| Google's dataLayer | Events your site already pushes for Google Tag Manager. See Events from Google's dataLayer. |
What does the tag never collect?
- What a visitor types into a field, passwords, card numbers.
- IP addresses: used to find the country and, before consent, to make the day's visitor code, then dropped. Never stored.
- Emails, tokens and long ids in page addresses: cleaned out before they leave the page.
How do you count your own events?
Sign-ups, demo requests and purchases mean something only to your site, so the tag can't guess them. Send them with one line each: Custom events.