Diagnostics
Attriax includes diagnostics and setup views for teams that need to validate links, platform integrations, runtime events, and release readiness without guessing.
Diagnostics
This section stays intentionally general. For detailed configuration, project-specific diagnostics, release context, and exact disclosure guidance, open the app workspace for your project.
What the diagnostics workspace exposes
The signed-in app workspace is where the exact values live, but the public docs can still explain the workflow.
Platform configurators
Review platform-specific identifiers, verified web origins, desktop routing notes, and setup status tied to your project.
Test devices
Inspect detected platforms, recent devices, SDK versions, last-seen activity, and reset device records to replay attribution flows.
Recent sessions
Connect setup work to real traffic by checking app opens, page views, events, and recent runtime activity after integration changes.
Vibe Setup builder
Generate AI-ready implementation prompts with feature toggles, verification steps, and links back into the relevant SDK docs.
Special cases
Some integration paths are intentionally more hands-on, and the diagnostics pages make that explicit.
- Desktop support is manual today: your runner or activation handler forwards the URI, then Attriax resolves and routes it.
- Unity integrations benefit from an in-workspace validator after the package is imported and configured.
- Uninstall token bridges stay platform-specific. Unity Editor and desktop players do not register uninstall tokens directly.