How tracking works
Understand browser pageviews, sessions, custom actions, and the limits of collection.
The browser snippet creates an anonymous visitor ID and sends pageviews to Graytower. Pageviews include the path, page title, referrer, and supported campaign parameters. Graytower groups visits into sessions and can connect later actions to the same visitor.
What arrives automatically
| Signal | When it is sent |
|---|---|
| Pageview | Initial page load and client-side pathname change. |
| Source context | With a pageview when URL parameters or a referrer provide it. |
| Session context | Alongside browser events so visits can be grouped. |
Custom actions and scroll sections need explicit setup.
Sessions and events
A new session starts after 30 minutes of inactivity or a new acquisition context. The tracker also observes client-side changes to the URL path. Repeated views of the same path within 60 seconds are suppressed.
You can send custom events for actions such as newsletter_subscribe. Scroll events are opt-in: add data-gt-scroll to a section you want to measure. Graytower does not automatically send a custom event for every scroll.
Accepted pageviews and custom events use the Workspace's tracked-event allowance. Identity updates and Stripe payment imports do not.
Check collection
Use Website → Settings → Tracking to confirm a recent accepted pageview. If Traffic remains empty, follow Verify tracking before interpreting reports.