Website traffic

Nectazo can count visits to your own website and show them on your dashboard: how many people, where they came from, which pages they read, and who is on the site right now.

It needs the Nectazo Connect plugin and one checkbox. WooCommerce is not required — this works on any WordPress site.

Turning it on

1. 1In WordPress, go to Settings → Nectazo and tick Count visits to this website.
2. 2Save. That is the whole setup — there is no tracking code to copy and no ID to paste.
3. 3Open your Nectazo Dashboard. A Website panel appears once the first visit arrives.

What you see

“Right now” means someone has loaded a page in the last five minutes. The number refreshes while you are looking at it and stops when you switch tabs.

Underneath it is each of those people and the route they have taken, most recently active first. The route reaches back half an hour, so somebody who has been reading for a while shows their whole visit rather than only the page they are on.

No cookie banner needed

This stores nothing at all on a visitor's device — no cookie, no local storage, nothing. That is what makes it lawful to run without asking for consent, and it is not an option you can turn off.

• No IP addresses are stored, and no browser or device details.
• Visitors are told apart using a one-way code that is regenerated every day, so the same person on two days is two anonymous entries with nothing connecting them.
• The query string is removed from page addresses before they are stored, so anything a link happened to carry in it is discarded.
• Nothing is ever linked to a contact, an email address or a name — not even for people who are already on your list.
• Records are deleted after 90 days.

Why there is no “unique visitors this month”

Because visitors cannot be recognised from one day to the next, Nectazo can tell you how many different people visited on a given day, but not across a week or a month. Adding up seven daily figures would count somebody who came back on three days as three people.

Rather than show a number that is quietly wrong, that figure is left out. It is the honest cost of not using cookies, and other privacy-first tools carry the same limit whether or not they say so.

Routes, and the day they die

Analytics → Website lists today's visitors. Each one opens into the pages they read, in order, with the time of each and where they arrived from.

Today, and only today. The code that tells one visitor from another is a one-way hash of the day's date, so at midnight UTC it is regenerated and yesterday's cannot be reproduced — not by you, and not by us. Two days of routes can never be joined into a longer profile, because the halves no longer share anything to join on.

Nothing extra is collected to do this. It is the same rows the counts have always come from, read in order instead of added up, and still nothing is stored on the visitor's device. That is worth knowing when you write your privacy policy: what changed is what Nectazo shows you, not what it holds.

What is not here

Bounce rate, time on page, session recordings and heatmaps are all deliberately absent, as is any route that crosses a day boundary. Some would need a cookie; the rest would make this a web analytics product rather than a way to see whether your email is bringing anybody to your site.

Seeing which campaigns bring traffic

Add utm_source, utm_medium and utm_campaign to the links in your emails and those tags appear under Where they came from. A link tagged utm_source=newsletter is reported as “newsletter” rather than as the mail provider that opened it, which is usually what you wanted to know.

Which emails brought people in

Email carries no referrer, so somebody who clicks a link in your newsletter and lands on your site looks exactly like somebody who typed the address in. Both show as Direct.

Turn on Label links in my emails under Settings → Integrations → Website traffic and Nectazo adds a small tag to each link, so each campaign's traffic is counted separately. The campaign report then shows how many visits it sent, and the traffic sources list breaks them down by campaign rather than lumping them together.

• Links get slightly longer. Nothing else about them changes, and they go to exactly the same place.
• A link you have already tagged yourself is left alone — your own utm_source is never overwritten.
• The unsubscribe link is never tagged.
• Automation emails are tagged with the automation's name, so abandoned cart and post-purchase show up separately from broadcasts.

If nothing appears

• Give it a minute, and load a page on your site in a normal browser window rather than as a preview.
• Nectazo ignores obvious bots, so a link checker or an uptime monitor will not appear.
• The panel is hidden entirely until the first visit arrives, so a brand new setup shows nothing rather than a row of zeroes.
• The plugin needs a working API key — the same one that syncs contacts. If that is missing or revoked, nothing is sent.