Documentation

Integrate Daively with an explicit measurement contract.

Start with one SDK key, keep billing value server-authoritative, and validate the complete path before a production conversion rollout.

Start here

Documentation by workflow

Install Swift Package 3.x, configure the SDK key, ATT flow, sales events and purchase observations.

Add the Android SDK, configure install delivery, Install Referrer, deep links and product events.

Configure Link ID, event mapping, App Conversion delivery, spend sync and SKAN reconciliation.

Connect authenticated billing lifecycle without coupling the Daively SDK to a billing dependency.

Create owned links for QR, web, email and cross-promotion, then resolve attribution in the app.

Understand device-scoped attribution access, export, erasure and credential revocation.

Integration principles

Installs, sessions and product events belong to the native measurement contract.

Value, currency, trials, renewals and refunds come from authenticated server sources.

External conversions are queued, deduplicated and observable independently from event acceptance.