Analytics
Understand recorded traffic, sources, interactions and enquiries.
Start with all traffic
Overview and Analytics use the visits and interactions received by your Zowar collector. Review sessions, pageviews, pages, sources, events and leads without connecting an external reporting account. Use the same date range when comparing reports.
- Sessions
- Recorded browser sessions; not a count of unique people.
- Pageviews
- Page loads and supported client-side route changes received by the collector.
- Sources
- Referrer and campaign attribution available for recorded traffic.
- Intent
- Actions such as form starts and contact-link taps; not proof of a completed conversation.
- Leads
- Submitted enquiries and supported automatic contact leads.
Understand the coverage
A tracker can only report what it receives. Blocked scripts, withheld consent, connectivity failures and missing campaign tags affect coverage. Session and attribution cookies do not identify a person across devices. A contact tap is an intent signal, not proof of a sale.
Manually entered and imported leads stay in the CRM, but are excluded from website conversion figures because no website visit was measured for them.
Traffic from Google remains a source of first-party visits when Google reporting is disabled. Referrers and campaign parameters do not require a reporting integration.
Optional Google figures
Google reporting is disabled by default. When an operator enables it, linked services can add impressions, search queries, advertising spend and Google Analytics figures. Those figures have their own definitions and should not be added to first-party session totals.
Google sign-in is separate from reporting. See the optional integration reference if your operator enables these services.