Analytics
Open any link and choose Analytics for the last 30 days (adjustable up to a
year).
What you get
| Panel | What it tells you |
|---|---|
| Clicks | Link opens in the window |
| Scans | QR scans in the window, counted separately |
| Unique | Approximate distinct visitors in the window |
| All-time clicks | The lifetime counter for the link |
| Timeline | Clicks and scans per day — the shape of the campaign |
| Referrers | The hosts traffic came from; direct/unknown is grouped |
| Devices | Mobile / tablet / desktop |
| Countries | Where visitors were |
Who clicked
Aggregates answer "how many". The who clicked panel answers "which people".
Identity is only knowable for clicks that carried a per-recipient marker — that
is, links ZingaConnect sent to a known contact. A link you posted on social media
or printed as a QR is anonymous by design, and always will be.
The panel shows:
- known clicks — clicks that came from an identified recipient,
- distinct recipients in the window,
- anonymous clicks — everything else, and
- the roster: which contacts clicked, how many times, and when they last did.
The counts are shown on every plan. The named roster needs a paid ZingaConnect
plan, since it is contact-level CRM data — so you always see a true number, and
know exactly what unlocking would add.
Bots are filtered
Mail-security scanners and image proxies fetch every link in an email before a
human ever sees it. Those hits are recognised and excluded from all the counters,
which is why a Zingalinks click count is usually lower — and much closer to
reality — than the raw hit count in a server log.
Reading the numbers honestly
- Unique visitors are approximate. They are derived from a hashed address,
not a cookie: a phone that moves from mobile data to Wi-Fi can count twice, and
an office behind one gateway can count as one. - Referrers are often missing. Apps and secure pages frequently strip the
referrer, so a large "direct / unknown" bucket is normal. - Scans and clicks can overlap. Someone can scan a code and later click the
same link from an email; that is two events from one person.
Pulling the data out
Everything on the page is available from the API
(GET /papi/v1/links/{id}/stats) if you want it in your own warehouse or
dashboard — see Analytics and QR codes.