Skip to main content
Hiveku includes a privacy-friendly visitor analytics tool built into every project. No cookie banner required, no separate account, no manual script installation — just flip it on and start seeing traffic.

​
Enable Visitor Analytics

1

Open your project

From your dashboard, click the site you want to track.
2

Turn on the integration

Go to Hosting > Integrations and toggle Visitor Analytics on.
The tracking script is injected automatically at deploy time. You don’t need to add anything to your HTML.
3

Deploy

Click Deploy in the top bar. The script only attaches on the next build — existing live pages won’t track until they’re rebuilt.
4

Open the Analytics tab

Back in your project, click Analytics in the sidebar. You’ll see a dashboard that fills in as visitors arrive.

​
What Gets Tracked

  • Page views — every page load, with path and title
  • Sessions — grouped visits from the same visitor
  • Referrers — where visitors came from
  • Devices — desktop, mobile, tablet breakdown
  • Countries — based on IP geolocation (not stored)
  • Browsers and operating systems
Use the Date range selector at the top to switch between 24 hours, 7 days, 30 days, 90 days, or a custom range.

​
Reports

  • Top Pages — which URLs are getting traffic
  • Top Referrers — which sites are sending visitors
  • Browser / Device / Country breakdowns — audience composition
  • Real-time — see live visitors currently on your site
The real-time view is great for launches — refresh it as you share a link and watch traffic arrive.

​
Privacy Posture

Hiveku Analytics is designed to be GDPR/CCPA-friendly out of the box:
  • No cookies
  • No personal data stored
  • No cross-site tracking
  • IP addresses are used only for geolocation and then discarded
Most regions don’t require a cookie banner for this kind of analytics, but check your local regulations.

​
Using Google Analytics or Plausible Instead

If you prefer a dedicated analytics tool, you can keep Hiveku Analytics off and add your own.
1

Add your tracking ID as an env var

In Settings > Environment Variables, add:
NEXT_PUBLIC_GA_ID=G-XXXXXXX
or for Plausible:
NEXT_PUBLIC_PLAUSIBLE_DOMAIN=yourcompany.com
2

Add the script to your layout

Ask the AI: “Add Google Analytics using the NEXT_PUBLIC_GA_ID env var”. It will drop the right snippet into your root layout.
3

Deploy

Click Deploy. Traffic will start flowing to the external dashboard.

​
Verifying It Works

Visit your live site in a new browser or incognito window. Within a few seconds, you should see the visit show up in Analytics > Real-time. If you chose Google Analytics or Plausible, check those dashboards instead.

​
Troubleshooting

The tracking script attaches at build time. Click Deploy again after enabling the integration, then visit your site. Real-time should populate within seconds.
This is expected — uBlock Origin and similar tools block most analytics scripts. Hiveku Analytics tries to look like a first-party request, but dedicated blocklists still catch it. Test from a browser without blockers, or ask a colleague.
If you’ve attached a custom subdomain via your own CDN, the script may not be injected. Confirm the subdomain is pointed at Hiveku directly (see /publishing/custom-domains) and redeploy.
Single-page apps (React Router, Next.js App Router) often have client-side navigation that the default script tracks. If you’ve customized routing, the AI can audit your setup — ask: “Are my analytics capturing client-side route changes?”

​
What’s Next?

SEO

Pair analytics with SEO to understand which pages convert

Custom Domains

Track traffic on your own domain, not the .hiveku.com default