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:
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.
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.
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:
ManufacturerRevenueService in ExireNexus.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.This "strict," first-party approach to analytics keeps reporting accurate, privacy-respecting, and tightly connected to the actual content and commerce data it describes.