Know what gets attention after launch
See visits, sources and audience across your workspace—or explore a single project. Try the same analytics interface you’ll use in Console.
Open analyticsProjects in this workspace
Selected range: 24h
Selected range: 24h
Selected range: 24h
Traffic Trend
Traffic Sources
Traffic by Location
Device & System & Browser
Device
OS
Browser
Know if the page deserves the next move
Before you rewrite copy, buy traffic, or wire up product analytics, get the first answers that decide whether the site is working.
Traffic Trend
The first read after publish
Find out if a portfolio, campaign page, docs update, or client preview actually gets opened after the link goes out.
Interest, not vanity traffic
Referrers, countries, and entry paths help separate a useful audience from a pile of empty pageviews.
Design with the actual audience
See the browser, operating system, and device mix before you spend time tuning the wrong layout problem.
A lighter default
Use platform-level launch visibility first, then add a full analytics product only when the project needs deeper behavior tracking.
See what keeps moving
Compare projects and time ranges to spot which sites keep growing and which launches stopped earning attention.
Improve the pages with a chance
Top URLs show where attention is already landing, so optimization starts with pages that can actually convert.
Traffic Sources
Useful when the launch is still warm
The first few days after a link is shared are when basic traffic signal matters most.
Independent builders
Know whether a portfolio, side project, or one-page launch is getting attention without spending the afternoon wiring up tracking.
Marketing teams
Read the early response to a campaign page while copy, routing, and audience targeting can still be changed.
Commercial landing pages
See which sources, devices, and pages are worth attention before changing the offer or buying more traffic.
Frequently asked questions
Q: Does this slow the site down?
The built-in view does not require adding a heavy third-party analytics bundle to your static files. Your page payload can stay focused on the site itself.
Q: Is this included on every plan?
Analytics availability follows plan limits and retention settings. Teams can start simple and upgrade when historical depth or traffic volume grows.
Q: How long is data retained?
Retention follows the active plan so higher tiers can keep more historical visibility for ongoing comparison work.
Q: Can I exclude internal traffic?
That belongs in advanced analytics settings. The goal is to keep team review traffic from muddying launch data.
Start from the part every static site already has
Upload the built files, get a live HTTPS link, then add domains, rollback, analytics, automation, and team control when the project needs them.