Client reporting & attribution
Agencies need clean data separation, not just separate folders. Nimriz makes each client domain a fully isolated reporting unit — so data you share with clients only contains their own links, clicks, and analytics.
- Analytics scoped at the data layer — not filtered in a dashboard after the fact
- Bot-flagged click events so client reports reflect real human traffic
- Privacy mode on by default — IP and User-Agent not stored
Each client's data is isolated to their own domain — no cross-client visibility.
What you get
Analytics scoped at the data layer — not filtered in a dashboard. Client A's records are structurally separate.
Bot-flagged click events with referrer, country, and device — reflects real human traffic for each client.
Each client gets their own branded domain — links look like they belong to the client, not an agency tool.
IP and User-Agent not stored with privacy mode on — easier to address client data-handling requirements.
How it works
Per-client data at the data layer
Click records are stored with (domain_id, short_code) as the key. This means client A's analytics are structurally isolated from client B's — no query-time filtering required.
- Domain-bound uniqueness means the same slug can exist across client domains without collision — consistent campaign structures across clients.
- Analytics are scoped per (domain_id, short_code) at the data layer, so reports are always isolated by default.
- Bot signals are flagged in click records — client-facing reports show cleaner numbers without manual bot filtering.
- Per-domain fallback landing URLs keep expired links returning branded responses per client.
- Workspace isolation means all client domains can be managed from one login without leaking configuration or data.
Related use cases
Ready to get started?
Create your account and start using Nimriz in minutes. Starter is free — no credit card required.