Attriax Docs

General Attriax documentation covering SDKs, setup workflows, platform coverage, attribution, analytics, Smart Pages, store privacy, diagnostics, and collaboration.

Start with the surface you care about most

Every page here is public. Use the project workspace when you want detailed setup steps, validation tools, release details, or project-specific disclosure guidance.

Setup Workflows

See how configurators, builders, diagnostics, and the AI-assisted Vibe Setup flow fit together at a high level.

Open docs

Platform Coverage

Understand where Attriax is strongest today, where support is more manual, and how to choose the right SDK path.

Open docs

Ad Network Integrations

Map AdMob, AppLovin MAX, ironSource LevelPlay, Admost, and other ad SDK callbacks into standardized Attriax methods.

Open docs

Flutter SDK

Use the reference mobile SDK for deep links, install attribution, page tracking, events, and runtime diagnostics.

Open docs

Web SDK

Track browser journeys, manual page views, deep-link resolutions, and web-first attribution flows.

Open docs

React SDK

Drop Attriax into routed SPA flows with a provider, deep-link hooks, and route-aware page view tracking.

Open docs

Analytics

Explore attribution, sessions, events, retention, funnels, crashes, and chart-heavy dashboards in one workspace.

Open docs

Attribution

Understand standard links, dynamic links, install referrer capture, deferred deep links, and attribution analytics.

Open docs

Smart Pages

Publish branded app entry and onboarding pages, connect them to your links, and review view analytics, referrers, and plan limits.

Open docs

Diagnostics

Inspect platform setup, origin and domain configuration, recent test sessions, and guided validation flows.

Open docs

Store Privacy

Review generic Play Store and App Store disclosure guidance before you open the app-specific mapping tools.

Open docs

GDPR & Consent

Understand the shared GDPR consent model and the public SDK entry points before wiring your own consent UI.

Open docs

Teams

Share work across owners, editors, and viewers without giving every teammate the same level of control.

Open docs

Supported platforms

Every SDK now wraps one shared Kotlin Multiplatform core, so Flutter, web/JS, React, React Native, native Android, native iOS, Unity, and desktop all ship the same 0.6.0 behavior. Mobile and web remain the surfaces we validate most deeply.

Primary support

  • Android and iOS are the core mobile targets for install attribution, deep links, and runtime tracking.
  • Browser web is a first-class surface for links, page views, route tracking, and web journey analytics.
  • Flutter, browser JS, React, React Native, native Android, native iOS, Unity, and desktop all ship on the shared 0.6.0 core.

Additional coverage

  • Windows, macOS, and Linux desktop apps ship on the shared core via com.attriax:core-jvm and the Kotlin/Native klibs; desktop deep-link routing is best validated with the diagnostics.
  • Unity ships as a versioned Git UPM package (0.6.0) with runtime setup and validation surfaces, wrapping the same shared core as every other SDK.
  • The project workspace includes the diagnostics that make these lighter-tested paths much easier to validate.

What unlocks after you create a project

Public docs explain the product. The project workspace adds the project-aware helpers that save the most setup time.

Configurators and builders

  • Detailed project values, environment-aware setup surfaces, and platform-specific configuration helpers.
  • Per-project docs tabs for SDK usage, store privacy answers, platform configuration, and release downloads.
  • Link defaults, Smart Page builders, revenue provider status, and platform-specific integration helpers.

AI-assisted Vibe Setup

Vibe Setup stays project-specific on purpose. Inside the project workspace, Attriax can generate a ready-to-use AI prompt for Flutter, web, React, React Native, native Android, native iOS, Unity, or desktop with your enabled features, implementation checklist, and verification steps. That is where the "save hours of coding" path lives.