Sign inGet started
Tracking

What the tag collects

View as MarkdownOpen in ChatGPTOpen in Claude
Connect your agent
Add to CursorAdd to VS Code

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?

WhatDetails
Page viewsEvery page, also on single-page navigation, with its title and HTTP status.
Where visits came fromThe 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 scrollHow long the page was in front, and how far it was read.
ClicksOutbound links, tel: and mailto: links (never the number or address), downloads and anything marked data-na-event.
FormsStarted, each field reached (its name or label, never what was typed), sent or abandoned.
JavaScript errorsUncaught errors and failed promises, with the file and line.
Page speedWeb Vitals (LCP, INP, CLS, FCP, TTFB) on one page view in ten.
DeviceDesktop, mobile or tablet; browser; operating system; country.
Google's dataLayerEvents 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.

Related
  • Add the tag: Put one script line in the head of every page. Where it goes in plain HTML, site builders and each framework.
  • Cookieless counting and consent: The tag counts without cookies until a visitor agrees. How consent works, from your banner or your code.
  • Custom events: Send your own events and orders, such as sign-ups, demo requests and purchases, with one line of JavaScript each, so revenue ties to the visit.
  • Identify people: Name signed-in people with identify, so their visits on every device make one profile your agent can read. It works only after the visitor's consent.
  • Subdomains, domains and Safari: Keep one visitor across your subdomains and your other domains, and stop Safari from forgetting returning visitors after 7 days.
  • Events from Google's dataLayer: The tag reads the events your site already pushes for Google Tag Manager, such as purchases and sign-ups.
Still have questions?
Was this page useful?