Revenue Analytics
Attriax can track monetization events beside attribution data so revenue, refunds, campaigns, and user quality stay in the same workflow.
Analytics / Revenue
This section stays intentionally general. For detailed configuration, project-specific diagnostics, release context, and exact disclosure guidance, open the app workspace for your project.
Revenue metrics exposed today
The current revenue workspace focuses on normalized purchase and monetization reporting rather than generic accounting exports.
Net revenue, gross revenue, and refunds on the same timeline.
Paying users, ARPU, ARPPU, and average LTV.
Transaction type splits and optional ad-network breakdowns.
Recent monetization events with user, session, and attribution context.
Validation posture and normalized revenue event inspection.
Chart-ready trend lines that sit next to the rest of the analytics stack.
How teams use it
The goal is not only to record revenue, but to make it comparable with acquisition quality, lifecycle behavior, and release health.
- Compare net and gross trends to understand when refunds or reversals are distorting campaign performance.
- Follow revenue back to users, sessions, and attribution context instead of splitting monetization into a separate reporting silo.
- Use the revenue page as a monetization view while retention and funnel analytics handle the cohort and journey questions elsewhere in the workspace.
Availability
Revenue is part of the analytics surface, but not every plan exposes it.
Revenue analytics are currently available on eligible paid plans. Public docs stay general; the app workspace shows the exact plan gate for each project.