Answers
Site Traffic: your funnel without Google Analytics
Flip on the Site Traffic module and you get the analytics most people install Google Analytics for, except it comes from the tracking snippet you already run. Nothing else is installed and nothing is sampled or modeled.
Overview
Six figures for the window you pick, each against the period before: visitors, pageviews, engaged, average visit, leads and on mobile. Engaged means two or more pages, or ten seconds or more on the site. Below them: visitors and engaged visits by day (hover a day for its sources), how they arrived by channel with AI assistants as their own slice, the funnel, your top landing pages with a speed score beside each, when people visit as an hour by weekday grid in your own clock, and where they are. Running several websites? Filter by each one from the chips.
Sources, Pages, Visitors
Sources groups every visit by channel and says under each channel how it is decided, so nobody has to guess what Direct means; it also lists sources by tag, campaigns by tag joined to the ad platform’s spend, and referrers, with the untagged social visits named so you can tag the links. Pages is every landing page with its visitors, engaged rate, form submits and speed. Visitors is bounce, pages a visit, whether our cookie survives on your site, devices, hours and cities.
The funnel
The funnel connects everything: ad impressions to clicks to visits to leads to customers to dollars. Every stage is clickable. The top is anonymous by nature, counts rather than people, and it gets personal on the way down: leads and customers are actual names from your CRM. The impression and click stages fill from your connected ad accounts, so they stay grey until Google or Meta is connected. A grey stage beats a made up number.
Site health
Google PageSpeed checks your busiest landing pages every night on a phone and a desktop: the lab score, what real Chrome visitors saw over 28 days where Google has enough of them to say, a 90 day trend per page, and the audits in words. The score is Google’s; the link to your visitors is ours, so each page’s speed sits against its engaged rate and your ad cost.
Manage sites
Every site your snippet has reported from is listed under Settings → Modules → Site Traffic. Tick anything that is not really yours, a staging copy, a test build, somebody else’s domain, and it leaves every number on the page. Nothing is deleted: your raw events stay exactly as they arrived, and restoring a site brings its visits straight back.
Site monitoring
Every fifteen minutes we load your site’s home page the way a visitor would, from Cloudflare’s network, and time the answer. Two failed checks in a row count as an outage; one blip never does. An outage and its recovery are logged in Activity, listed under Site health with how long it lasted and why, and sent by email to the owner, or to the owner and the admins, or to nobody, whichever you choose under Settings → Modules → Site Traffic. A server that answers but refuses our check, a firewall usually, is shown as unknown and never as down. The same page load checks that your tracking snippet is still on the page: if it was there and goes missing, a redesign or a caching plugin is the usual cause, and Site health says so before your numbers go quiet.