Analytics
Attriax analytics combine attribution, sessions, events, crashes, retention, and funnel views so teams can see what happened after a click, an install, or a release.
What the analytics workspace covers
The product already exposes these surfaces inside each project workspace today.
Overview dashboards
Track clicks, installs, users, sessions, events, conversion rate, first-launch sessions, top countries, top platforms, and top links.
Event explorer
Search event names, page names, and custom event data with filters for platform, country, locale, device, and app version.
Ad events
Review requests, loads, failures, impressions, clicks, rewards, and ad revenue in a dedicated monetization analytics page.
Crashes
Inspect fatal and non-fatal crashes, exception sources, stack traces, affected users, and release or session context.
Retention and funnels
Review cohort heatmaps, day-based retention windows, and saved funnel definitions with drop-off and conversion rates.
Link and click analytics
Break performance down by campaign links, countries, platforms, and click timelines, with deeper traffic forensics on higher plans.
SKAdNetwork
Monitor Apple developer-copy postbacks, signature status, fine/coarse values, schema decoding, ad-network identifiers, and source metadata.
Charts and tables
Use line charts, bar charts, pie charts, heatmaps, and detailed tables instead of relying on a single summary number.
How the views fit together
Attriax treats analytics as the layer that explains whether attribution and routing are actually producing good user journeys.
- Overview dashboards answer the top-line questions: traffic, installs, users, sessions, and conversion.
- Event explorer and recent sessions answer the debugging questions: which user, which platform, which payload, and which route.
- Retention, funnels, crashes, and revenue answer the product questions: do people stay, where do they drop, what broke, and what paid off.
Some advanced views are plan-sensitive. Revenue analytics require an eligible paid plan, click forensics go deeper on higher tiers, and team access starts on collaboration-ready plans.
Anonymous analytics
Consent-sensitive flows can still produce aggregate analytics without restoring a normal identified user path.
Read how anonymous metrics behave
The anonymous counters on the overview page are meant for privacy-restricted sessions where policies like GDPR prevented analytics permission from being granted, but product teams still need aggregate volume and trend visibility.
Revenue is part of analytics
Revenue is documented separately so you can share monetization-specific guidance without losing the bigger analytics context.
Open the revenue guide
See monetization metrics, refund handling, ARPU and ARPPU, LTV, transaction splits, and revenue trend charts.
SKAdNetwork reporting
SKAN is delayed, privacy-thresholded, and schema-dependent, so Attriax treats it as its own analytics workflow instead of mixing it into normal event reporting.
- Configure Window 1 six-bit rules and Window 2/3 coarse rules in the dashboard; Flutter and Unity SDKs load the saved schema during app open.
- Set NSAdvertisingAttributionReportEndpoint to https://skan.attriax.com and save the numeric iOS App Store ID so developer-copy postbacks can map to the app.
- Use the SKAdNetwork analytics page to inspect verification status, raw payloads, decoded fine values, coarse values, ad-network IDs, source identifiers, and CSV exports.
- Expect Apple delays, crowd-anonymity limits, missing fields, and schema-history caveats; do not compare SKAN counts one-to-one with normal install or event analytics.