Analytics You Can Actually Trust
Knowing what's working on your site shouldn't require bolting on a third-party analytics script and hoping it's configured correctly (or that it respects visitor privacy).
The pain it solves: Third-party analytics tools are often disconnected from your actual content and commerce data, and can raise privacy/compliance concerns depending on how they're configured.
How it helps:
- Built-in, strict analytics track what matters — page views, content engagement, shop performance, event registrations — without relying on external trackers.
- Because analytics live in the same platform as the content and commerce data they describe, reports can directly connect "this page" to "these orders" or "this event" to "these registrations."
- Strict data handling means analytics can be configured to respect visitor privacy rules by design, rather than needing to audit a third-party vendor's practices.
- Reports surface directly in Backstage dashboards, so there's no separate analytics portal to log into.
The happy workday: Open the dashboard, see what's actually working, and make decisions based on data you control — with no separate privacy audit required for a third-party tool.
Why This Matters for Your Organization
Owning your analytics data end-to-end simplifies privacy compliance and ensures the numbers you see are directly tied to your actual content, orders, and events — not an approximation from an external service.
Technical Details
Analytics data is captured and reported from within the platform itself, alongside the entities it measures (Item, ShopOrder, Event), rather than through third-party JavaScript trackers.
Key implementation points:
- Because tracking happens server-side/first-party rather than via third-party scripts, there is no dependency on browser cookie consent flows for external trackers — reducing both privacy risk and the need for cookie-banner complexity tied to analytics specifically.
- Reporting surfaces are integrated into the same Backstage dashboard widgets used for other modules (see the Dashboard module), so analytics sit alongside orders, events, and content activity rather than in a separate tool.
- Revenue-specific reporting (e.g.,
ManufacturerRevenueServiceinExireNexus.Services/Services/Shop/) demonstrates the pattern: analytics services are built as focused, single-purpose services layered directly on top of the existing commerce data models, not as a generic bolt-on analytics platform. - Multi-tenant isolation applies to analytics the same way it applies to all other data — each organization only ever sees its own numbers.
This "strict," first-party approach to analytics keeps reporting accurate, privacy-respecting, and tightly connected to the actual content and commerce data it describes.