The Reporting Nobody Ever Has Time to Build
Zunoy tracks content, API traffic, visitors and media delivery on its own. You get a dashboard, plus a digest every week and every month.
Content, API, Visitor, and Delivery Data — One Dashboard
Most platforms measure one of these. Tracking all four together is what lets you link an API spike to a content type, or heavy delivery to one oversized image. The connection is the useful part.
Content inventory
Types, entries, published counts, per-type breakdowns, recent activity.
API traffic
Total calls, 24-hour and 7-day windows, active keys, request logs.
Website visitors
Browser, device and OS, plus country, country code and city.
Media delivery
Which assets get requested, and which transformations run.
PUBLISH RATIO
Published vs. Total Entries Shows Stalled Content
Zunoy tracks total entries and published entries for every content type. The ratio between them is often the most useful number on the dashboard. Almost nobody thinks to look at it. A content type with 200 entries and 12 published is telling you something — either the project was abandoned, or the workflow is stuck.
Per-type totals shown next to per-type published counts
See exactly how many entries exist versus how many are live, for every content type.
Top content types by real usage, not creation date
Ranked by actual publish activity, so you know what's really being worked on.
Recently created entries for a quick activity read
A fast pulse check on what's been added without digging through logs.
RARE FOR A HEADLESS CMS
Visitor Data, Next to Your Content
Zunoy records browser, device type and OS from the user agent, and resolves country, country code and city. It sits beside your content inventory instead of a separate tool — so "which countries visit us" and "what content do we have for them" are one screen apart.
Browser, device and OS captured per request
Country, country code and city resolved geographically
Admin traffic counted separately from public API traffic
Weekly and Monthly Digests
Zunoy builds and sends digests on a schedule. Visibility stops depending on someone remembering to open a dashboard. Weekly covers recent activity. Monthly adds trend and plan usage.
Feature | Weekly | Monthly |
|---|---|---|
Cadence | Every week | Every calendar month |
Best for | Catching problems early | Trends, reporting upward |
Growth comparison |  — |  Against the previous month |
Plan usage bar | — | Usage against your tier limits |
See Plan Usage Before You Hit a Limit
Hitting a plan limit hurts because nobody saw it coming. API calls, form submissions, AI credits, storage. Putting usage against limit in the monthly digest makes the trend visible weeks early, while it is still a decision rather than an emergency.
Search Queries Are Analytics Too
Every query logged
Match quality and latency captured per query
Low-scoring questions ranked
Weak matches surface as content opportunities
Real intent, real visitors
Not keyword-tool guesswork
Branching Does Not Distort Your Numbers
Analytics count the main branch only, never your working branches.
Creating a branch clones your content without inflating your inventory
Branch three times and your published-entry count stays honest
Dashboards keep describing your live site, not an in-progress redesign
Who This Is For
Content leads
Proof of what is working, and a published-to-total ratio that exposes stuck workflows before anyone thinks to ask about them.
Per-type inventory with publish ratios
Visitor questions as a ready-made content backlog
Developers
API traffic across 24-hour and 7-day windows, with request logs. Admin activity is kept separate from genuine public consumption.
Active key counts and request-level detail
Founders
A monthly digest that arrives without anyone building it. Growth against last month, and how much plan headroom is left.
Growth and plan usage in one email
Agencies
Reporting for every client workspace, without setting up analytics infrastructure for each site you take on.
Scheduled digests per workspace, zero setup
Where the Data Comes From
Insights gathers activity the rest of the platform already produces. Nothing needs separate instrumentation.
Headless CMS Engine
Content inventory and per-type entry counts
Global Edge CDN
Asset access and transformation delivery logs
AI Studio
Semantic query logs with match counts and latency
Cookie Consent
Consent grant rates broken down by category
Forms
Submission volume measured against plan quotas
Environments
Analytics scoped to main, keeping figures accurate
Common Questions
What analytics does Zunoy provide?
Four layers. Content inventory with entry and publish counts per type. API traffic with 24-hour and 7-day windows. Website visitor analytics. And media delivery covering asset access and transformations.
How often are reports sent?
On two schedules. Weekly digests cover recent activity so problems surface early. Monthly digests add a growth comparison against the previous calendar month and a summary of plan usage.
Do content branches distort the figures?
No. Analytics count the main branch only. Cloned content on working branches does not inflate entry counts or other inventory metrics while a redesign is under way.
Does Zunoy include website visitor analytics?
Yes. Zunoy records browser, device type and operating system from the user agent. It also resolves country, country code and city. This is unusual for a headless CMS to include natively.
Do monthly reports show usage against plan limits?
Yes. Monthly digests include a plan usage bar showing consumption against your tier limits. Approaching a limit becomes visible weeks before it disrupts anything.
Is admin activity counted separately from public API traffic?
Yes. Zunoy tracks admin-layer and public API calls apart from each other. Internal editing activity stays distinguishable from real consumption by your frontend or other clients.
Stop Digging Through Logs for Answers
The reporting you keep meaning to build is already running.