Apivom Opus — web analytics that stays server-side
Opus is the privacy-first, server-side web analytics layer behind the Apivom products: visits, pages, goals and reports, collected on the server through Apivom Orbit instead of by a tracking script in the browser. Opus is included with the products and is not sold separately.
Infrastructure layerKnow how your sites are used, without a script on the page
Visits and events arrive server-side, every organisation gets its own site, and reports are archived on a schedule.
Server-side collection
The browser loads only the event SDK. A server-side adapter writes each visit to Opus, so there is no separate analytics script on the page.
One site per organisation
Every Iris and Atlas organisation gets its own analytics site, created automatically by a workflow, with a rollback if a step fails.
Goals and reports
Reports cover visits, pages, events, goals and conversions, custom dimensions and a live visitor log, so you can follow what people do.
Scheduled archiving
Tracking writes go to a queue and are processed in the background. Reports are archived every 5 minutes, not when someone opens a page.
Human and automated traffic
Every visit carries a traffic type. Automated traffic is labelled, not blocked, and saved segments let you leave it out of a report.
Operator sign-in
Apivom operators sign in to Opus through Apivom Key. Data is self-hosted, and erasure requests can be handled by user id or visitor.
How the Apivom products use Opus
You do not set Opus up on its own. It is where visitor analytics lands for the websites and portals Apivom runs, and Apivom Orbit is its only input. Here is where it is used today.
- apivom.com. Visits and events on the Apivom website are recorded in Opus, alongside other websites that Apivom runs.
- Iris portals. Each Iris organisation gets its own analytics site, provisioned automatically.
- Atlas. Each Atlas organisation gets its own site too, and Atlas’s public pages have one.
- Orbit as the only input. Opus receives events only from Orbit, server-side. Orbit’s Overview and Websites views draw on Opus and the warehouse.
Analytics without an extra script in the browser
Because Opus is fed by Orbit on the server, the page loads one event SDK and nothing else for analytics. The real client address is preserved through forwarding, and a visitor is recognised from the anonymous or user id.
- Self-hosted data. Analytics data stays on Apivom’s own platform rather than with an outside analytics service.
- Consistent visitors. A visitor id is derived from the anonymous id or the user id, so one person is one visitor.
- Erasure on request. Privacy tools handle erasure requests by user id or by visitor.
Frequently asked questions
What is Apivom Opus?
Opus is privacy-first, server-side web analytics. It records visits, pages, events, goals and reports for apivom.com and for the Iris and Atlas organisations, with one analytics site for each organisation. Apivom operators use it to see how the sites and portals are used.
Is Opus sold separately?
No. Opus is an infrastructure layer that is included with the Apivom products. You do not buy or set it up on its own. If you want to know what analytics you get with Iris or Atlas, talk to us.
Where does the data come from?
Only from Apivom Orbit, on the server. The browser loads the event SDK and nothing else for analytics, and an adapter on the server records each visit in Opus. There is no third-party tracking script on the page.
How does analytics work for a customer’s portal?
Each Iris and Atlas organisation gets one analytics site in Opus, created automatically by a provisioning workflow. Its events arrive through Orbit, and Orbit’s Overview and Websites views present web analytics per customer organisation built from Opus and the warehouse.
How fresh are the reports?
Tracking is written to a queue and a worker processes it in the background. Reports are archived on a 5-minute schedule, and archiving is not triggered from the browser, so opening a report does not slow it down.
How does Opus relate to Orbit?
Orbit is the event pipeline and Opus is one of the places its events end up. Orbit sends page and event data to Opus on the server, and also writes them to its own warehouse. Opus turns them into visits, goals and reports.
Analytics that comes with the platform
Opus is included with the Apivom products. Talk to us about what you want to measure.